Webcast on deploying embedded databases


Update: Q & A from the webcast is available here. I’m still working on getting the source code posted. If you missed this webcast, you can view it on demand from this page.

———————————————

I’ll be giving a webcast that describes how to deploy an embedded database using Visual Studio 2005 ClickOnce technology. The webcast will be at 1 PM Pacific time on Friday 5/12. You can register for the webcast here.

I hope you have a chance to log in.

Mike Wachal
SQL Express team

Comments (6)

  1. Josh.Fruits says:

    I saw this On-Demand webcast and found it very useful. The topic of distributing your applications with SQL Server Express does not seem to be widely covered.

    During the webcast there was mention that the source code used for the helper class (sorry, forget the name off hand) would be made available, probably in this weblog. It would be nice if a link to it would be posted.

    I find quite a few webcasts quite useful. Thanks for taking the time to put them together.

  2. sync-mobile says:

    I  watched your archived webcast and it was very good (sorry about posting this question by mistake in your Access webcast).

    It was a little hard to tell but it looked like the deployed application was about 1 GB in size.  Is that correct?  If so, is there any way to minimize the size and how small can it be if you are deploying SQL Server Express?

    Thanks.

  3. Woodworks says:

    This web cast offered many different ideas in a very useful maner. I was very impressed. More More Bravo.

  4. Embedding SQL Express to use with Linq to SQL and User Instances can be a pain

  5. Bob says:

    This web cast is no longer available, is the text of it written down somewhere.

    I too had the problem of data never seeming to be written to the database, turns out it is a simple thing, that the db file is being overwritten when I run the project.

    This faq

    blogs.msdn.com/…/668971.aspx

    Tells me to change the project settings to "Copy if newer", but that the db may still get over written. The problem here is that some of the db is filled automatically in code, but some requires interaction from myself. I don't want to have to do this every time I run it and it could all be in development for quite some time.

    A solution I was trying for is to create the database and then just access it as a service from my code, but as far as I can see SQL Express does not seem to allow this, am I wrong in that?