How to run it in real SQL Server instead od SQL Express


Is there a way to run it with sql server 2005 instead of SQL Express ?
The preinstallation checklist is telling me that it's required and I don't feel like installing it because I already have the real SQL Server.


habibh wrote Aug 7, 2009 at 5:49 AM

Unfortunately, there currently isn't a clean way of doing this. You need to make changes in several places including the Dependency Checker, SQL restore scripts and the connection string(s) to make this work. It's certainly possible to make these changes but it involves some work.

Habib Heydarian.

wrote Aug 13, 2009 at 9:53 AM

fmorriso wrote Feb 26, 2010 at 12:02 PM

I encounter this all the time and find there are two choices available to work around the issue:
  1. If the connection string(s) of the applicatoin, typically located in web.config, can be modified, simply change ".\sqlexpress" and "UserInstance=True" to "." and remove the entire UserInstance=True string.
  2. If you cannot edit the application's connection string(s) or it has an installer that insists that a named isntance of SQL Server named sqlexpress must first exist, then simply install a new, named instance of "regular SQL" (Enterprise, Standard, Developer, etc.) name, guess what? Yes, you guessed it. sqlexpress. In most cases, the application never knows the difference. You may still have to hack the connection string(s) of the application to remove "UserInstance=True", but that's usually a one-time change.
Of the two choices, #1 is the best but may not be viable depending upon your situation. #2 works but requires you have the rights to install a new, named instance, which may be even less viable than choice #1.

wrote Feb 14, 2013 at 6:35 PM