Viewing 9 posts - 31 through 39 (of 39 total)
Didn't see the one-line-instead-of-two solution, but I guess I should have.
Anyway, thanks for the feedback, Steven!
September 3, 2004 at 3:35 am
Sorry about my misunderstanding. Kind of tricky problem, and I'm afraid I can't give you a good solution.
My best attempt (it seems to work for your example, but is probably not as...
August 30, 2004 at 2:07 am
Hi,
My suggestion would be to rewrite and use union. But of course, the performance of the query below is not goint to impress anybody...
SELECT ft.*
FROM @fulltable ft
...
August 29, 2004 at 12:01 pm
Just a suggestion,
If you don't want to remove the duplicates, but just get a result set that doesn't contain duplicates, an easy way to do this would be using UNION....
August 23, 2004 at 12:11 pm
I believe the example below could be an alternative approach, given the assumption that 0 in input indicates that this is no search-criteria. It is doubtful whether this is faster,...
August 21, 2004 at 3:52 am
The steps should execute in the order of statements, so (timewise) there is no need to worry that records are deleted before the insertion takes place.
But transaction-wise, another problem...
August 21, 2004 at 3:25 am
I asked the same question I while ago, and received the linke to this article:
http://qa.sqlservercentral.com/columnists/ajethva/capturingtheerrordescriptioninastoredprocedure.asp
Unfortunately, I wouldn't work for me, as we can't use server-wide settings (or extended...
August 18, 2004 at 3:50 pm
Hi,
I don't think you are allowed to call "normal" procedures from a function. The only exception (for some reason) are extended procedures.
June 24, 2004 at 7:18 am
My best guess (but not tested):
-- Before batch
use master
go
alter database foo_db
modify file (name=foo_db_log,
size=24 GB)
go
-- After batch
use...
June 18, 2004 at 8:53 am
Viewing 9 posts - 31 through 39 (of 39 total)