I have both a laptop and desktop computer for development on both of which I have installed Visual Studio 2015 Express for Web. I'm developing an ASP.Net MVC application with Entity Framework code-first.
On the laptop, I was able to add a SQL Server LocalDb database file to the App_Data folder, however when trying to open the database on the desktop machine (with the same version of Express 2015 for Web installed - from the same installer), I get error messages saying something along the lines of:
The database file you are attempting to connect to is not compatible with the current instance of SQL Server. To continue, you must upgrade this database file...
Having been through this loop several times with endless issues relating to compatibility of LocalDb databases between workstations, I'm getting a bit fed up. Every time I've had compatibility issues between machines whereby I've upgraded the database only for the other workstation not to be compatible with that version.
My question is: is it worth persisting with LocalDb or should I just move the database across to SQL Server Express and be done with it? I like the idea of LocalDb as I can keep the database in the solution.
Related
We are planning to upgrade our SQL Server 2104 to SQL Server 2016.
Our SQL Server is in a clustered setup, and infrastructure is planning to do a side-by-side upgrade (where they will spin up new windows server machines and move resources from old machines to new machines).
We have 99% SSIS packages stored in file system, and 2% in SSISDB (Integration Services Catalog).
We have SSRS reports too.
What should be our approach towards SSIS packages and SSRS reports, while SQL Server is getting upgraded.
Should we copy the SSIS packages to Visual Studio, and change TargetServerVersion, and paste back to the folder location?
Should we copy report server databases (2 of them) and database encryption key to new machine, and spin up new SSRS along with existing URL.
In your situation, the best is to add all the existing packages in one project and upgrade the project.
In the development studio for SQL Server 2016, this is really interesting feature that you can upgrade as well as downgrade existing projects.
Project Properties Dialog
Post upgrade tests your packages in lower environment, the only challenge could be any .net code tasks if used. sometimes code is not upgraded to the latest version.
For report server your strategy is fine.
List item
I have a WPF project and I will use SQL Server database. The instance of SQL Server IT created for me is SQL Server 13 (2016 standard version) on a remove server. When I’m deploying the application on a client’s computers, what version I need to install there as a prerequisite? Can I deploy SQL Server Express 2016 on a client’s computer and access the remove SQL Server Standard edition? I am looking for a simple solution and for a lighter version I need to install on the user’s computers. I cannot install a full SQL Server on each user.
I have searched the net and a similar question has been asked many times, but I didn’t find a clear answer before. Many people started their SQL Server experience using local type databases, like SQL Server CE or LocalDB. In this case specific DLLs and redistributables must be added with the installation program. It is hard to understand at the beginning, but when an instance of SQL Server is on a remote server, this is a different story. Everything is happening on this remote server. There is no need of any SQL Server instances on a client’s machine. Just a connection string must be added. The adapter or Entity Framework will take care of everything else.
I am developing with BizTalk for the first time. I have created an extremely basic project in VS2103 which builds but fails to deploy with the output:
error DEPLOY: The database or the database version is incompatible with the installed version of this product.
The BizTalk installation is BizTalk 2013 R2 on a SQL Server 2012 SP3 database.
My project is using VS2013 because I understand that VS2105 can't be used to target BizTalk 2013.
There is no further information in the output window. I have a valid login on the database and can perform CRUD operations on it through VS2013.
This page suggests I need "SQL Server Development Tools" - am I right in assuming this means "SQL Server Data Tools" because that's all I seem to get when I search for it.
Even a pointer to where I can find a more more informative error would be useful (perhaps unsurprisingly changing the build verbosity only affects the build output when what I'd like is a more informative deploy output!).
Apparently this issue is related to the OS - BizTalk 2013 (or some other element of my setup) isn't compatible with Windows Server 2012 R2. Downgrading to R1 isn't an option the security team will allow. Upgrading BizTalk means upgrading SQL Server means upgrading some other software we have running on it so that's not going to happen any time soon. Looks like it's time for me to move to Azure!
I installed VS 2008, VS 2012 and the community version 2013 along with the matching SQL Servers but never needed the SQL Servers and never checked if they were properly installed.
I recently picked up SQL Server Management Studio and tried to connect to a server.
Unfortunately, it does not detect any local server, even though I have about twenty different entries in programs & apps for SQL Server related stuff including SQL Server 2012 and 2014 Express Localdb, an installation of SQL Server 2008, data-tier app frameworks, native clients, transact SQL, a couple "compact" versions, tools and what's not.
One would think that something in this mess would be recognized as a server, but apparently not so. I had an entry for SQL Server in the start menu with a nice GUI with an install DB option... that requested a server media folder (lord knows which). I tried starting manually one of the many SQL Servers (sqlservr.exe) from the program files folders to no avail (I get a message about a corrupt installation)
My DB experience is pretty much exclusively with MySQL and I am lost with all these applications that look like they should do something but don't.
I would like to have a bare bones installation that works for the following use:
Coding Winform apps with local databases (compatible with Entity Framework)
Allows to distribute the apps with local databases for free (commercial use, small data volume)
Running SQL queries from SQL Server Management Studio
What is the minimum I need for this purpose?
Should I uninstall all the existing SQL Server related programs and make a clean install from a single install file (for instance, would installing the 1.1gb SQL Server 2014 Management Studio Express 64 Bit.exe give me all I need)?
Or if not, is there any way to install a recent version and ignore the underlying mess? (I don't really care for the disk space, I just want this thing to work).
I apologize if this question is a mess but I am pretty confused with this, and I could really use a hand figuring out what's what.
I'm working on a winform application using VS2012 (.NET 4). I use SQL Server for my database affairs, I can run this application smoothly on my development systems (which have VS 2012 installed) but when I give EXE and my MDF files to someone who don't have VS2012 installed, they get an SQL server exception (also program runs but they cannot use database features), I think problem is that they don't have SQL server installed, how can I solve this problem? what should I give to my users? Is there any difference between Debug and Release versions? I deploy Debug EXE which runs but as mentioned SQL server features are not usable