Viewing 15 posts - 56,926 through 56,940 (of 59,101 total)
The problem with such "real time" apps is that no one plans on the connection being down
Have your "trigger" write to a...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 19, 2007 at 5:02 pm
Kind of a double post... please see my other reply.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 19, 2007 at 4:55 pm
Don't embed the quotes... put the quotes around each full path.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 19, 2007 at 4:54 pm
Oh no, no, no... MJV had it right and ISNUMERIC does NOT mean ISALLDIGITS!
create table #tmp( tc VARCHAR(10))
insert into #tmp
select '0d01' union all
select '0e01' union all
select...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 19, 2007 at 4:33 pm
Yep... then make sure that you rename the column in every stored procedure, view, UDF, foreign key, etc, that uses that column in all databases...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 19, 2007 at 6:18 am
What have you tried?
--Jeff Moden
Change is inevitable... Change for the better is not.
February 19, 2007 at 6:15 am
Now, THAT's what I'm talkin' 'bout ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
February 16, 2007 at 6:59 pm
You just love patting yourself on the back eh Jeff |
--Jeff Moden
Change is inevitable... Change for the better is not.
February 16, 2007 at 6:56 pm
Might also find it useful to put your "Numbers" or "Tally" table there along with an auxiliary date table... make sure you keep the code to build them safe for when...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 16, 2007 at 7:25 am
Micheal Valentine Jones has a faster way but this is an easy way...
Step 1. Create a permanent Tally table... (it has many, many uses)
--===== Create and populate the...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 16, 2007 at 7:21 am
Heh.... agreed... poor ol' Adam already admitted that the whacko that designed this headed for the hills a long time ago... Who would do this? I can (possibly) understand needing...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 16, 2007 at 6:53 am
That's a great suggestion... guaranteed to not duplicate between tables and no trigger overhead.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 15, 2007 at 10:31 pm
That's a cool function... change the 36 to 27 and drop the 1-9 from the string and I think it'll work for the 0, A-Z range...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 14, 2007 at 1:41 pm
Like I said, keep the identity column and add a calculated column. Takes care of new rows, old rows, etc...
Or, you...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 14, 2007 at 1:31 pm
Heh... speak of the devil and who shows up? I just recommended your sequential numbers function... was writin' while you were postin' ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
February 14, 2007 at 1:12 pm
Viewing 15 posts - 56,926 through 56,940 (of 59,101 total)