Operating System : Windows 8
Visual Studio installed : 2015 Enterprise Edition
Installed successfully : SQL Server 2008 R2
Installed successfully : SQL server management studio
But while checking the services through SQL configuration manager cannot see the instance server :
"remote procedure call failed"
This can happen if you have more than once instance of SQL installed, I've seen it happen where Express has also been installed on the server.
Browse directly to the correct version of configuration manager here:
SQL Server 2016 - C:\Windows\SysWOW64\SQLServerManager13.msc
SQL Server 2014 - C:\Windows\SysWOW64\SQLServerManager12.msc
SQL Server 2012 - C:\Windows\SysWOW64\SQLServerManager11.msc
SQL Server 2008 - C:\Windows\SysWOW64\SQLServerManager10.msc
Related
I install sql server 2016, sql server 2016 sp1 and it's ssms. but I cant to connect local server. I check services.msc but it contains no sql services like sql server agent , ...
It solved by three steps :
1.Update Visual Studio Installer
2.Update Visual Studio(from VS 2017 build 15.0.0 to build 15.3.0)
3.Repair SQL Server again.
Services added correctly, every thing is fine now.
Trying to install ssms (tried version 2012, 2014 and 2016) on Windows server 2008 R2 with both SQL server 2008 and SQL server 2012 installed on it (using remote desktop). But get following errors:
Error on installing ssms 2016 : The process cannot access the file because it is being used by another process(0x80070020).
Error on installing ssms 2014: Extraction failed, though the file works on Windows 10.
Error on installing ssms 2012 : File is corrupt, but again the file works fine on windows 10.
Is it because of any missing component on sql server 2012 ? Should I repair it or am I missing .NET or any other program ?
I have a microsoft sql server 2014 instance with a database "myDB". In SSMS I have registered this database as Datatier application. I have installed the latest dacfx with nuget to my visual studio project. When I hit DacServices.GenerateDriftReport("myDB") it throws:
Databases registered as a DAC database must be hosted by an instance of SQL 2005 SP4, SQL 2008 SP2, SQL 2008 R2, SQL 2012 or SQL Azure.
Also the method DacServices.Unregister throws this error.
I am installing Windows Server Updates to the SQL Server machine but I don't believe this would fix it.
I've got a fresh install of Windows Server 2008 R2 SP1 and just installed SQL Server 2008 R2, including SQL Server 2008 R2 Management Studio.
When I go into Management Studio, it does NOT show the SQL Server instance that was created during setup. It only has (local) and won't let me connect to it at all.
Any ideas?
First check if SQL Server 2008 instance is installed show on your SQL Configuration Manager.
If it doesn't exist you need to re install you sql server 2008 r2 and follow these steps on this link below:
SQL SERVER – 2008 – Step By Step Installation Guide With Images
And it exist just add server name : yourpcname
Best Regards
Problem solved. Management studio requires <computer name>/<instance name> under the "Server" section. I was only entering in the instance name.
Another solution that worked for me:
enter "localhost" as the server (computer-name\MSSQLSERVER failed)
Not sure why but the name "MSSQLSERVER" as shown in Configuration Manager is not the name shown when I log in via Management Studio. The name in Management Studio is SQL Server 9.0.5000 which corresponds to SQL Server 2005 SP4 (which is correct in my case).
I already had the SQL Server 2008 Express engine installed (just the bit that comes with VS 2008 Express). I then installed SQL Server 2005 Express followed by SQL Server 2005 Management Studio Express, all of which seemed to install OK without any errors. However, when I run SQL Server 2005 Management Studio and enter the Server name as machine name\SQLEXPRESS and click Connect I get the message:
"This version of SQL Management Studio Express can only be used to connect to SQL Server 2000 and 2005 servers".
Presumably the instance name SQLEXPRESS refers to the 2008 version, is the 2005 instance a different name, or is it a different problem? Any ideas please, thanks
You are right that the SQL 2008 Express took the 'SQLEXPRESS' instance name. The 2005 toolset cannot connect to 2008. You need to find out the isntance name under which the 2005 VS installed it's Express. Easiest way is to start the Service Manager (run services.msc)and see the instance name there.
Run "services.msc" and check the service name that is running your SQLServer 2005 Express instance. You should use it, and not "SQLEXPRESS" if it is running your SQLServer 2008 instance.
Btw, SSMS 2008 works beautifully with 2005 instances.
Check this link to download SSMS Express 2008. I'm not sure code completion will work with SQLServer 2005 tho.