I am migrating my Webappserver from SQL2012Express to SQL2016Enterprise.
for this I have installed a Windows server 2016 with IIS10 my current IIS db connection String is
"data source=.\SQLEXPRESS;Integrated Security=SSPI;AttachDBFilename=|DataDirectory|aspnetdb.mdf;User Instance=true"
this is on Windows 2008 and IIS 7 with SQL 2012 Express.
Now on the new webappserver my source is no longer SQLexpress since the SQL is enterprise not express. my instance name was SQL2012 I changed it to Sql2016 in my Software's web.config and IIS as well I am not able to connect my software to the Database.
Here is what my current Db String is on the current webappserver.
My SQL management Studio is
On the New Server My ISS db connection string is the same which is express?
and my SQL Studio properties are
My connection string in my MVC app web.config file is
I hope I am giving you enough information to help me on this challenge I am facing.
This is my first time migrating SQL server and I am sure I have create the instance correctly.
my connection String to the site on IIS is
data source=.\SQL2016;Integrated Security=True;App=Worldwide;Initial Catalog=Worldwide
Any Help is very, very appreciate it.
Thank you.
Related
Will database security configurations (Logins etc.) persist through upgrade from SQL Server 2014 Express to SQL Server 2017 Express?
I am running a database instance on SQL Server 2014 Express edition and would like to move to the SQL Server 2017 Express edition but I fear that security credentials might get lost.
This is a production environment so I'm assuming someone will answer that I should do a test environment which I'm unsure how to setup. Without testing would I need to worry about any security information being reverted? I've tried to backup and restore the database to a separate instance of SQL Server 2017 evaluation but the security information had to be redone of course and the users were able to see the instance but not the database within. Any thoughts?
First time asking a question on here so don't kill me if I didn't follow a certain protocol
I've ran the upgrade of the SQL Server from the 2014 version to the 2017 version and I can confirm that security configurations are transferred over to the new version. As well when you upgrade your edition of the server security configurations also persist.
I have a phone server running Window Server 2008. The server software is currently using Microsoft SQL Server 2012 Express Edition. I created an IVR application that has created a second database using the same SQL Server instance.
I found out post-development that the version of SQL Server installed on the server was Express and NOT Standard like I had thought. I checked the SQL Server Configuration manager and noticed that the instance is MSSQLSERVER, but it is running express. The phone system software I am using is proprietary and I cannot get in to change/modify connection strings.
My question is:
Is it reasonable to assume that upgrading from SQL Server 2012 Express to SQL Server 2012 Standard is safe? Does upgrading change the connection string, or instance name? Or is there anything I should be aware of during the upgrade? Or would it be better to just run Standard alongside Express?
Thanks!
I have read various articles saying that the connection string doesn't change, but I would like some input from someone who has actually upgraded from Express to Standard.
Problem
I have a webproject that uses Fulltext-search, that I imported to a new computer (virtual machine).
I get a warning, when opening the website in Visual Studio, saying:
"The Web project xxx requires SQL Server Express, which is not installed on this computer. The recommended database engine for Microsoft Visual Studio is SQL Server LocalDB Express..."
Old computer setup:
SQL Server Express with Advanced Services (I think it was 2012).
Visual Studio 2012 Ultimate installed.
New computer (VM) setup:
SQL Server Enterprise 2012 (from DreamSpark).
Visual Studio 2014 Professional.
How i'm trying to resolve it:
I tried to modify the connectionString, but I couldn't find the right SQL db engine in Advanced Properties:
How do I get the right engine to show up here?
I have been searching through SO and found a connection string that seems to be what I need.
However, it does not work.
I use SQL Server 2012 Express and I need my application to connect (with no credentials). I am using the following con.string:
Server=(localdb)\\SQLEXPRESS;Database=MyDB;Trusted_Connection=Yes;
However, the server does not respond.
You need to either use the proper SQL Server Express - then use this connection string:
server=(local)\\SQLEXPRESS;Database=MyDB;Integrated Security=SSPI;
(use just (local) - not (localdb))
or you use LocalDB (which is a "run-on-demand" version of SQL Server Express), in that case, use:
server=(localdb)\\v11.0;Database=MyDB;Integrated Security=SSPI;
The difference:
SQL Server Express proper is a server-based solution, which is installed and runs as a Windows service all the time
SQL Server Express LocalDB is a run-on-demand version of SQL Server Express, which only gets started up when you need it (e.g. in debugging inside Visual Studio 2012/2013)
I have SQL Server 2008 Express and SQL Server 2012 Developer edition installed.
When I want to connect to SQL Server from Visual Studio 2010 I have only option to connect to VISTAUSER-PC/SQLEXPRESS but I know that the name of 2012 Developer edition is VISTAUSER-PC so I just write that name, test connection and its working.
DotNetNuke just gives me option to connect to express edition and when I enter VISTAUSER-PC for the name of the server it cannot connect. I know that DNN works with SQL Server 2012
http://img825.imageshack.us/img825/7582/captureqnn.jpg
If your DotNetNuke install is on the same box as IIS/SQL2012/VS2012 then you just select "SQL Server 2005/2008 (Express) File".
You need to make sure other SQL instances, except SQL 2012, are NOT running on your machine when you do this....
DotNetNuke ships with a database.mdf file which is used by default by SQLExpress.
To recap..
Do not edit your SQL connection strings in your web.config
Stop any other SQL instance but SQL2012
Select the radio button beside "SQL Server 2005/2008 (Express) File".
I have noticed that SQL2012 uses a different account to run under so you may need to go in and change to "Network Service" so you can cleanly connect to SQL20102
Good luck...