Viewing 15 posts - 53,791 through 53,805 (of 59,072 total)
Also - your test has a flaw in it, since you start by trying to cram 4 digits after the decimal point into 2 digits after the dot. So you...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 30, 2007 at 2:55 pm
Heh... You do DELETEs? In a "staging area"? I'd just mark the rows with a flag of some sort and tell my procs to ignore those rows.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 30, 2007 at 2:26 pm
Heh... at that point... I'd be thinking "BEER"! 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
November 30, 2007 at 2:22 pm
Even if it's "auto-generated" code, someone someday is going to have to troubleshoot it... take some time out to format it! And, the use of table aliases would clear...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 30, 2007 at 2:15 pm
And (missed it), Antares has even better reasons...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 30, 2007 at 1:21 pm
Heh... there's just a pot-wad of undocumented features and sprocs in SQL Server... most would warn against using them because if they're undocumented, they could disappear on the next service...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 30, 2007 at 1:18 pm
For me, it's because most things that you query are tables... for a view or a function, you might want to use the Hungarian notation to make it obvious that...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 30, 2007 at 1:06 pm
Or, you could try posting in the "Access" forum 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
November 30, 2007 at 12:10 pm
Not odd behaviour... same as what happens with most numeric datatypes...
DECLARE @Datum2 INT
SET @Datum2 = ''
SELECT @Datum2
--Jeff Moden
Change is inevitable... Change for the better is not.
November 30, 2007 at 11:59 am
IF OBJECT_ID('TempDB..##my_temp_table','U') IS NOT NULL
PRINT 'Table Exists'
ELSE
...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 30, 2007 at 11:55 am
FYI... sp_MSforeachdb uses a cursor 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
November 30, 2007 at 11:49 am
Use WITH ROLLUP... search for the correct "NULLS"...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 30, 2007 at 11:47 am
CREATE TABLE #DirInfo
(
SubDirectory SYSNAME,
Depth...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 30, 2007 at 11:45 am
you need to first EXPAND the precision BEFORE the operation, and then DECREASE the PRECISION when you're done....
Heh... and what better way to do that than to use FLOAT...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 30, 2007 at 11:21 am
b_boy (11/29/2007)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 30, 2007 at 11:08 am
Viewing 15 posts - 53,791 through 53,805 (of 59,072 total)