Viewing 15 posts - 20,326 through 20,340 (of 22,220 total)
It is possible for the RI checks to be performance hit, sure. But if you've set up your tables & indexes appropriately, they shouldn't be. Doing an RI read 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 27, 2008 at 6:29 am
It's my understanding that if you mark a database as read only, no locking occurs. So if you have a warehouse type of app where you won't be modifying 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
May 27, 2008 at 5:43 am
I'm not sure. I've never seen it go off without there being a collation value set either on the table or column or parameter. If you're getting collation errors 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 23, 2008 at 1:24 pm
I'm not a hard-core programmer, so forgive me if I say something more stupid than I usually do...
You'll get the number of units that should be displayed and you'll 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
May 23, 2008 at 12:26 pm
You can go into the Advanced Properties of a step and set up a number of retry attempts and a retry interval. That ought to do what you need.
"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 23, 2008 at 12:15 pm
Check the code to see if it added the COLLATE key word after the parameter definition. That would cause the problem.
"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 23, 2008 at 12:12 pm
fshguo (5/23/2008)
After I compared the execute...
"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 23, 2008 at 12:08 pm
Before I try to solve that, you might want to rethink the approach. If you fill out the rows for the user, even though there's no data, you either go...
"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 23, 2008 at 10:30 am
dp (5/23/2008)
"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 23, 2008 at 8:56 am
Oooh. Excellent. I've got a lot of respect for Aikido. Very useful techniques. We've had people teach seminars on it so that we at least have a level of understanding...
"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 23, 2008 at 6:56 am
I'd start with Itzik Ben-Gan's two books, Inside T-SQL Querying and Inside T-SQL Programming.
"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 23, 2008 at 6:51 am
That's only one insert every 5.76 seconds. Even if you assume that all the records will come in over a 12 hour period that's only one every 2.5 seconds. Even...
"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 23, 2008 at 6:49 am
It's just guesses without some code and structure.
If you step through the process, running the steps manually, can you see the data move appropriately? That's where I'd start.
"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 23, 2008 at 6:44 am
You can certainly update from an inner join. That's easy. The trick is to get the join right to start with.
Instead of doing an update, write the whole thing as...
"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 23, 2008 at 6:14 am
Since these are all pulling from the same table (except one of the queries) have you looked at either using an OUTER join or even an INNER join to pull...
"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 23, 2008 at 6:05 am
Viewing 15 posts - 20,326 through 20,340 (of 22,220 total)