Viewing 15 posts - 7,186 through 7,200 (of 22,219 total)
Well, first of all, I'd say that while an identity column does uniquely identify a row, you still should have the business key as a unique constraint on the table....
"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
November 26, 2014 at 10:37 am
Read the execution plan to understand how the query optimizer chose to interpret your query.
"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
November 26, 2014 at 10:32 am
Query Shepherd (11/26/2014)
Yes. Sorry, I ment page splits and the timestamp is not indexed and the table is not a heap...
Then it won't do anything any differently than any other...
"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
November 26, 2014 at 10:30 am
So this has nothing to do with the query. It's the settings within SSRS that will allow you to have multiple columns.
Unfortunately, I don't know SSRS well enough 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
November 26, 2014 at 8:56 am
How do you mean paging? Data is stored on pages. Do you mean page splits? Timestamp isn't going to lead to page splits unless you've indexed it and then 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
November 26, 2014 at 8:54 am
For the general stages, go and look at the error log of a server right after startup. It'll show you a number of processes as each completes so that you...
"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
November 26, 2014 at 8:52 am
Yes, have one.
But seriously:
Start with backups. Identify the Recovery Point Objective (RPO). That's the amount of data that the business is willing to lose. They'll say zero, but that's an...
"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
November 26, 2014 at 7:31 am
If you know for certain that you're using no other mechanisms that need the SQL Writer service, it can be disabled. That's from 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
November 26, 2014 at 3:21 am
So, not so much a bench marking tool as a load generation tool. HammerDB is one of the preferred approaches. But, if you want to simulate load, you could get...
"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
November 26, 2014 at 3:14 am
Yes, they would be. It'd be a bad choice to do this after setting up a cluster. I'd suggest going the method of scripting everything for your initial deployment.
"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
November 26, 2014 at 3:11 am
Yes, the role changes. When you fail over from one database to another within your availability group, the active node switches. If you're scheduling activities on the databases, you'll want...
"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
November 26, 2014 at 3:09 am
And, as the article says, it's going to be a rare case. Don't panic. Read the KB. Apply the fix. It's probably not a bad idea to get ahold of...
"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
November 26, 2014 at 3:04 am
Yeah, sorry, should have commented on that. The messages sound perfectly correct.
"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
November 25, 2014 at 3:23 pm
Could be a trigger? Nothing else is immediately coming to mind.
"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
November 25, 2014 at 3:16 pm
But if you're looking for backup, I'd strongly suggest using the built in backup mechanisms. Full backup, differential backup and log backups combined can ensure very little or even zero...
"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
November 25, 2014 at 11:28 am
Viewing 15 posts - 7,186 through 7,200 (of 22,219 total)