Viewing 15 posts - 19,216 through 19,230 (of 22,226 total)
Yep. I'm just starting the process of evaluating all our 2000 servers using the 2008 Upgrade Advisor. That's one syntax error that's popping up all over the place. I'm a...
"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
December 2, 2008 at 9:28 am
The old parser would also let you refer to columns by the table alias and the new one does not.
"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
December 2, 2008 at 8:40 am
Have you taken a look at the execution plans? Are different tasks being performed by the system?
Second vote for making sure you did maintenance after the upgrade, especially updating statistics...
"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
December 2, 2008 at 8:29 am
Use SQL Agent to schedule the time for the daily run. You can run a tsql statement from within the Agent job.
"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
December 1, 2008 at 11:08 am
Well now, our methods worked, but they were predicated off of joins and a single row out of each set, not multiple rows out of each set. I still think...
"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
December 1, 2008 at 8:44 am
Chris Morris (12/1/2008)
Thanks for the tip, Grant, Ill try and get hold of that article. Do you mean this...
SELECT o.*
FROM #TOPTEN AS o
WHERE BATCH = 10
AND [ID] IN
(SELECT...
"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
December 1, 2008 at 8:10 am
No, no, no apoloogies. If there's any misunderstanding, it's on my side. I think your solution is likely the only one. I've never needed to capture an output from sqlcmd...
"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
December 1, 2008 at 7:45 am
Output to what? I mean what am I outputing to? Sqlcmd can just output to a file pretty easily if that's 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
December 1, 2008 at 7:08 am
You would want to use it with any of the ORM tools that try to walk the structure of the data returned. By masking the table structure off behind 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
December 1, 2008 at 7:06 am
I'd suggest using the TOP and an ORDER BY within the sub-query instead. Assuming there is an index for the ORDER BY clause to use, I think you'll see 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
December 1, 2008 at 7:01 am
As everyone else has said, it depends.
I used to use the approach of an identity column on most, if not all, tables. I've learned better. Now I tend towards what...
"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
December 1, 2008 at 6:54 am
The way I've done it previously is to output the procedure to XML and store it on the side. Then as you make adjustements to the query, you can compare...
"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
December 1, 2008 at 6:45 am
Oops. Missed that this was SQLCMD
That's OK. You can use SQLCMD variables the same way, still using OUTPUT parameters. For more on SQL Command variables, this is BOL: ms-help://MS.SQLCC.v10/MS.SQLSVR.v10.en/s10de_1devconc/html/793495ca-cfc9-498d-8276-c44a5d09a92c.htm
Or online...
"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
December 1, 2008 at 6:37 am
Use output parameters. They work a little like this:
--create a procedure
CREATE PROCEDURE dbo.MyProc
@ID int OUTPUT
AS
SELECT ID FROM schema.Table
GO
--now you can call the proc like this
DECLARE @LocalId int
EXEC dbo.MyProc @ID =...
"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
December 1, 2008 at 6:33 am
I think you've hit the nail on the head here Tony. I don't agree with either of the wild fringe groups. I think that well designed apps take advantage of...
"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
December 1, 2008 at 6:16 am
Viewing 15 posts - 19,216 through 19,230 (of 22,226 total)