SQL Server Express LocalDB support

Does Lightspeed support "SQL Server Express LocalDB" (ref: http://www.microsoft.com/sqlserver/en/us/editions/express.aspx)? If yes, which provider should be used?

Looking at the docs, it looks like LocalDB is just like 'normal' SQL Server from the client point of view, just deployed differently and with a special connection string format. So we believe that LightSpeed should work with LocalDB by specifying the SqlServer2008 provider and a LocalDB connection string. We have not yet tested this configuration though -- let us know if you run into problems and we'll investigate further.

Yes, as Ivan has mentioned LocalDB acts the same as a 'normal' SQL Server 2012 instance so for LightSpeed we would recommend you use the SqlServer2008 provider.

If you have .NET 4.0.2 or 4.5 installed you can connect using the (localdb)\instance moniker as the server name in your connection string. You will also need to be using VS 11 for server explorer support.

If you need to connect from an earlier framework version you will want to use the underlying instance name which you can find using the SqlLocalDB command line tool:

e.g. run:

SqlLocalDB.exe info "<instance name>"

And then you can use the instance pipe name to connect which will be in the format of np:\.\pipe\LOCALDB#\tsql\query

Jeremy

I have problem with this subject, my code looks like:

var connectionString = @"server=\\.\pipe\LOCALDB#A1E327B3\tsql\query; Integrated Security=true; AttachDbFileName=C:\temp\test.mdf"; 
IMigrationLoader migrationSource = new AssemblyMigrationLoader(typeof(BasicMigrationForUT.BasicMigration).Assembly);
Migrator mig = Migrator.CreateMigrator(migrationSource, ProviderType.SqlServer2005, connectionString, null, false);
mig.Execute();

Result is:

"An attempt to attach an auto-named database for file C:\temp\test.mdf failed. A database with the same name exists, or specified file cannot be opened, or it is located on UNC share."

Is it necessary to create DB file manually? The above code works without "AttachDbFileName" parameter.

Try specifying a Database=[name] to avoid it using auto-naming and also check that the LocalDB sqlservr.exe process actually has permission to create/access that database file. The error message is pointing to more of an access issue, but you can also hit this if you already have an matching auto-named database attached to the instance (the auto-name will just be the filepath).

Jeremy