Viewing 15 posts - 52,816 through 52,830 (of 59,098 total)
... 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
I've seen requests like this before and they always puzzle me... it would appear that the name should be the primary key in this case. Yet, you have more...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 19, 2008 at 7:34 pm
waitfor usage can bring an entire application to a grinding halt in an instant:
Not sure what you mean... how?
--Jeff Moden
Change is inevitable... Change for the better is not.
January 19, 2008 at 7:29 pm
If you do it right, more than you can possibly imagine...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 19, 2008 at 7:25 pm
The following URL has a lot of good information about Excel spreadsheets and ADODB... perhaps it'll have what you're looking for...
http://www.simple-talk.com/sql/t-sql-programming/sql-server-excel-workbench/
--Jeff Moden
Change is inevitable... Change for the better is not.
January 19, 2008 at 6:56 am
Also, not sure why you'd bother pinning it... it will certainly fit in cache.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 18, 2008 at 7:44 pm
17GB seems a bit large even if it's a Terabyte instance... if folks are using triangular joins, cursors for large record sets, temp tables for large record sets, views of...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 18, 2008 at 7:41 pm
remember this code was done based on BOL examples, but I don't remember the topic.
First, nice idea... hadn't thought about doing it that way. Great way to import...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 18, 2008 at 7:07 pm
Sergiy (1/14/2008)
Using "," as delimites is an error waiting to happen.
mdjtlj, ask you supplier to build a test file containing '19" Monitor'.
Then try to process that...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 18, 2008 at 7:05 pm
Viewing 15 posts - 52,816 through 52,830 (of 59,098 total)