Viewing 15 posts - 10,621 through 10,635 (of 22,224 total)
It depends on two things, neither one database size, transactions in transit and your connection speed. So, no, you should see reasonably fast transitions depending on what's going on with...
"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
July 20, 2012 at 5:10 am
The signal wait is just time waiting on the processor. It's an indication that for any given type of wait, you may, depending on what percentage the signal wait takes...
"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
July 20, 2012 at 5:06 am
Probably should be moved to the "Anything that is not about SSC" forum, but that's Steve's call.
I was drafted/volunteered. I was working for a dot com startup as a developer....
"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
July 20, 2012 at 5:03 am
Also remember that recompile might play a factor. It's reduced or eliminated with table variables, but it's something you'll have to deal with when using temporary tables. Remember, there are...
"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
July 20, 2012 at 4:58 am
Not much to add. I'd start with Gail's articles. Once you're going, my books can help. Also, performance issues can be from causes other than queries (although that's near 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
July 20, 2012 at 4:56 am
The DMOs related to query performance are basically, what is absolutely executing right now, sys.dm_exec_requests, or, an aggregate of queries that have executed for the queries currently in cache, sys.dm_exec_query_stats...
"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
July 20, 2012 at 4:51 am
Test all three and see which one does what you want in the most efficient manner.
Probably, I'd look at #3 first, but it really depends on what the execution plan...
"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
July 20, 2012 at 4:48 am
Devesh_Srivastava (7/19/2012)
If the size of databases are very large and you are using backup compression technique then you should not include the Verify Backup option in the Backup job 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
July 20, 2012 at 3:23 am
Query Tuning
Execution Plans
Backups
Monitoring
Development & Deployment processes
Deadlocks
Parameter sniffing
Rinse and repeat
"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
July 20, 2012 at 3:21 am
Ah, I don't think it displays status for that recovery process. I think you'll have to wait. Sorry.
"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
July 18, 2012 at 8:14 am
I have several different versions of this type of query in this article[/url]. Take a look. I think you'll find something to help.
"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
July 18, 2012 at 7:59 am
I would get a full understanding of the state of the backups. In addition, what are the maintenance routines currently in place. After that, I'd want to work on establishing...
"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
July 18, 2012 at 7:52 am
You can take a look at the DMO sys.dm_exec_requests. For a backup or restore it will show a percentage complete. It's not a perfectly accurate measure, but it will be...
"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
July 18, 2012 at 7:49 am
You can get that right out of the Dynamic Management Objects (DMO). This will get that piece of data:
SELECT deqs.creation_time FROM sys.dm_exec_query_stats AS deqs;
"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
July 18, 2012 at 6:48 am
In general, to coordinate databases with code, the best approach I've found over the years is to get your database into source control. That used to be quite difficult, but...
"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
July 18, 2012 at 6:03 am
Viewing 15 posts - 10,621 through 10,635 (of 22,224 total)