Viewing 15 posts - 49,816 through 49,830 (of 59,091 total)
Oh, very clever... well done, Barry!
Only corrections are to remove the CASE in the final insert and to delete the compressed rows...
Other than that, very, very clever... 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
June 21, 2008 at 2:46 pm
Tally table method in 2000 for this would require a triangular join... I believe. If you know a way to do this in 2k without using a loop but...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 21, 2008 at 12:53 pm
Jeff Moden (6/21/2008)
Steve Jones - Editor (6/21/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 21, 2008 at 12:51 pm
rbarryyoung (6/21/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 21, 2008 at 12:50 pm
Steve Jones - Editor (6/21/2008)
SQL Apprentice Jeff...has a nice ring to it. Maybe we can chip in for a pointy hat for you to wear to the meetings 😉
Heh... you...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 21, 2008 at 12:47 pm
Dang... I just can't beat the kids anymore... 😀
Very nice, Matt. Thanks.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 21, 2008 at 12:40 pm
Matt Miller (6/21/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 21, 2008 at 9:12 am
Absolutely perfect... you actually need to use two tables... let's say you have TableA and TableB and they are identical. You have a view or a synonym pointing...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 21, 2008 at 8:34 am
Mobasha,
To be true, there is a UID (User ID) column in the TempDB..SysObjects comapatibility view of SQL Server 2005... it's not the ID of the person that made it, though......
--Jeff Moden
Change is inevitable... Change for the better is not.
June 21, 2008 at 8:14 am
I don't understand why you think there's a problem... no one else has access to the Temp Table or Table Variables... why are you using a transaction on them? ...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 21, 2008 at 8:01 am
sharma (6/21/2008)
Thanks..I am using BULK INSERT in that i had specified ROW TERMINATOR & FIELD TERMINATOR only.
How to specify a TextQualifier?
I had used format file also.
To the best of my...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 21, 2008 at 7:57 am
...and, if you just happend to have posted in the wrong forum and you actually have SQL Server 2005, you need to let us know that because there's a very...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 21, 2008 at 1:05 am
sqldba (6/20/2008)
example
(SVDB, N, Y; SFGB, N, N; SGTE Y, S; SVHG Y,Y; SVFH, Y, Y; ........)
data set in string...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 21, 2008 at 12:57 am
karthikeyan (6/20/2008)
first of all try yourself, otherwise you can't learn anything new. Try to write your own SP. Becuase it is a basic one, without knowing how to wite a...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 21, 2008 at 12:54 am
There is a way to do this using SET ROWCOUNT 1 and a cursor (which is technically an intermediate table but fools most people). Performance will totally suck. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 21, 2008 at 12:37 am
Viewing 15 posts - 49,816 through 49,830 (of 59,091 total)