Viewing 15 posts - 7,036 through 7,050 (of 22,219 total)
spaghettidba (1/1/2015)
And there's a very special thank you message for every single one of you on my blog here! đŸ™‚
Thank you for involving me in the most...
"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 2, 2015 at 4:05 am
IncidentalProgrammer (12/29/2014)
"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
December 30, 2014 at 3:55 am
Welcome to the forums!
Best of luck on what you're trying to accomplish.
The one thing I would add is to be sure that you learn how SQL Server does backups. It's...
"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
December 27, 2014 at 5:26 am
Lynn Pettis (12/23/2014)
"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
December 27, 2014 at 5:21 am
burfos (12/22/2014)
Could a database audit specification be another solution?
Sure, but audit compared to what? You have to maintain some sort of baseline. That's one of the many resources that having...
"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
December 27, 2014 at 5:16 am
Nope. You can't do that within the definition of a procedure. So, instead, you can use a local variable and set that within the body of the procedure.
"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
December 19, 2014 at 5:50 am
Pretty sure it will connect, yes. But, you will be better off in terms of support with the upgraded client.
"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
December 19, 2014 at 3:28 am
It's probably the same plan, but there will be two of them because you have what would be considered two different queries because of the different aliases.
"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
December 19, 2014 at 3:25 am
Other than that fact that there's no WHERE clause to filter the data output, I can't see anything immediately wrong with the query.
There are changes in the optimizer and...
"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
December 19, 2014 at 3:23 am
I think testing is the way to go on any of this. But, also check the index usage stats to see if they've been used. If an index has been...
"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
December 18, 2014 at 8:00 am
You can't do it as a batch. You'll have to create a cursor. You can just query sys.databases to get the list and then dynamically build a backup for each...
"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
December 18, 2014 at 6:04 am
Tac11 (12/18/2014)
I know both have toll. what would you do on production db backup? only CHECKSUM? CHECKSUM AND RESTORE VERIFYONLY? OR VERIFYONLY?
There are caveats to all this, but the article...
"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
December 18, 2014 at 6:01 am
First, you're estimated to be moving 2.9 million rows into temp tables and that's coming from four scans against your tables. That's just to load #temp_violation. That's going to 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
December 17, 2014 at 9:25 am
Check the error log. You can see when backups were fired off there. I think, but would have to look it up to be sure, it's also in the system_health...
"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
December 17, 2014 at 8:29 am
Jason-299789 (12/17/2014)
PiMané (12/17/2014)
Cause the pk when it's created will already point to the cidx and wont need rebuild/recalculate. Less work on the io system and cpu.
I thought all the NC...
"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
December 17, 2014 at 8:27 am
Viewing 15 posts - 7,036 through 7,050 (of 22,219 total)