Windows Integrated account is slow to connect to the SQL server database. - sql

I have a SQL server that belongs to a domain and an application server that is stand alone. Of course it has the right ROUTES to reach the sql server.
when I use a test.udl file to test the connection, a sql login would work right away. But if we try a windows integrated account (servername\username) it takes about 25 seconds to connect.
Unfortunately I have MSMQ running on that server and application that has to take these messages and send it to the SQL server. Because of the delay (I think) MSMQ keeps all its messages.
Do you know what could be the reason for this delay only on WIndows integrated logins?
Note that, I have windows firewall disabled on these servers, No Antivirus.
SQL Server 2008 R2.
Application Server - Windows 2008 R2
Thanks for your time,
RM

Related

ASP development after SQL Server goes down?

Scenario: ISS 8.5 is on our work machines, our Microsoft SQL Server is currently down for an indeterminate amount of time, and we don't have a back-up. We can continue to develop code on localhost. Because SQL Server is down, we can't execute any data transactions. Are there any reliable resources online to, at least, test if the developed SQL syntax is correct?
Edit: I will go ahead and eat my words. I had presumed that we were not allowed to install SQL Server Express locally. That was a bad guess. After I had sent our boss the suggestion from marc_s, he gave us the go-ahead. Now we have a back-up plan. For the record, the SQL Server is now online.
You must have access to another SQL server in order to test code against a SQL server. Your only options are to install SQL server on local machines, install SQL server on a local networked computer, or use a SQL server installed at a third party host.

SQL Server Service Stuck in ‘Starting’ Status

I am not able to connect to the database engine. I have recently installed SQL Server 2012 after formatting my hard drive.
Operating system : Win 7 Enterprise 64-bit
When I try to connect to the database engine :
WN7X64-XXXXXXX, I get the following error message
A network-related or instance-specific error occured. Could not open connection to the SQL Server'.
I tried accessing using (localhost). It did not work.
I tried accessing using (localhost)/SQLExpress. It did not work.
I tried accessing using (localhost)/MSSQLServer. It did not work.
I tried accessing using MSSQLServer. It did not work.
When I checked the services. SQL Server status is starting, and it does not give me the option to start/stop. SQL Server Agent status is blank, when I start the service it gives
Error 1068 : dependency service or group failed to start.
Name Status Startup Type
SQL Full-text Filter Daemon Launcher (MSSQLSERVER) Started Automatic
SQL Server (MSSQLSERVER) Starting Automatic
SQL Server Agent (MSSQLSERVER) Automatic
SQL Server Analysis Services (MSSQLSERVER) Started Automatic
SQL Server Browser Started Automatic
SQL Server Distributed Replay Client Started Automatic
SQL Server Distributed Replay Controller Started Automatic
SQL Server Integration Services 11.0 Started Automatic
SQL Server Reporting Services (MSSQLSERVER) Started Automatic
SQL Server VSS Writer Started Automatic
I sometimes get SQL Server Express stuck in 'starting', in fact, just now, which is why I googled up this page. The solution is to kill the process and restart it.
Simplest way to do that is through Task Manager, which you can start by right clicking the Windows system tray (banner at the bottom of the screen where minised programs go). Processes tab, Sort processes by Name, find all beginning 'SQL...' and stop them.
To restart SQL Server right click the Windows Start button, start Control Panel, Administrative Tools, Services, scroll to all services starting 'SQL...', right click to refresh, and stop any that are running, then start the 'SQL Server' service, followed by any others that are set to Auto or Manual start.
I had the same issue and MSDN Documentation did not help. https://support.microsoft.com/en-us/kb/307288.
It was to do with that there was an orphan Sql related service i.e SqlWriter was hanging around. Go to task manager and killed it. Then the error went away.
To connect to a SQL Server default instance (not Express), you can use:
just a . (dot)
just a (local) (be aware: in round brackets)
just a localhost (be aware: NO brackets)
See the official MSDN documentation on Logging In to SQL Server for more details and explanations, and for even more options how to connect.
Try localhost or (local). Not (localhost).
I had the same issue . go to task manager , search for "SQL Server Windows NT" then end the task . after that , go to your services (Run services.msc) and restart your sql server instance .
Solution works for me in MSSQL Server express edition with Windows 10 environment .

How to find why application cannot connect to SQL Server 2008

Windows application is set to connect to the SQL Server using SQL Server authentication.
When I RDP to the box where the application resides and start the application, it successfully connects to the SQL Server.
When a customer runs the application on his desktop (he is on the network with the application box) and starts the application, connection fails (error. Server does not exist or access denied).
The customer can ping the SQL Server IP in his command prompt.
Yet, when I look at the error log on the SQL server I don't see the logs of his failure to connect.
What could be blocking his access to the SQL Server?
You may have to enable the TCP/IP protocol in SQL Server Configuration Manager - it's disabled by default.

Installed SQL server management studio 2012, but there are no instances running

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.

SQL Server fails to connect to database on client

I have installed SQL Server 2008 R2 Express on a Windows Server 2008 R2 machine, and now when I want to open that database using SQL Server Management Studio on the client machine it fails to open.
But the database opens normally on the server.
The owner of the database is sa and on client I am logged in with windows authentication.
How to resolve this error??
the server priciple smtech/prabhu is not able to access the database
the user is of client under the server domain
I suggest making sure that the account you are trying to connect with actually has access.
Log onto the server, open up management studio, look in object explorer. There should be a Security folder icon in the treeview, Expand that and the Logins folder.
If the user you are trying to connect with isnt present you may need to add it.
Other than this instead of connecting with windows authentication maybe try connect with SQL Server Authentication as the SA user?
Is both Client and DB sever are on SAME domain ?? If not, then I think Windows Authentication will not work for you.
(As already suggested in above answer) create a SQL Login try with to connect DB from Client using that Login.
If both machine are on same domain and still you are not able to connect server, then few things you can check,
Can your client actually "see" this server over network ??
Most common reason is firewall. By default SQL Server communicates from port 1433 and 1434. Try to see if this MSDN link helps
Make sure that your SQL Server instance is configured to communicate using TCP/IP. This can be configured from SQL Server Configuration Manager.