Viewing 15 posts - 8,041 through 8,055 (of 22,232 total)
What kind of execution plan are you seeing that in? A graphical plan, a text plan or something else?
"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 9, 2014 at 11:23 am
Basically you can put IF logic within an in-line function to determine which table to query. That way the code refers to one thing, but the function breaks the output...
"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 9, 2014 at 6:10 am
It could be you don't have the right service packs in place on the 2000 version to upgrade to 2008R2. Do a quick search for the Upgrade Advisor 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
June 9, 2014 at 4:46 am
There's no easy way to do this, like Kevin says. One thing you can try is to use either views or in-line functions to expose a common object name 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 9, 2014 at 4:44 am
Red Gate SQL Compare works quite well with Windows Azure SQL Database.
Disclosure, I work for Red Gate.
"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 9, 2014 at 4:38 am
SQL Server prevents changes from occurring at the same time. It's part of the Atomicity, Consistency, Isolation, and Durabality (ACID) properties of the database. You can't both SELECT a row...
"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 9, 2014 at 4:34 am
Yeah, of course. Both processes are going to use CPU and memory and I/O. Therefore there's a very distinct possibility that the two processes may be in contention on those...
"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 9, 2014 at 4:32 am
Extended events is not easier than trace, but it's pretty easy and certainly has less impact on the server. Books Online will get you going.
"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 5, 2014 at 2:50 pm
That's an excellent point. Sounds like you're doing fine. If you hit issues, you know where to go for help.
"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 5, 2014 at 2:31 pm
Lookup the data types of the underlying columns and then manually set them. That's the only way.
"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 5, 2014 at 2:10 pm
Sean Lange (6/5/2014)
http://www.sqlusa.com/bestpractices/%5B/url%5D
Don't worry there is soap for your eyes. Then if you read some of the content you may want to find...
"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 5, 2014 at 12:49 pm
sqldriver (6/5/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
June 5, 2014 at 12:42 pm
patrickmcginnis59 10839 (6/5/2014)
Grant Fritchey (6/5/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
June 5, 2014 at 12:39 pm
Jason Strate has a great example that shows the effects of NOLOCK.
But, one little thing, just on the side, why write code where you put NOLOCK everywhere. If you're really...
"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 5, 2014 at 11:47 am
While you can use trace, extended events might be a better way to go. The filtering on trace events occurs after the event is captures while the filtering on extended...
"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 5, 2014 at 11:43 am
Viewing 15 posts - 8,041 through 8,055 (of 22,232 total)