Viewing 15 posts - 54,721 through 54,735 (of 59,098 total)
If you have to tract all that other stuff about a card, why worry about how many rows you have... it's gonna have to be stored somewhere. Perhaps a...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 6, 2007 at 8:10 pm
When in doubt, simple tests will keep you from barking up the wrong tree or missing a perfectly good fire hydrant 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
October 6, 2007 at 8:04 pm
3. SELECT indentity(int,1,1) as ID, * into #tab from T are very common.
Shoot, that's one of my favorites. If the boys in Redmond ever get rid of Select...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 6, 2007 at 8:01 pm
It's probably a good thing you don't know how because my recommendation is not to store images in SQL... store them in files and store the file names in SQL....
--Jeff Moden
Change is inevitable... Change for the better is not.
October 6, 2007 at 7:55 pm
Heh... when are you going to get to all the things I sent you, Steve?
--Jeff Moden
Change is inevitable... Change for the better is not.
October 6, 2007 at 7:53 pm
... and, if there are any questions about possible performance, lets use the good ol' million row test table I keep around...
--===========================================================================================
-- Build a million rows of test data. THIS...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 6, 2007 at 7:47 pm
Original thread seemed pretty darned clear... but I could be wrong...
This should do it...
--===== If the temp table exists, drop it
IF OBJECT_ID('TempDB..#SandBox') IS NOT NULL
...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 6, 2007 at 7:21 pm
Actually WreckageTime is added to date part of AnnounceDateTime to generate a smalldatetime value to be used particularly in this query
But, that's what I'm talking about... I wasn't talking about...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 6, 2007 at 6:53 pm
Or, just...
SELECT @bLookForChangedCUSIPs = SIGN(COUNT(*))
FROM Performance.dbo.gChangedCUSIPs
WHERE CUSIPKey = @vchVAGK + @vchPAC
--Jeff Moden
Change is inevitable... Change for the better is not.
October 6, 2007 at 3:07 pm
So, do table valued functions create temp tables in tempdb?
Yes, they do... Please refer to Q4/A4 at the following URL...
http://support.microsoft.com/default.aspx?scid=kb;en-us;305977&Product=sql2k
--Jeff Moden
Change is inevitable... Change for the better is not.
October 6, 2007 at 2:59 pm
No... I wouldn't make an alpha-numeric primary key... they're slow and difficult to maintain.
Why don't you just use an INDENTITY column and a Country column?
--Jeff Moden
Change is inevitable... Change for the better is not.
October 6, 2007 at 2:56 pm
This will help, as well...
http://www.w3schools.com/sql/default.asp
--Jeff Moden
Change is inevitable... Change for the better is not.
October 6, 2007 at 2:40 pm
Heh... You did go backwards, indeed...
Instead of me trying to figure out what the function is supposed to do, please tell us so we can tell you how to do...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 6, 2007 at 2:31 pm
Muhammad Furqan (10/2/2007)
i think i was unclear.
what i meant was that constraint should be enforced, but a constraint being violated should not give an error and terminate the...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 6, 2007 at 2:27 pm
My recommendation would be to import the data into a staging table using BULK INSERT. Nasty fast... then, you can add the necessary indexes for performance... can't do that...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 6, 2007 at 2:22 pm
Viewing 15 posts - 54,721 through 54,735 (of 59,098 total)