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.
Related
I am planning to install the latest version SQL Server Management Studio SSMS 2017 and trying to use the same local server name which was on SSMS 2014.
So I uninstalled SSMS 2014 then install SSMS 2017. After the installation complete, I am not able to login to my local server by using the same credential.
I have checked SQL Server 2017 Configuration Manager, there is nothing under the SQL Server services.
And there is nothing under the registered servers.
Need help to retrieve my local server name, or guide how to recreate a new server name.
Thanks
Currently I am creating SSIS packages for SQL server 2014 using Visual Studio 2012 and the SSDTBI for VS2012.This works well.
But I found some compatability issues with VS2012 for SSIS 2014(on web).I'm new to SSIS.I dont know what is that exact issues with VS2012?.And also they mentioned SSIS 2014 is compatible only with VS2013.Here i have mentioned the link below.
http://www.stefanjohansson.org/2015/02/issues-upgrading-an-ssis-solutionpackage-from-visual-studio-2012-to-vs-2013/
http://blogs.technet.com/b/dataplatforminsider/archive/201
3/11/13/microsoft-sql-server-data-tools-update.aspx
Can anyone tell me what is exact compatability issues for VS2012 with SSIS 2014?.I can not seem to find anything on google.
Thank you
According to msdn it possible.
On an instance of SQL Server 2014, you can import packages from an
instance of SQL Server 2008 or from an instance of SQL Server 2012,
but you cannot export packages to an instance of SQL Server 2008 or to
an instance of SQL Server 2012.
-
Run packages. You can run SQL Server 2008 Integration Services and SQL
Server 2012 Integration Services packages by using the SQL Server 2014
version of the dtexec utility or of SQL Server Agent. Whenever a SQL
Server 2014 Integration Services tool loads a package that was
developed in SQL Server 2008 or SQL Server 2012, the tool temporarily
converts, in memory, the package to the package format that SQL Server
2014 Integration Services (SSIS) uses. If the SQL Server 2008 or SQL
Server 2012 package has issues that prevent a successful conversion,
the SQL Server 2014 Integration Services tool cannot run the package
until those issues are resolved. For more information, see Upgrade
Integration Services Packages.
However, I would just use VS 2013 if you can.
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 have Installed Microsoft Visual Studio 2012 (Ultimate) , and it installed all the SQL files,
yet I can't find the SQL Server Manager in the Start Menu, like the old version, so I can't start the services, , or there is an other way to run the services, so I can connect to the SQL Server?
In Run window, type "C:\Windows\SysWOW64\mmc.exe" /32 C:\windows\SysWOW64\SQLServerManager12.msc. I did come across the same problem (Sql Server Configuration Manager is not in start menu) before, and I had to pin it to task bar.
SQL Sever 2012 service are installed via Microsoft® SQL Server® 2012 Express as VS 2012 does not install it unless you are using custom installer..
Once you install Microsoft® SQL Server® 2012 Express in your machine you can use SSMS and other tools to manage SQL services on your machine.
Use 'sqlserver.exe' to start SQL Server from the command line - MSDN reference here. Or you can download SQL Server Management studio as shown below - from this link.
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.