Viewing 15 posts - 12,421 through 12,435 (of 22,224 total)
Basically, I'd set up two, identical databases with the two different collations and then run a set of queries against each database, one at a time, capturing a full set...
"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
June 7, 2011 at 9:39 am
Does location matter? Meaning, could people work remotely? I know several people (including me) who have lower rates for remote work.
"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
June 7, 2011 at 7:22 am
There are just scads and scads of articles and books out there on managing log files (I know because I've added to the heap several times). It's not that hard...
"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
June 7, 2011 at 7:17 am
Haven't had one yet this week, but the week is young for me. Stay tuned, I'm sure to have 3-5 before Friday.
"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
June 7, 2011 at 7:13 am
John Mitchell-245523 (6/7/2011)
Gus is right.I think sp_delete_backuphistory is date specific, not database specific, so you may end up throwing the baby out with the bathwater if you use it.
John
It is...
"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
June 7, 2011 at 7:04 am
Learn, use, and love the Books Online for SQL Server. They really do have almost every possible basic explanation you could ever need. Here's the entry on Join Types in...
"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
June 7, 2011 at 6:56 am
I would not suggest putting them in a schema in the same database as your operational tables, no. You're going to hit the log & data files on your main...
"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
June 7, 2011 at 6:53 am
Gianluca nailed it. You get new statistics during an index rebuild. You will not get updated statistics during an index reorg.
"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
June 7, 2011 at 6:49 am
If you've already defined which queries are causing you pain, you're past the starting point. Once you identify the queries, then yes, absolutely, the execution plans are the way to...
"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
June 7, 2011 at 6:48 am
Unless those are covering non-clustered indexes (meaning, all columns needed by the query are included in the index), then you're probably also seeing an RID operation. Posting 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
June 7, 2011 at 6:46 am
If databases that are no longer on the server are in the backup history, that just means the history wasn't cleared when the database was dropped. You can use sp_delete_backup_history...
"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
June 7, 2011 at 6:40 am
Piling on, but same thing, you won't know for sure how much compression you get for sure unless you use it.
"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
June 7, 2011 at 6:35 am
Lowell (6/7/2011)
you said "... If a plan is never cached, it won't appear in the query stats DMV at all...", can you clarify?
I thought every...
"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
June 7, 2011 at 6:33 am
WayneS (6/6/2011)
If I've read things right, you're going to the Summit? Do you know that Thursdays up there is "Kilt Day"? Grant started it... he can fill you in on...
"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
June 7, 2011 at 5:37 am
I'll be making a new avatar out of a scary/goofy picture of me in a wet suit up in Alaska right before we went snorkeling... on the other hand, it...
"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
June 6, 2011 at 2:01 pm
Viewing 15 posts - 12,421 through 12,435 (of 22,224 total)