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
Related
I have an old 32-bit application sitting on a sql server 2000 personal edition windows NT 6.0 service pack 2.
I am performing a side-by-side migration
I was given a windows 2016 x64.
I installed SQL Server 2008 developer edition x86
I backed-up and restored the necessary databases, changed compatibility level, move logins and permissions, move over necessary extended stored procedures.
ISSUE: The application throws an error when trying to connect. 'Could not load the DLL C:\Program Files (x86)...applicationspecified.dll, or one of the DLLs it references. Reason: 126(The specified module could not be found.)'
I did check to confirm the path is correct.
I used dependency walker to see if there were any missing DLLs
EDIT: The app was installed on the new windows server (2016), opening the app while on windows 2016 against old database/sql2000 works fine. Opening the app against the new databases/sql2008 fails.
I am currently trying to install SQL Server 2017 Enterprise on Windows Server 2016 Datacenter.
When the installation reaches "Install Setupfiles", the window freezes.
I have tried to install SQL Server 2016 Enterprise and SQL Server 2016 Developer, but no difference.
I also have installed .Net Framework 4.7 to meet the requirements of the setup, but nothing changed.
There is also no information from the setup, despite the fact that it skips downloading and extracting the installation files (which is fine, due to the fact that I downloaded a full ISO), but it also skips "installing installation files".
Did I forget any crucial software or setting ?
Did anyone face the same problem ?
Best regards,
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 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.
This question may seems a bit silly. The thing is I'm programming a WPF using VS2010, which contains a .sdf database (connection is ADO.NET).
Someone told me that if I use a SQL Server Express database it can be run on any PC even it has no SQL Server installed. But after I tried executing in my virtual machine (win7 & win xp), seems it cannot even start up.
So, can someone brief me, what database do people normally use in developing WPF software? Is it true that my program using a SQL Server database file cannot execute on PC without SQL Server installed?
Much appreciate in advance!
Yes, it can!
SQL Server Compact (that produces and uses .sdf) is the only SQL Server edition that does not require a server to be installed. All its code and logic is contained in the handful of DLL's that you need to include with your application. Just ship your app with those DLL's and you should be fine.
Read more about SQL Server Compact and how to use and deploy it on MSDN.
SQL Server Express (and any of the other editions, like Web, Standard, Developer, Enterprise) on the other hand does require an installation of the SQL Server Express edition - either on that machine, or somewhere in the network where your app runs (remote connections from the network are disabled by default, but can be enabled).