Viewing 15 posts - 21,526 through 21,540 (of 22,232 total)
The basic syntax will work in Oracle, but you can't have the brackets.
"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
November 21, 2007 at 7:29 am
Since I know just how HORRIFIC the XML EXPLICIT statements can be, I shudder to say this, but go ahead and post the query (maybe as an attachment) and someone...
"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
November 21, 2007 at 5:10 am
I don't believe the CREATE TABLE scripts can be made generic, but I could be wrong. As to the INSERT scripts, just be sure you're, for want of a better...
"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
November 21, 2007 at 5:07 am
This being the SQL Server 2005 development board, and your question being about connecting Access to SQL Server 2000, you might want to post it in a different forum. 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
November 21, 2007 at 5:01 am
Assuming both databases are on the same server:
INSERT INTO DB1.schema.table
()
SELECT ...
FROM DB2.schema.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
November 21, 2007 at 4:58 am
Andy,
Thanks so much for posting this. Ever since I heard about the event I've been wondering how you went about pulling it off. It's something I'd like to see our...
"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
November 21, 2007 at 4:55 am
We do this sort of query quite a lot. We've found that we use one of two patterns, one works well for a single row, one works well for multiple...
"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
November 20, 2007 at 9:37 am
No one is going to want to look at a report that has 43 columns, let alone 430 or 43000. You'd want to look at aggregating the data in some...
"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
November 20, 2007 at 8:20 am
Ah, true. I thought we were dealing with only a few rows. If there are hundreds or thousands, this won't work well at all. As a matter of fact, if...
"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
November 20, 2007 at 7:41 am
The 'FROM x' should be changed to 'FROM dbo.DATA_QUALITY_OVERVIEW_TOTALS_AND_PERCENTAGES' because X was just name of the test table that I cooked up to play with your data.
You can look at...
"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
November 20, 2007 at 7:27 am
Oh heck, I misread. You do have an ORDER BY. Oops. Sorry for the bad info.
"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
November 20, 2007 at 7:08 am
This is a slight modification of a Jeff Moden script:
DECLARE @SQLHead VARCHAR(8000)
DECLARE @SQLBody VARCHAR(8000)
DECLARE @SQLFoot VARCHAR(8000)
--===== Populate the variables using info from the table
SET @SQLHead =...
"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
November 20, 2007 at 7:03 am
Well, basically, if you don't need a join, don't use one. Even if there are no rows, the engine needs to look at the table to determine the fact 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
November 20, 2007 at 5:58 am
Funny, I was just reading about this, you can't use the TOP without an ORDER BY in that situation.
"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
November 20, 2007 at 5:53 am
I guess I'm wrong, but I thought that the TOP operator strictly applied to what was returned to the client, not what was actually processed on the server. It does...
"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
November 20, 2007 at 5:45 am
Viewing 15 posts - 21,526 through 21,540 (of 22,232 total)