Viewing 15 posts - 6,886 through 6,900 (of 22,219 total)
There are a whole slew of performance monitor counters all dedicated to the Buffer Manager. That's the place I'd start.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 16, 2015 at 5:10 am
Check out the lessons at Pluralsight.com. They have some specifically for that test. I'm starting to work on the 70-464 lessons right now.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 16, 2015 at 5:00 am
Trace events on either machine should see the queries if you're capturing both rpc_completed and sqlbatch_completed.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 16, 2015 at 4:58 am
That's an indication of long term blocking. It sounds like you need to tune your system or tune your queries. Deadlocks are also an indication of performance issues caused by...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 16, 2015 at 4:57 am
If you mean DBCC, the options are limited. You can run a PHYSICAL_ONLY check that will just check the external storage of the data and not the internal storage. That...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 16, 2015 at 4:53 am
It's all managed through the buffer manager. It will remove older stuff from cache in order to support newer stuff.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 16, 2015 at 4:51 am
I'm not sure. There's nothing in the standard documentation. It almost looks like the first message is nothing but a warning and the second is the actual error. That certainly...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 16, 2015 at 4:47 am
lshanahan (1/15/2015)
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 15, 2015 at 6:57 am
This is the DMV you need, sys.dm_db_index_usage_stats. As for querying it, it's really straight forward. You can join to other system views to get the table & index names. The...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 15, 2015 at 6:07 am
There are a number of workarounds posted here at the Connect item. There's also a discussion around why it's occurring. Short answer, it's because they actually preallocate identity values as...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 15, 2015 at 6:03 am
Microsoft does a pretty thorough job of documenting these right here in the Books Online.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 15, 2015 at 5:57 am
So you're not checking consistency prior to running backups? Might want to start that going forward.
First, identify the exact object that is corrupted. If it's a nonclustered index, you have...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 15, 2015 at 5:55 am
I don't see any way to capture that information. Even the existing_connection event which has more data than any other event around connections doesn't have IP addresses. I suspect this...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 15, 2015 at 4:40 am
Before I immediately did the restore, I'd check that object_id to see what the object is that is misallocated. If it's a nonclustered index, you can drop it and recreate...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 15, 2015 at 4:24 am
The best way to get this kind of thing done is not to put the database into single user mode. The best way is to put it into restricted user...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 15, 2015 at 4:21 am
Viewing 15 posts - 6,886 through 6,900 (of 22,219 total)