December 14, 2012 at 12:06 pm
I installed SQL 2012 SP1 on a newly built windows 2012 server…32 cores, 256 GB RAM, EMC SAN, etc… Before doing anything to SQL, right after the install, starting SQL takes much longer than I expected. The SQL error log has a time gap of about 45 seconds. See below. This is my first time installing SQL 2012 and I’m wondering if this is normal for SQL 2012. I have uninstalled and reinstall several times on 2 machines and I get the same results.
I am installing it from an image that has SP1 built into it. Right after the installation, there are 3 error logs with data, the first 2 error logs do NOT have this time gap, the last one does have this gap. The first log shows SQL starting and stopping in 7 seconds. The second log has a lot of info in it similar to the first start after a service pack, no time gap. The last log has this gap, and all subsequent logs have this gap. I attached the whole log if anyone wants to take a look. I tried installing CU1 for SP1 but that did not fix it.
Is this normal? Does SQL 2012 SP1 take much longer to start than previous versions? Is this a bug?
2012-12-14 13:30:16.21 spid8s Starting up database 'msdb'.
2012-12-14 13:30:16.22 spid15s Starting up database 'mssqlsystemresource'.
2012-12-14 13:30:16.26 spid15s The resource database build version is 11.00.3000. This is an informational message only. No user action is required.
2012-12-14 13:30:16.38 spid15s Starting up database 'model'.
2012-12-14 13:30:16.64 spid15s Clearing tempdb database.
2012-12-14 13:30:16.90 spid15s Starting up database 'tempdb'.
2012-12-14 13:30:58.85 spid22s The Service Broker endpoint is in disabled or stopped state.
2012-12-14 13:30:58.86 spid22s The Database Mirroring endpoint is in disabled or stopped state.
2012-12-14 13:30:58.86 Server CLR version v4.0.30319 loaded.
First line of the log:
Microsoft SQL Server 2012 (SP1) - 11.0.3000.0 (X64)
Oct 19 2012 13:38:57
Copyright (c) Microsoft Corporation
Enterprise Edition: Core-based Licensing (64-bit) on Windows NT 6.2 <X64> (Build 9200: )
December 16, 2012 at 6:39 pm
It almost looks like it's taking a long time to create TempDB which leads me to ask: How large is TempDB? Also what's the performance like on the TempDB drives, and does the SQL Services account have Perform Volume Maintenance Task rights?
Cheers
Leo
Leo
Nothing in life is ever so complicated that with a little work it can't be made more complicated.
December 17, 2012 at 12:58 am
Were the TempDB files where they should be? Or did SQL have to create them?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
December 17, 2012 at 7:21 am
I put the tempdb files on separate SAN drive. I ran SQLio on every drive and there were no IO problems with any of them. The tempdb files are the original size, the data file is 8 MB an the log is 1 MB.
I'm assuming no one else has this issue with Windows 2012 and SQL 2012 SP1?
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply