I just installed SQL Server Management Studio, version 18.9.1, on a Windows 10 system. The installed Management Studio cannot discover known SQL Server databases out on the network, so I cannot log into a SQL Server using SQL authentication.
Please note, the target SQL Server has been installed for a while, and is running fine. I am trying to access this SQL Server from a new workstation.
The SQL Server Browser is running on the SQL Server I am trying to reach.
I am confused as to what should be installed if what I installed is not correct. I'm also confused as to which services to check are installed after installation. It doesn't look like a SQL Agent or locator service was installed, after I installed SQL Server Management Studio.
Am I better off installing a development database and just not using it in order to get the locator service?
Related
I have installed an application which creates SQL Server 2008 instance for its usage. The software and server and not communicating. Actually software is unable to connect to instance.
In the investigation I have found that the SQL Server instance created by software is stopped. I tried to start the SQL service through configuration manager but it is not getting started. I am unsure whether SQL Server 2008 express is compatible with Windows 8. Please help.
I freshly installed Microsoft SQL Server on my machine and started it. When I try to connect to a server I use a . for the server name (which should point to the local machine from what I read?). However I get the following error:
So I went to the SQL Server Configuration Manager and checked under SQL Server Services, which seems to be empty.
How can I establish a connection?
Your services are not running.
Make sure you installed this.
The above answer was correct, however, you only installed the SQL Server Management Studio.
If you installed Express, downloaded from the Microsoft website you might want to download and create the server instance with the management studio. You will need to select if you want Windows authentication or SQL Server authentication using a username and password. Remember to add the current windows user for using either.
Here is SQL Server 2014 Express: http://msdn.microsoft.com/en-us/evalcenter/dn434042.aspx.
This will download everything you need to connect to a server.
Please let me know if you need more information.
I dont know much about sql server.
I have just re-installed windows 7 on my laptop. After that I installed Visual Studio 2012 Express Edition. I also Installed SQL Server Management Studio 2008 R2.
Now when I try to log in to sql server management studio by using server name as . or (local) or .\SQLEXPRESS or PC-Name\SQLEXPRESS and using Windows Authentication I get the error as below.
Please dont mark this question as negative as I have searched on google for last 4 hours but did not understand the problem.
Update:
There are many reasons that may cautioning the problem:
SQL Server is not running
SQL Server is not properly configured
You try to connect with a worng instance Name
You can try the following:
Go to Mycomputer->Rigt Click->Manage->Application and Services
And from there check that SQL Server Express is running
2.From there also, gCheck the Instance name of your SQL Express and be sure when you log on to Management Studio you Provide the same Instance name
Confirm that the service is installed and running. Under Computer Management, drill-down into Services and Applications -> Services.
There should be a service named "SQL Server (SQLEXPRESS)". Try a restart or start of the service.
If any other instance of SQL Server is installed it will be listed - try connecting to LOCALHOST(whatever the instance is listed as) to verify the installation is functional.
UPDATED following further information from comments:
You may have only installed the client tools (management studio), and have not installed the database service. Ensure you have the correct installer which includes the database services engine.
First check that the SQL Server parameters are set accordingly.
Go to Start -
All Programs — Microsoft SQL Server 2008 R2 — Configuration tools —
SQL Server Configuration Manager
Under SQL Server Services, make sure that the instance is running :
SQL Server ()
SQL Server Browser
Under SQL Server Network Configuration - Protocols for (), these are enabled:
TCP/IP
Named Pipes
Do the same under SQL Native Client 10.0 under Client Protocols
I need to deploy a WCF service with a database on client machines. I am confused about SQL Server Express. I need to verify all of the following.
When attaching database files in the App_Data folder, do I still need to install SQL Server Express engine (Windows service) on client machines?
There is a flavor called SQL Server Express LocalDb. That one does not need an engine (Windows service)? But I think it need a prerequisite installation of LocalDb.
Localdb is introduced with SQL Server 2012. There is NO localdb for SQL Server 2008. Correct? I could not find 2008 version on MS site.
Do I still need to install SQL Server Express engine (A win Service)
on client machines?
Yes, they need it installed for your application to query the database. Can't really get around it.
There is a flavor called SQL Express localDb. That one does not need
an engine (win service)? but I think it need a perquisite installation
of localdb.
Yes, you'd still need to install LocalDB on the client machine. It's pretty hassle-free to do, but I think it's overkill unless you really need the full features of a SQL Server instance for your webservice.
Instead of LocalDB I'd strongly recommend using SQL Server Compact Edition - it performs the role you're thinking of (your WCF Service can simply connect directly to the database file on your client machines without installing SQL Server, and is lightweight), but doesn't need to be installed (it's simply included as a DLL with your WCF application):
Unlike other editions of Microsoft SQL Server, SQL CE runs
in-process with the application which is hosting it.
In Microsoft's own words on the differences between LocalDB and SQLCE:
LocalDB and SQL Server Compact?
Small and simple database, lightweight installation, connecting to a
database file -- this will sound familiar to any developer using SQL
Server Compact. The similarities are not accidental, as our goal for
LocalDB was to be as easy to use as SQL Server Compact (while being as
powerful and compatible with full SQL Server as SQL Express).
There are significant differences between LocalDB and SQL Server
Compact:
Execution mode: SQL Server Compact is an in-proc DLL, while LocalDB runs as a separate process.
SQL Server CE is kind of like an updated version of MS Access, the file goes with the application which can "just connect" to the database file without involving any database server installation, and its syntax/features are very close to SQL Server standard.
I cannot get my local computer to run SQL Server. I looked in the SQL Server configuration manager and noticed that there are no SQL Server Services listed. That can't be right. I also noticed that There are two Managers listed in the SysWOW64 folder (I'm running Win7): SQLServerManager10.msc and SQLServerManager.msc. Neither show any services at all. When trying to connect via SSMSE, I get the standard:
A network related or instance specific error occurred while establishing a
connection to SQL server...
I haven't installed a prior version, but did try to uninstall and reinstall using the Web platform installer from Microsoft. Any suggestions?
Thanks
I had the same problem and as Brian said, I was missing SQL Server Express. So I download SQL Server 2008 R2 Express and I installed it. now everything works fine.
Note that I thought I already installed it when I installed SQL Management Studio R2. Now, be aware that when installing SQL Management Studio R2, you are not installing SQL Server and you won't get any SQL Server Services in your Sql Server Configuration Manager -> SQL Server Services. You also need to download and install SQL Server Express.
Is SQL Server listed in services? (Start->Run->Services.msc)
If so, is it running?
That is an instance error, meaning you cannot connect to the instance. Most likely there is no instance installed on this machine. Meaning your not connecting correctly to the instance. Connect to the database engine again and check the server name and make sure your connecting to the correct server name or the local host, depending if this is a local machine or if this is on a server. Go back through setup and see if there are any features that didn't get installed. Try that and see if it works. If not then reinstall SQL Server and make sure all folders are removed and nothing is left behind before you reinstall.