localdb

问题 We are currently using SQL CE 3.5 with many different bidirectional sync dbs ( Syncframework 2.1 ) with server DBs, and .net 4.5 windows based WPF application. But down the line the performance of the application degrades and we regularly need to regenerate the new local SDF for users. And by that way we see there is visible improvement in performance and after 60 days or so, the same happens. So we are looking for upgrading the SQL CE , but on research, we noticed that SQL CE doesn't support

问题 So..I managed to almost finish all my problems.But now i deal with another one. I used this connectionstring : SqlConnection con = new SqlConnection(@"Data Source=.\SQLEXPRESS;Database=Database1.mdf"); And it throws the next error: Login failed for user ' If i remove the .mdf extension it throws the same error Now if i'll add the following to the string: Integrated Security = true It throws this: Cannot open database "Database1.mdf" requested by the login. The login failed. Login failed for

问题 I tried to start an instance of SQLLOCALDB 2017 on win7 (x64) but this message box Appears : "The procedure entry point BCryptKeyDerivation could not be located in the dynamic link library bcrypt.dll" Anybody knows it's reason? more info from CMD: Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Users\hashem-7-x64>SQLLOCALDB INFO MSSQLLocalDB C:\Users\hashem-7-x64>SQLLOCALDB VERSIONS Microsoft SQL Server 2017 (14.0.1000.169) C:\Users

问题 I'm looking at using SQL LocalDB as the client side database which will replace the current SQL CE 3.5 database inside an in-house application developed in .net 4. I've come across a problem that I'm not sure how to get around and that's with security setup of the LocalDB instance. If I setup a script inside .net to create a private LocalDB instance, e.g. (localdb)\T1, then create a new database inside that instance plus add a SQL user account + password (non domain account), how do I stop

问题 I'm using SQL Server LocalDB for a website. SQL Server LocalDB is installed and a database is created during Setup. A shared instance is created via LocalDBCreateInstance, StartLocalDBInstance and LocalDBShareInstance. The website can successfully connect to the database if the instance is started. However, if the instance is stopped, it is not automatically started. Accessing the database (when instance is stopped) from a console application causes the instance to be started. So this seems

问题 I recently installed VS2015 Update 2 on two different PC, one at home and one at work, with the same installer file. Now if I open a project with Sql LocalDB on my own PC, I obtain this error: The database 'M:\PROJECTS\BLOG\APP_DATA\myBlog.MDF' cannot be opened because it is version 851. This server supports version 782 and earlier. A downgrade path is not supported. I cannot retrieve information about this 851 version (maybe Sql LocalDB 2016?). I'm sure to have Sql LocalDB 2016 RC0 on both

问题 According to this answer, SQL Server Data Tools uses a private LocalDB instance ProjectsV13, which you're not supposed to use for your own applications. Instead, you should use MSSQLLocalDB or your own private instance. Is this documented anywhere? What does SSDT use its private instance for? (I don't see anything in mine.) Is a private LocalDB instance basically spinning up a second copy of SQL Server? On the surface, it sounds rather resource intensive to have a dedicated database engine

问题 Our application uses SQL Server LocalDb 2014 as the database engine. The connection string we use is "Data Source=(localdb)\MSSQLLOCALDB;Initial Catalog=OurDatabase;MultipleActiveResultSets=True;Integrated Security=True;AttachDBFilename=|DataDirectory|OurDatabase.mdf" Now, on just one of our computers, it has VS 2015SP3 and the latest version of the SQL Server objects installed, our application starts using SQL Server LocalDb 2016. This is undesirable as we exchange back-ups of the database

问题 I have a MVC4/ASP.Net application that uses localdb. Everything "appears" to work correctly. However I am getting loads of errors in my event log: The "DataDirectory" registry value is missing in the LocalDB instance registry key: {BB3F4304-E7E9-4EE7-9A25-B46BFAA73FB4} The "DataDirectory" registry value is missing in the LocalDB instance registry key: {BB31321B-BEB9-465B-8C8E-DEF9C2C67FBE} Each time the instance changes. XML Detail of the error: <Event xmlns="http://schemas.microsoft.com/win

问题 I'm trying to deploy a DACPAC to LocalDB 2012 but it's just not having it: Stack trace is as follows: ================================== Could not deploy package. (Microsoft.SqlServer.Dac) ------------------------------ Program Location: at Microsoft.SqlServer.Dac.DeployOperation.Microsoft.SqlServer.Dac.IOperation.Run(OperationContext context) at Microsoft.SqlServer.Dac.OperationExtension.Execute(IOperation operation, Action`2 reportStatus, CancellationToken cancellationToken) at Microsoft