Viewing 15 posts - 21,706 through 21,720 (of 22,224 total)
Definitely go for the varchar(max). The only down sides are disk space, but that's easily monitored.
"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
October 11, 2007 at 11:37 am
I wasn't going to comment on the Tuning Advisor, but since the gate is now open... I haven't had good experiences with the Advisor either. I haven't had it ruin...
"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
October 11, 2007 at 7:19 am
Oh, and, I'd offer to help her work on her performance issues in order to clean up her system enough so that you can connect to 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
October 11, 2007 at 7:03 am
Steve's correct. Further, some degree of processing will occur on both of the servers, no matter what. Bare minimum, depending on what kind of server you're linking to and how...
"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
October 11, 2007 at 6:59 am
Still not there.
"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
October 11, 2007 at 6:55 am
One other suggestion, I'd use SSIS over DTS especially since you're trying to move data to 2005.
"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
October 11, 2007 at 5:35 am
I'm largely piling on at this point, but what the heck...
Yes, seperate the databases by customer and seperate them by module as well. If possible isolate by instance or use...
"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
October 10, 2007 at 11:39 am
I was thinking the same thing, but I did some searching Integer8 and it's actually a 64 bit value. I'm not convinced you can put it into a BigInt, but...
"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
October 10, 2007 at 6:56 am
g.sarvesh (10/10/2007)
No, i m using SQL SERVER 2000
You are posting your questions to the 2005 TSQL forum. Any answers are likely to contain syntax that won't work in 2000. That'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
October 10, 2007 at 6:43 am
The first two messages are lower level messages that are not a part of the TSQL statement, but are occurring at a lower level within the system. The CATCH statement...
"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
October 10, 2007 at 6:37 am
I'm sorry, I've got nothing that shows how to convert from the 64bit Integer8 data type into anything in SQL Server within TSQL.
You may have a perfect opportunity 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
October 10, 2007 at 5:35 am
Good one. I hadn't thought it through that far.
"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
October 10, 2007 at 5:19 am
Gonzalo Faral (10/9/2007)
So it is impossible to concatenate a string to form the name of a variable and tell the compiler it is a variable and not a string?
Unless...
"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
October 9, 2007 at 1:16 pm
Sorry that wasn't helpful.
You've got a lot of very odd restrictions on how you can do this work. Why is the behavior so peculiar?
However, if you must have 30...
"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
October 9, 2007 at 12:37 pm
If I understand the problem correctly, what about:
CREATE PROCEDURE x
(@ParamList XML)
AS
DECLARE @iDoc int
EXEC dbo.sp_xml_preparedocument @iDoc OUTPUT, @ParmList
INSERT INTO dbo.MyTable
(Id, Value)
SELECT
(Id, Value)
FROM OPENXML(@iDoc, '/MyParameterList',1)
WITH(Id int '@Id',
Value varchar(50) '@Value')
EXEC dbo.sp_xml_removedocument @iDoc
GO
That will...
"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
October 9, 2007 at 11:41 am
Viewing 15 posts - 21,706 through 21,720 (of 22,224 total)