So, as it says, I installed sql server (2012 express), and during installation I checked the option LocalDB. Now I'm trying to connect to the database engine, but can't. I've tried connecting with windows authentication (to local, and localhost), with sa-user and no password and a bunch of other stuff.
When I visit the configuration tool and try to se what my instance is called, I see a new problem. There's nothing running at all. Under SQL Server configuration manager (local) --> SQL Server Services there's nothing.
What am I missing? Obviously I've missed som step where I start something up, but for the life of me I don't know what.
Help!
just use localhost\sqlexpress with Windows Authentication
You can also Try .\SQLExpress
http://www.stratospher.es/blog/post/connecting-to-localdb-with-sql-server-management-studio-2012-ssms
LocalDB doesn't create any database services; LocalDB processes are started and stopped automatically when needed. The application is just connecting to "Data Source=(localdb)\v11.0" and LocalDB process is started as a child process of the application. A few minutes after the last connection to this process is closed the process shuts down.
I had the same issue and was able to connect using (localdb)\v11.0 with Windows Authentication.
Related
I am new to Team Foundation server and when I am configuring TFS for SQL Server, I am getting below error where TFS is not able to connect to the SQL Server instance where as when I connect to SQL Server it is connecting successfully. Both SQL Server and TFS are on the same server machine. Please advise
Error while clicking on Test Link
According to the error info, you need to make sure the TFS service accounts(which you started the TFS Installer) have permissions on the DB server.
Add the account in the list of logins in SQL Server side and retry
the previous operation.
Moreover, if Windows Firewall is on the TFS box, switch it off during the installation and try again. After finish the installation reopen the firewall.
For more details you could take a look at below similar issue:
Errors during TFS 2013 install–and how I worked past them
Workaround Error TF255049: Punching a hole through Windows
Firewall
I installed SQL server 2012 developer addition.
My windows is working on Parallel Access installed on MAC.
When I tried opening SQL server, It initiated a call to connect to server. And when I clicked on connect it gave me error.
I've never installed SQL server 2012 in my personal PC. WHen I was installing I chose Windows authentication mode and user ROMANCH9326 came out automatically.
Please help me, I'm clueless about this problem.
TITLE: Connect to Server
Cannot connect to ROMANCH9326.
ADDITIONAL INFORMATION:
Login failed for user 'ROMANCH9326\romanch'. (Microsoft SQL Server, Error: 18456)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&EvtSrc=MSSQLServer&EvtID=18456&LinkId=20476
On Start > Search type "sql configuration"
Open SQL Configuration Manager
SQL Server Network Configuration >Protocols for [SQLINSTANCENAME]
Check if Named Pipes is enabled, enable it if not.
Restart your SQL Server Instance.
Well This is a pretty silly solution but when I tried repair function on SQL server it said that my Database Engine libraries were not installed properly somehow.
So I reinstalled the software and now it worked just fine. I was able to log in.
Thanks :)
I've just built a new dev machine and I can't get SQL Server Agent working. What I've done so far:
Install VS 2010 (I think this installed an express version of SQL Server)
Install SQL Server 2008 R2 Developer edition.
I'm not sure if I did something wrong in step 2. All I want is a fully working version of SQL Server with SQL Server Agent running and no limitation on the amount of data I can store (I will need more than 10GB).
Currently, in SSMS I have the following instance: ./SQLEXPRESS. I thought that during step 2, this would have been upgraded, but it doesn't seem so.
Can anyone help?
Note: I ended up resolving this by uninstalling everything that had "SQL Server" in it in Control Panel > Programs and Features. I then reinstalled from scratch.
Note: I ended up resolving this by uninstalling everything that had "SQL Server" in it in Control Panel > Programs and Features. I then reinstalled from scratch.
The agent account is disabled. If you aren't able to enable it through configuration manager, try enabling it through services. After its enabled, try starting the serivce. If you still have issues starting the agent, try changing the account the service is running under. There may also be an issue with the account that the SQL Server service is running under. Trying changing the SQL Server service account and restarting it. The agent should then start up successfully.
You have two installations, with two named instances. The Express named SQLEXPRESS and the developer edition named MSSQLSERVER (unless you changed this during install). connect to .\MSSQLSERVER and see, it should be there available to be started.
SQL Server Express does not ship with the SQL Server Agent.
I've just started work on a new computer in which I had to download all the software fresh.
I've just download a copy of SQL Server 2008 R2, and I'm trying to connect to SQL Server Management Studio without success. I vaguely remember last time I installed this, it asked me to choose between windows, or sql server authentication, however this didn't happen for this installation.
If I try to login via Windows Authentication (where the username and password fields are greyed out, localhost as server name) it gives the following error:
"A Network-related or instance
specific error occured while
establishing a connection to SQL
Server. The server was not found or
was not accessible. Verify that the
instance name is correct and that SQL
Server is configured to allow remote
connections. (provider: Named Pipes
Provider, error: 40 - Could not open a
connection to SQL Server) (Microsoft
SQL Server, Error: 2)"
I have checked everything in SQL Server Configuration Manager, and everything bar VIA is enabled.
If I try SQL Server Authentication, It asks me for a username and password which I definiately have not set yet. Also, under SQL Server Services in configuration manager, there is nothing there.
Any help would be appreciated :)
Thanks
PS: I don't know if it's worth mentioning but I am running Windows 7 as a virtual machine on a Mac.
Are you sure you have the correct instance name? If it was SQL Server 2008 R2 Express Edition then the default instance name is .\SQLEXPRESS.
Also if your using sql authentication to connect try running sql management studio as admin, if you are a limited user your identity might not be mapped to an account in sql server yet but i believe the Administrators user group is.
You need to check if your services are running.
Please type
net start mssqlserver
in your command prompt. Then try to login.
Ended up reinstalling completely and doing a fresh install from a fresh download. When I did this I was brought through the steps of selecting the default instance, and selecting authentication modes.
Working fine now :)
After checking tons of sites looking for an answer to this question, I think I have a simple solution.
Open the sql Server Configuration
Click on the sql server services node
Right Click on Sql server
Click Start.
I have been screwing around with this forever, and this simple method actually worked.
I am sorry if this sounds like a silly question, but I have googled for a while for a solution and no success. I am trying to establish a connection from VS 2008 to SQL Server. I am trying to use an user that my web application has been successfuly using to access the database from in its connection string. But when doing it from VS 2008, it tells me "Login failed for use 'xxxxxx'". I am currently in the "Add Connection" window. I have chosen the datasource and server name, fulfilled username and password for SQL Server Authentication. Do I have to set specific permissions for this user? Do I need to allow a VS 2008 user in SQL Server? Thanks.
I have found the solution for this problem. My Visual Studio would pull automatically something like MACHINENAME\SQLEXPRESS. As it was pulled automatically, I did not bother taking a closer look at it. I finally realized the connection string that worked for me in my other application was .\SQLESXPRESS. When I entered it in Visual Studio, it did work. Thank you all for the help.
Do you have SQL Server Management Studio Express Installed? if so try connecting as the same user through that interface. This will isolate your problem a bit.
With Visual Studio, you're connecting through a "remote" connection, even though they're on the same machine. With Server Management Studio, you're connecting through a named pipe probably. You need to change the SQL configuration so that it allows remote connections. Here are instructions for how to do it.
You can test your SQL connection by connecting using LINQPad, Often find this solves problems with connections to new SQL Server instances at my workplace.
http://www.linqpad.net/
Are you trying to specify the username and password to connect with in the connection string - ALA:
Data Source=myServerAddress;Initial Catalog=myDataBase;User Id=myUsername;Password=myPassword;
This actually uses SQL Authentication, not Integrated (Windows) authentication. What you might be looking for is this:
Data Source=myServerAddress;Initial Catalog=myDataBase;Trusted_Connection=True;
This would log into the database as the use running Visual Studio. Notice that the username/password aren't specified here - it uses the current Windows identity - in your case, that's the user running Visual Studio.