I have experienced a weird issue a few hours ago and i cannot seem to figure out what has caused this problem.
I have SQL server 2012 installed on a windows server 2012 virtual machine.
I have windows services, Windows applications and web sites accessing a database on this server.
all applications lost access to the database for +/- 10 minutes and it suddenly just came back up again.
during that ten minutes i managed to log onto the SQL server remotely and open management studio and access all the databases but the applications still could not connect.
The database did not go into single user mode, the CPU and memory was normal, i could ping the server from my desktop.
I looked at the event log and SQL logs but couldn't find anything related to why the database could not be accessed.
I am baffled I've been trying to figure this out for the last 2 hours and i not getting anywhere.
I would appreciate any assistance
Thanks
run the dbcc checkdb command. This will check the database and tables for any corruption/errors.
Related
My company looks after a server which is running SQL Server 2014 Standard Edition. The main application database on the server is replicated out to about 20 subscribers. The server has only been in operation for about a week and at the time of setting it up we moved the existing database and replication across from the old server. At that time we also changed the recovery model from Simple to Full.
The performance of the server hasn't been particularly good so far, even though it has 24 logical processors and 32 GB of RAM. However it seems to be SQL Server that has been performing badly due to locks etc. according to the event logs.
This morning we couldn't access any tables in Management Studio and after a period of time we decided to try restarting the service. The service did not seem to stop properly and we were forced to restart the server. After restarting the server everything seemed fine until we tried to expand out the 'Databases' tab in Management Studio. It just says 'expanding...' in the UI and after several minutes brings up a timeout error message. After clicking ok on this message we can browse all the system databases as normal but the main application database is not shown.
One of the problems that has come to light is that the log file has grown extremely large (over 1 TB).
This is a major problem now as you can imagine, since we cannot connect to the database to shrink the log file and no applications can connect to the database Connecting to the database using 'sqlcmd' doesn't work either. We can't 'open' the database.
Look forward to hearing if anyone has come across this before and knows of a solution.
We have two servers - One Windows 2012 server as a web server and one Windows 2012 server as a SQL server (Web Edition)- using the private IP address between them. We have production sites running on this platform fine using reasonably small databases etc.
Today we moved another website over to this setup. The site was running on a Windows 2003 server with a SQL 2008 Server (Web Edition) with no real issues, just the server was getting old and cranky.
I'm no MSSQL DBA but can handle most simple things fine. Here's what we did.
Took a full backup of the database on the source server - it is using Simple recovery.
Copied the DB to the 2012 server and restored it, created a user and assigned permissions to the tables and SPs etc.
Set up the site - which is a classic asp site on IIS8 and used the following connection string, which we've been using on the other sites on the new server:
objDBConn.Open "Provider=SQLOLEDB.1;Password=XXXX;Persist Security Info=True;User ID=XXXX;Initial Catalog=XXXX;Data Source=10.183.5.120;Network Library=DBMSSOCN"
The site started up fine and connected to the database, but some pages were running very slow and eventually timing out:
Microsoft OLE DB Provider for SQL Server error '80040e31'
Query timeout expired
It seemed to be more on one particular table than others. It's a large database - 3GB data excluding any log. But there was no issue with this on the old server.
We switch the A record and people started hitting the site. The site gets a couple of thousand visitors a day.
Over the course of the next couple of hours, any pages using the connection were getting less responsive until nothing and timing out.
Increasing the connection query timeout helped sometimes - but it had to be set to some crazy amount of time.
It ended with me calling Rackspace and rebooting the SQL server. On reboot the site appears to be functioning OK now. But I am concerned that we don't know what caused it.
Has anyone come across this type of issue in a similar situation?
Haven't got the cash for some crazy $400 / hour Rackspace SQL DBA for sure.
I am currently running SQL Server 2005 Standard Edition on a Windows 2003 server machine.
I have gone to the properties of the server and confirmed that the Login Auditing is set to both failed and successful logins. For some reason though there is nothing in the logins for fails or successes in the SQL Server logs when I know there have been logins for both.
I have searched out the reason for this and have not been able to come up with anything helpful, so I am hoping that someone here could give me a little direction. This is working on my other SQL Servers, so I know where to look for the results, but there are none there.
After speaking with Microsoft about the issue and doing much research, it was determined that this was an issue with the particular version of SQL (SQL Server 2005 Service Pack 2 9.00.3042) running on that particular version of the windows release. We reinstalled SQL, and then did all the updates and patches to both windows and SQL and this seems to have resolved the issue. The SQL logs are now tracking both success and failed logins.
I have a computer working as a server with many SQL Server 2005 databases in it since two years ago.
Today, I don't know why, when I try to connect locally to any of the databases it gives me that error. It fails even if I'm logged in using Windows Authentication or as 'sa' user. It just wouldn't let me access the databases' info.
Could anybody explain me what's going on?
Database does not exist or it's offline etc.
First check, can you see the DB in the object explorer in SSMS?
Well, I don't know what was going on. I ended up rebooting the server and it all started working fine as always.
I'm running SqlServer 2005 express edition on my laptop for development purposes. It seems that when I open a connection to the database, the setup time is REALLY slow. It can take up to 10 seconds to get a connection. I usually have multiple connections open at the same time (Profiler, Development environment, Query Analyser, etc.) I have a hunch that the slow times are related to the fact that I have multiple connections open.
Is there a governor in Express edition that throttles connection times when multiple connections are made to an instance?
Update:
My workstation is not on active directory, and SQL is running mixed mode security. I will try the login with sql authentication. I am not using user instances.
Update2:
I setup a trace to try and figure out what is going on. When the connection to the database is opened the follow command is executed:
master.dbo.sp_MShasdbaccess
This command takes 6 seconds to execute.
I figured it out. The problem was I had multiple databases with AutoClose set to true. I shut it off in all my databases and the problem went away.
see this article for more info.
Are you sure the connection is the bottleneck? Is it your conn.Open() line that is taking 10 seconds?
AFAIK there's no governer anymore in SQL Express.
Now, are you on a Windows Active Directory Domain? If so, there might be an issue with your DNS or something that means the connection to the domain controller to validate your logon to the server instance is taking the time. I suggest you experiment switching the server over to use SQL Security, give the SA account a password, and try logging in as SA and see if that makes a difference.