06 Jan 2012
06 Apr 2012
Link to this post
We worked with SQLEXPRESS and attachedFile functionality for development step. For the production environment we wanted to migrate under SQLSERVER 2008 R2.
As SQLSERVER does not support attached file functionnality we created a "real" database from the database file. Next we tried to change the connection string and here is our problem : whatever value we set the connection string, it seems sitefinity always try to work from the database file.
Here is our cconnection string : Server=.\SQLSERVER;Database=sitefinity;Integrated Security=SPPID
And the associated error when we try to visit our website : "The user instance login flag is not supported on this version of SQL Server".
We tried to add "User Instance=false" to the connection string without result, we tried to user a SQL authentification instead of windows authentification... same thing : always the same error.
We tried to create a new Sitefiniy project, if we specify a new database in the sartup option sitefinity create the database and use it but there is no connection string in the web.config. If we specify an existing database it doesn't work and create a database file under app_data. If we create a database in a new project, next delete these database in SQLServer management studio then import an existing sitefinity database we have errors with the custom modules created from the moduleBuilder.
We cannot just re-enter all the site content. So, how can we do ?