|
web
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
deployment of project migrating MSDE to SQLExpressmanged group, please let me know. I currently have an application written in VB.Net using MSDE as the database. Current install is via InstallShield. As I've just found out that MSDE is not supported under Vista, I need to migrate to SQLExpress. I am also potentially interested in migrating to using an installer built in Visual Studio. I have a few questions: Are there any "best practices" for migrating from msde to sqlexpress? As this is a downloadable trial application, I need to minimize download size -- suggestions for doing so? Is it possible to configure so that SQLExpress and the .Net framework are only downloaded on an as needed basis? The configuration for SQL Express needs to be transparent to the user -- I use a specific instance with a sa password unknown to users. Getting started with creatign installs via Visual Studio documents would be helpful. The install needs to support a couple of different scenarios - ie: a "server" install that installs and configures sqlexpress and a "client" install that only installs program files and is able to pass command line parameters to the .exe so that I can handle setting connection strings etc. internally. Any help would be greatly appreciated. Hi Matt,
First of all, I would like to confirm my understanding of your issue. From your description, I understand that you need to migrate to VS.NET setup project from InstallShield. Also, you need to include SQL Server 2005 Express Edition in the setup project. If there is any misunderstanding, please feel free to let me know. In a setup project or ClickOnce deployment, you can add Prerequisites to the application. When the prerequisites are not detected, the setup project or ClickOnce will try to install them. After installation, you can run certain scripts to configure the SQL Express. Here is some reference: http://msdn2.microsoft.com/en-us/library/h4k032e1.aspx In this case, there are two scenarios. In a setup project, the size of a SQL Express package is about 34MB. The package is installed when needed, but downloaded always. The Setup project does not support download when needed option. Otherwise, you can try to use ClickOnce deployment. When it detects that certain prerequisites are not installed, it will try to download the setup package from a location you specified. Thus minimizes the download size. For more information about ClickOnce, please check the following link: http://msdn2.microsoft.com/en-us/library/wh45kb66.aspx If anything is unclear, please feel free to reply to the post. Kevin Yu Microsoft Online Community Support ================================================== Get notification to my posts through email? Please refer to http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif ications. Note: The MSDN Managed Newsgroup support offering is for non-urgent issues where an initial response from the community or a Microsoft Support Engineer within 1 business day is acceptable. Please note that each follow up response may take approximately 2 business days as the support professional working with you may need further investigation to reach the most efficient resolution. The offering is not appropriate for situations that require urgent, real-time or phone-based interactions or complex project analysis and dump analysis issues. Issues of this nature are best handled working with a dedicated Microsoft Support Engineer by contacting Microsoft Customer Support Services (CSS) at http://msdn.microsoft.com/subscriptions/support/default.aspx. ================================================== (This posting is provided "AS IS", with no warranties, and confers no rights.) Matt,
In addition to Kevin, there are no other differences between using MSDE and SQLExpress (beside connection string) than that SQLExpress is thousand times easier to install, than MSDE was. (You can use SQLExpress as well in a kind of Access way with a not enclosed database but that was not your question). Cor Show quoteHide quote "Matt Fielder" <mfielderREMOVECAPS@nospam.nospam> schreef in bericht news:ObtwOFLFHHA.924@TK2MSFTNGP02.phx.gbl... > First off, if this is better posted in another group that qualifies as a > manged group, please let me know. > > I currently have an application written in VB.Net using MSDE as the > database. Current install is via InstallShield. As I've just found out > that MSDE is not supported under Vista, I need to migrate to SQLExpress. > I am also potentially interested in migrating to using an installer built > in Visual Studio. > > I have a few questions: > Are there any "best practices" for migrating from msde to sqlexpress? > As this is a downloadable trial application, I need to minimize download > size -- suggestions for doing so? Is it possible to configure so that > SQLExpress and the .Net framework are only downloaded on an as needed > basis? > The configuration for SQL Express needs to be transparent to the user -- I > use a specific instance with a sa password unknown to users. > Getting started with creatign installs via Visual Studio documents would > be helpful. The install needs to support a couple of different > scenarios - ie: a "server" install that installs and configures sqlexpress > and a "client" install that only installs program files and is able to > pass command line parameters to the .exe so that I can handle setting > connection strings etc. internally. > > > Any help would be greatly appreciated. > Thanks for the reply Cor... Looks like I'm getting a lot of good information
here. Ease of use and updating to more current standards are other reasons for changing to SQLExpress. I've picked up a "Beginning SQL Server 2005 Progamming" from Wrox to try and get an idea of some of the differences ... I'm hoping that 90% of my stuff will just work after converting the DB. My use of the DB engine really is pretty simplistic, just tables, views and stored procedures. No triggers or automated backups or things of that nature are in use. I do know already there are a few changes that need to be made - such as my CreateDatabase script probably won't work. I provide backup and restore capabilities that I manage via scripting and that will probably have to change as well. You did mention that SQLExpress can be used in an Access sort of way. I also seem to remember that it's possible to just use a path to a data file in the connection string. ... does this mean that it's possible to simply distrubute a data file and not need to install the engine on customers machines? Show quoteHide quote "Cor Ligthert [MVP]" <notmyfirstn***@planet.nl> wrote in message news:O09C3cQFHHA.5000@TK2MSFTNGP03.phx.gbl... > Matt, > > In addition to Kevin, there are no other differences between using MSDE > and SQLExpress (beside connection string) than that SQLExpress is thousand > times easier to install, than MSDE was. (You can use SQLExpress as well in > a kind of Access way with a not enclosed database but that was not your > question). > > Cor > > "Matt Fielder" <mfielderREMOVECAPS@nospam.nospam> schreef in bericht > news:ObtwOFLFHHA.924@TK2MSFTNGP02.phx.gbl... >> First off, if this is better posted in another group that qualifies as a >> manged group, please let me know. >> >> I currently have an application written in VB.Net using MSDE as the >> database. Current install is via InstallShield. As I've just found out >> that MSDE is not supported under Vista, I need to migrate to SQLExpress. >> I am also potentially interested in migrating to using an installer built >> in Visual Studio. >> >> I have a few questions: >> Are there any "best practices" for migrating from msde to sqlexpress? >> As this is a downloadable trial application, I need to minimize download >> size -- suggestions for doing so? Is it possible to configure so that >> SQLExpress and the .Net framework are only downloaded on an as needed >> basis? >> The configuration for SQL Express needs to be transparent to the user -- >> I use a specific instance with a sa password unknown to users. >> Getting started with creatign installs via Visual Studio documents would >> be helpful. The install needs to support a couple of different >> scenarios - ie: a "server" install that installs and configures >> sqlexpress and a "client" install that only installs program files and is >> able to pass command line parameters to the .exe so that I can handle >> setting connection strings etc. internally. >> >> >> Any help would be greatly appreciated. >> > > No the user needs the engine but you can deploy that seperately.
Cor Show quoteHide quote "Matt Fielder" <mfielderREMOVECAPS@nospam.nospam> schreef in bericht news:e8cvVaXFHHA.1912@TK2MSFTNGP03.phx.gbl... > Thanks for the reply Cor... Looks like I'm getting a lot of good > information here. > > Ease of use and updating to more current standards are other reasons for > changing to SQLExpress. I've picked up a "Beginning SQL Server 2005 > Progamming" from Wrox to try and get an idea of some of the differences > ... I'm hoping that 90% of my stuff will just work after converting the > DB. My use of the DB engine really is pretty simplistic, just tables, > views and stored procedures. No triggers or automated backups or things > of that nature are in use. I do know already there are a few changes that > need to be made - such as my CreateDatabase script probably won't work. I > provide backup and restore capabilities that I manage via scripting and > that will probably have to change as well. > > You did mention that SQLExpress can be used in an Access sort of way. I > also seem to remember that it's possible to just use a path to a data file > in the connection string. ... does this mean that it's possible to simply > distrubute a data file and not need to install the engine on customers > machines? > > "Cor Ligthert [MVP]" <notmyfirstn***@planet.nl> wrote in message > news:O09C3cQFHHA.5000@TK2MSFTNGP03.phx.gbl... >> Matt, >> >> In addition to Kevin, there are no other differences between using MSDE >> and SQLExpress (beside connection string) than that SQLExpress is >> thousand times easier to install, than MSDE was. (You can use SQLExpress >> as well in a kind of Access way with a not enclosed database but that was >> not your question). >> >> Cor >> >> "Matt Fielder" <mfielderREMOVECAPS@nospam.nospam> schreef in bericht >> news:ObtwOFLFHHA.924@TK2MSFTNGP02.phx.gbl... >>> First off, if this is better posted in another group that qualifies as a >>> manged group, please let me know. >>> >>> I currently have an application written in VB.Net using MSDE as the >>> database. Current install is via InstallShield. As I've just found out >>> that MSDE is not supported under Vista, I need to migrate to SQLExpress. >>> I am also potentially interested in migrating to using an installer >>> built in Visual Studio. >>> >>> I have a few questions: >>> Are there any "best practices" for migrating from msde to sqlexpress? >>> As this is a downloadable trial application, I need to minimize download >>> size -- suggestions for doing so? Is it possible to configure so that >>> SQLExpress and the .Net framework are only downloaded on an as needed >>> basis? >>> The configuration for SQL Express needs to be transparent to the user -- >>> I use a specific instance with a sa password unknown to users. >>> Getting started with creatign installs via Visual Studio documents would >>> be helpful. The install needs to support a couple of different >>> scenarios - ie: a "server" install that installs and configures >>> sqlexpress and a "client" install that only installs program files and >>> is able to pass command line parameters to the .exe so that I can handle >>> setting connection strings etc. internally. >>> >>> >>> Any help would be greatly appreciated. >>> >> >> > > Hi Matt,
I agree with Cor, that although we can redistribute the database file, it still requires the SQLExpress engine to run. Kevin Yu Microsoft Online Community Support ================================================== (This posting is provided "AS IS", with no warranties, and confers no rights.) 
Other interesting topics
Re: Is VB.NET Stable?? To Aaron Kemp - Ahole Extrordinare
String to Byte & Vice Versa End Processing in Multithreaded App Best way to communicate from Desktop to SQL DB Re: Is VB.NET Stable?? Create Property on the fly Cross-thread operation not valid. catching close button Re: Is VB.NET Stable?? Calculate inside a form and use the same form as Insert record form |
|||||||||||||||||||||||
