Viewing 15 posts - 5,566 through 5,580 (of 22,221 total)
Create the scripts for the tables first. Then modify those scripts prior to running them. Search and replace should work fine as was already mentioned.
A second suggestion, use this 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
September 7, 2015 at 4:36 am
You already have it. OPENQUERY is the other option to query across the line. Otherwise, you can look to SSIS to migrate the data.
"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
September 6, 2015 at 10:13 am
Jeff Moden (9/6/2015)
Grant Fritchey (9/6/2015)
You've shown very simplistic queries that are hitting entire data sets. Your tuning opportunities here are limited to what you can do with hardware.
+1000... unless maybe...
"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
September 6, 2015 at 10:12 am
SQL006 (9/5/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
September 6, 2015 at 5:08 am
Probably the foreign key was dropped at some point, the data was put in, and then the foreign key was reapplied using the WITH NOCHECK option. That will make 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
September 6, 2015 at 5:01 am
sql1512 (9/5/2015)
Hi All,I have to tune the below query so that it gets executed in the most minimal amount of time even when there is billions of records flowing in:
There's...
"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
September 6, 2015 at 4:58 am
Based on the query alone, I don't see where to put either a SUM or a COUNT (and it could be either depending on your structure). How is an 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
September 5, 2015 at 7:22 am
Use Extended Events to capture the execution of the queries instead of writing to a log 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
September 4, 2015 at 8:16 am
You could try scripting them out, modify the start dates on the scripts, then drop and recreate the jobs all at once.
"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
September 4, 2015 at 7:44 am
I would split those the same way. An alternate method is to use a table valued parameter.
"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
September 4, 2015 at 5:33 am
There's a lot in there that needs addressing. The biggest issue is all the places where there are functions on the columns like this:
AC.dt>=(cast(CASE WHEN dbo.AGM_isdatenull(POR.PromiseDt) = 1 THEN POR.DueDate...
"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
September 4, 2015 at 5:21 am
TomThomson (9/3/2015)
Alvin Ramard (9/3/2015)
Grant Fritchey (9/3/2015)
Nope. Just faked out the entire MSDN...
"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
September 3, 2015 at 9:10 pm
Alvin Ramard (9/3/2015)
Ed Wagner (9/3/2015)
Grant Fritchey (9/3/2015)
Alvin Ramard (9/3/2015)
Jeff Moden (9/3/2015)
Alvin Ramard (9/3/2015)
Grant Fritchey (9/3/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
September 3, 2015 at 12:59 pm
sqlkohai (9/3/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
September 3, 2015 at 12:53 pm
Alvin Ramard (9/3/2015)
Jeff Moden (9/3/2015)
Alvin Ramard (9/3/2015)
Grant Fritchey (9/3/2015)
Nope. Just faked out...
"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
September 3, 2015 at 12:07 pm
Viewing 15 posts - 5,566 through 5,580 (of 22,221 total)