Viewing 15 posts - 10,936 through 10,950 (of 22,224 total)
GilaMonster (5/8/2012)
Bhuvnesh (5/8/2012)
"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
May 8, 2012 at 3:53 am
My experience is the same, a regular refresh to ensure that data reflects production as much as possible. The issue is, this is only viable when the databases are 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
May 8, 2012 at 3:52 am
Unless we're talking about some type of actual error, no, there's nothing to see for a query that behaved, but didn't do what you wanted.
"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
May 7, 2012 at 11:01 am
No, I wouldn't say every table needs it at all. It's a business call. BTW, what about UpdateDate and UpdateBy? And are we doing physical deletes? Instead we could use...
"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
May 7, 2012 at 10:58 am
You can run it on any environment. As you've already been told by Gail, you must run it in Production. When? Find the time when you have the least load...
"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
May 7, 2012 at 5:06 am
I have a book on that topic, linked the signature below, or you can search online and find a free e-book copy of the book. I also post regularly 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
May 7, 2012 at 5:03 am
The simplist option is to restore the production database on your development environment. I agree with the previous poster, you should set up scripts to clean out any sensitive information.
After...
"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
May 7, 2012 at 4:59 am
If you're in transactional replication, did replication fail? Is the distributor down?
"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
May 4, 2012 at 12:19 pm
Although, if you're simply testing the restore to validate the backup, the fact that logins don't sync correctly is not an issue you need to worry about.
"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
May 4, 2012 at 9:16 am
Yeah, you can't test this against production systems. Good first choice.
After that, just take the backups that are already running in production and test them in a restore against a...
"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
May 4, 2012 at 7:34 am
Megistal (5/4/2012)
It works exactly as you described. It even works when using FORCESEEK (as it should as Microsoft stated)
It would be nice having an index hint that force index...
"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
May 4, 2012 at 6:37 am
That's not one I've hit on all the 2012 installs I've done. I'd suggest taking it to Microsoft. Go through support or post it as a Connect item.
"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
May 4, 2012 at 5:18 am
A backup is a bit-by-bit copy at the page level of the database. No way to single out objects from it, at all. You have to script this.
700 stored procedures...
"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
May 4, 2012 at 5:15 am
Glad the book is useful.
Not that one though. This one is out soon.
"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
May 4, 2012 at 4:33 am
Index intersection is rare and hard to demo. I have a demo of it in my query tuning book, but it's pretty contrived. You won't see it in the wild...
"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
May 3, 2012 at 12:21 pm
Viewing 15 posts - 10,936 through 10,950 (of 22,224 total)