Viewing 15 posts - 56,956 through 56,970 (of 59,101 total)
Guess I'll have to ask the obvious question... is either (or both) the SELECT and/or the INSERT wrapped in a BEGIN TRANSACTION/COMMIT pair?
--Jeff Moden
Change is inevitable... Change for the better is not.
February 13, 2007 at 7:24 pm
Is the ProfileID column an IDENTITY column or not?
--Jeff Moden
Change is inevitable... Change for the better is not.
February 13, 2007 at 7:20 pm
Why not have Informix do an export to, say, a comma or tab delimited file and then DTS that bad boy in?
--Jeff Moden
Change is inevitable... Change for the better is not.
February 12, 2007 at 8:29 pm
Anders is correct... the reason why you're getting the arithmetic overflow is because SQL Server looks at those types of numeric dates as the number of days since the 1st...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 12, 2007 at 8:26 pm
Dunno... If faced with such a problem, I'd have the spreadsheet do a transpose and write to a text file for me... then, I'd import the text file using Bulk...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 12, 2007 at 5:26 pm
Um.... let me get this straight... you say the delete job is scheduled to run once every minute and that everytime someone logs in to the app, it creates a...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 12, 2007 at 5:13 pm
Hey Robert!
Man, I just tried your fnStripTags function and I converted it to use a Tally table and tested both... I'm very well impressed! In this case, the WHILE loop...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 10, 2007 at 12:01 pm
But I still get a Incorrect Syntax near '.' error when I run the query by Robert Davis.... |
--Jeff Moden
Change is inevitable... Change for the better is not.
February 10, 2007 at 10:37 am
I'm thinking "structural artifact" myself. If the FILL FACTOR isn't set to 100, I could see where an index on a small table could out strip the size of the...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 10, 2007 at 8:07 am
How many indexes does the table have, Farrell?
--Jeff Moden
Change is inevitable... Change for the better is not.
February 10, 2007 at 7:38 am
Yep... like maybe to send an email to notify of a zero rows situation or maybe just log that nothing happened... hadn't thought about that before.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 10, 2007 at 12:29 am
(Not sure what happened to the post you responded to)
Yep... I could be wrong... please post your function and your test code some I might do some testing... I will,...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 9, 2007 at 11:18 pm
Lee,
Lynn is absolutely spot on... the only thing is that the necessary cross join will spawn a huge number of interim rows even if you add a DISTINCT to the...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 9, 2007 at 6:13 pm
... 'course, if you have a Tally table, you don't even need a function (although they are convenient)... included the original data for convenience...
Create Table TableA (ID varchar(2), Nodes...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 9, 2007 at 4:26 pm
Heh... looks like you've been bitten before, eh Juan?
So far as the ANSI_NULLs thing goes, the default setting, when you create an SQL Server instance, is ON. Unless someone...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 8, 2007 at 6:09 pm
Viewing 15 posts - 56,956 through 56,970 (of 59,101 total)