Viewing 15 posts - 21,706 through 21,720 (of 22,219 total)
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
Please don't cross-post the same question.
http://www.sqlservercentral.com/Forums/Topic408403-338-1.aspx
And I agree with the initial response.
"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 7:38 am
Maybe I'm confused by the question, but are you looking for a SELECT statement? Something like:
SELECT o.OrderId
,o.Custermer
,d.ProductId
...
"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 7:37 am
Most systems do some form of option #2. The main reason being, reporting. Your basic report engine just isn't going to be able to figure out the bit mask 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
October 9, 2007 at 7:22 am
You should look at the number of scans and reads each one is doing. Time is nice & all, but for most queries, reducing scans or reads leads to reductions...
"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 6:58 am
It is possible, but as Colin has noted, it's definitely not the right approach. If you were to try it, the trick would be to only use a single 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
October 9, 2007 at 6:55 am
Viewing 15 posts - 21,706 through 21,720 (of 22,219 total)