Viewing 15 posts - 52,801 through 52,815 (of 59,091 total)
T-SQL is great for manipulating data but writing a hashing algorithm in T-SQL would be a nightmare.
Never tried it because I just haven't had to do it. However, with...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 21, 2008 at 7:24 am
Sorry, Terry... I don't know enough about the client known as SSIS to flip a nickel. I'm just assuming (bad thing to do, I guess) that it has some...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 21, 2008 at 7:18 am
Misnomer would be correct... client could/will, indeed, pick it up as a "failure" because some error message as you said. Of course, that should be handled...
Loading the table...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 21, 2008 at 7:05 am
Then, you need to do as I said... check out the "What's New" section of each release on the Microsoft website.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 21, 2008 at 6:56 am
If you really have to copy the whole table, then you do not need deletes and you don't need the transaction. Insert into a new table... when you have...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 21, 2008 at 6:54 am
Yeah... mistakes like that would certainly do it... I thought you were talking about something symptomatic with using WAITFOR even though you'd used it correctly...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 21, 2008 at 6:38 am
Like everything else, it depends...
If you just happen to forget that a column may have times on it, BETWEEN is not a good thing because you may be missing a...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 21, 2008 at 6:35 am
The transcender tests are representative of what the real tests will be. The real tests, as you know, are to test if you know enough to deserve the certification....
--Jeff Moden
Change is inevitable... Change for the better is not.
January 20, 2008 at 7:29 am
... and, if you're really smart, do a backup first.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 20, 2008 at 7:26 am
You will need to use some form of dynamic SQL...
DECLARE @TableName SYSNAME
SET @TableName = 'sometablename'
EXEC ('CREATE TABLE '+@TableName+' put rest of create here')
I guess I'm really worried about why you...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 20, 2008 at 7:25 am
Going to another site for your files is a PITA... it would be much better if you'd just attach the files to your post.
The files are JSP files... I'm a...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 20, 2008 at 7:21 am
Replace this part of the code...
/*
EXEC EDI..prcCreditCardCampaign '2008-01-14 00:00:00:000','2008-01-18 23:59:59:999'
EXEC EDI..prcCreditCardCampaign NULL,NULL
*/
IF OBJECT_ID('prcCreditCardCampaign') IS NOT NULL
DROP PROC prcCreditCardCampaign
GO
CREATE PROC prcCreditCardCampaign
@FromDate DATETIME = NULL,
@ToDate DATETIME = NULL
AS
SET NOCOUNT...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 20, 2008 at 7:12 am
Heh... "Flat file cleanup on aisle 5"!
Are you all set, Kirk? Did Mark's post do what you needed (looks like it but thougt I'd double check)?
--Jeff Moden
Change is inevitable... Change for the better is not.
January 19, 2008 at 8:35 pm
No, no... it won't fail if the IGNORE DUPLICATES option is turned on for the unique index. It will just give a warning that at least one duplicate was...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 19, 2008 at 7:46 pm
You have no error detection code and no rollback code... and SET XACTABORT has not been turned on to make up for it...
... so why do you need a transaction...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 19, 2008 at 7:40 pm
Viewing 15 posts - 52,801 through 52,815 (of 59,091 total)