110
I upgraded my SQL server and inadvertently created a named instance. Not noticing I updated my databases and installed SL 2015. Everything works fine logged in locally on the server, but when I login on a client workstation I need to use the named instance for the server name. I can then select my System db, but when I choose the application db I receive an error saying the db is not associated. Any Suggestions?
*This post is locked for comments
Every time I logged into DB maintenance it would change from the <server name> to <server name\named instance> so, I ended up uninstalling the named instance and installing a default instance. This included removing the named instance as the default setting from the SQL registry settings.
I used the same domain admin login on both the server and the client. Both members of the same domain. And, yes the login is also in SQL security logins.
I copied the info below from an older support incident:
Create a new SQL server instance on the same server and put the 2011 Databases there. A new SQL Server instance should behave as if it were a totally separate SQL server. When you log into DB Maintenance just log into ServerName\InstanceName to access 2011. This is one way to be sure that your sync process won't have a negative impact on your Databases.
I have not run into a need for using a SQL instance other than the default with SL2015.
If using Windows security, are you using the same domain user on the workstation as the installing user account / dbo on the server? Your description sounds similar to where the user attempting to login isn't defined as an SL user, so you couldn't get past the System DB login. You can check SQL security to confirm the domain users have access to the SL databases on the new instance.
I changed the servername in domain and checked the vs_servername. However, when I ran the security sync in db maint. they were reset to just the servername without the instance name.
Have you updated the SERVERNAME field in the System database - DOMAIN table to reference the server using the naming format used for the SQL instance? After updating that field, I'd expect you will also need to run the SL Database Maintenance scenario for updating views.
#1
Community Member
136
#2
Mohamed Amine Mahmoudi
102
Super User 2025 Season 1
#3
REUser
8
Share
Report
All responses (
Answers (
