Viewing 15 posts - 6,961 through 6,975 (of 22,219 total)
Jeff Moden (1/9/2015)
Chris Wooding (1/9/2015)
"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 9, 2015 at 8:20 am
KenpoDBA (1/9/2015)
"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 9, 2015 at 8:16 am
Trace scripts should work. If you have an error you can post that would be helpful.
But really, the Profiler GUI shouldn't be connected to your servers directly. There are several...
"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 9, 2015 at 7:08 am
You can see an aggregate of query performance from the queries that are still in cache by looking at sys.dm_exec_query_stats.
But, understand, it doesn't show individual calls. It shows aggregate calls....
"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 9, 2015 at 6:32 am
Yep. It's a known issue and, according to Microsoft, by design. There are a few things you can use to try do deal with it at the link.
"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 9, 2015 at 6:29 am
GilaMonster (1/9/2015)
Grant Fritchey (1/7/2015)
Running a RESTORE WITH VERIFY_ONLY, which is what the backup validation does, shouldn't interfere with log shipping or anything else on your server.
It also won't verify that...
"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 9, 2015 at 4:50 am
It's likely that someone canceled the restore. Drop the existing database and start the restore again.
"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 9, 2015 at 4:14 am
No, you don't have to have HyperV running in more than one location. If you're using a server to train on, use it on the server.
"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 9, 2015 at 4:12 am
Extended Events will only work in 2008 or greater.
I haven't tried connecting to 2005 from 2014 Profiler, so I'm not sure what the issue might be.
Instead of using the Profiler...
"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 8, 2015 at 9:04 pm
Should work fine.
Also, there's this from Microsoft.
"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 8, 2015 at 12:52 pm
I also recognize that some guy responding to your question on the internet is not going to be exactly compelling evidence on your side. So, I did a quick search...
"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 8, 2015 at 11:20 am
Service Oriented Architectures are great. No question.
But this idea that a persons name has to be broken into multiple tables because part of it might be updated independently from 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
January 8, 2015 at 11:02 am
Unfortunately, the devil is in the details on the tech. There's not a single winning piece of tech on the Microsoft side. I think the only winning piece of tech...
"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 8, 2015 at 10:52 am
And I'm with Perry. I'd use .bak for all sorts of backup files, but differentiate them in the name.
"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 8, 2015 at 6:27 am
Nah. You can call your backup files .doc if you want to. They'll still work fine.
Don't do that though.
"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 8, 2015 at 6:26 am
Viewing 15 posts - 6,961 through 6,975 (of 22,219 total)