Viewing 15 posts - 121 through 135 (of 238 total)
Use Windows Performance Monitor (in Administrative Tools). Select SQLServer:Databases as your Performance Object and Active Transactions as a counter. You will see other counters there too.
February 13, 2003 at 5:40 pm
WHEN I INCREASED THE TIMEOUT INTERVAL FROM 30 TO 60 SECONDS, IT STARTED TO WORK WELL. I ALSO INCREASED THE BUFFER SIZES TO GAIN PERFORMANCE.
However, if I remove a relationship...
February 7, 2003 at 6:03 pm
Thanks Michael. I am trying all these things. It seems to be helping but we are still to see the end.
What did you mean by suggesting to remove joins?...
February 7, 2003 at 4:55 pm
Thank you Michael. I am going to try it right now.
Michael Romm
February 7, 2003 at 10:05 am
You can add or drop many columns at a time from a table. However you cannot alter more than one column in a single ALTER TABLE statement. Use multiple statements...
February 4, 2003 at 4:37 pm
No, you can return only an integer with the RETURN statement from a SP.
February 4, 2003 at 12:09 pm
If you need to store that data for later use, put it in a table.
I know, this does not answer your question, sorry. But Phill already answered.
February 3, 2003 at 4:37 pm
Are you sue you must have that logic in a trigger, not in a stored procedure?
Are you positive you have to use dynamic SQL?
February 3, 2003 at 3:59 pm
I meant something like this:
create table #aaa( <table definition> )
insert #aaa( col1, col2, col3 )
execute sp_executesql @query
February 3, 2003 at 3:02 pm
Consider creating a user-defined function that returns a table. Alsao, you can do this:
INSERT #temp_table ( <column list> )
sp_executesql @query
February 3, 2003 at 11:10 am
Of course, it is preferable in SQL to use a set-based operations instead of loops. Pattern matching capabilities will help to reslve your puzzle. Try something like this (details will...
February 3, 2003 at 11:05 am
It is slow not only now. It is generally slow.
Sorry for complaining, it is a great site anyway.
Edited by - mromm on 01/30/2003 3:06:17 PM
Edited by - mromm...
January 30, 2003 at 2:58 pm
UPDATE Xaction
SET InternationalPhoneFlag =
CASE WHEN v.FaxReqPhoneNum <> '000000000000000000'
AND x.FaxReqPhoneNum = '000000000000000000'
THEN v.InternationalPhoneFlag
ELSE x.InternationalPhoneFlag
END,
FaxReqPhoneNum =
CASE WHEN v.FaxReqPhoneNum <> '000000000000000000'
AND x.FaxReqPhoneNum = '000000000000000000'
THEN v.FaxReqPhoneNum
ELSE x.FaxReqPhoneNum
END,
...
January 30, 2003 at 1:41 pm
Then you would have to duplicate the same condition check in more than one CASE statement.
Edited by - mromm on 01/30/2003 1:34:50 PM
January 30, 2003 at 1:33 pm
To check for an error you use @@ERROR immediately after the given statement:
IF @@ERROR <> 0 <do something>
To raise a custom message, you can use the RAISERROR command:
RAISERROR( 'ERROR: bla-bla-bla',...
January 30, 2003 at 12:00 pm
Viewing 15 posts - 121 through 135 (of 238 total)