First of all, you shouldn't be inserting "Owner" into the Audits table because that's a form of denormalization you don't need here... bit, if you insist, here's a self supporting...

Good tool... bad answer ... you still haven't answered the "generic" question.  David got it, though...

(and it appears that you are not paying for this form of advertising which might...

 SELECT i.*

   FROM IndSales i

   LEFT OUTER JOIN mstBranch b

                ON i.BankCode   = b.BankCode

               AND i.BranchCode = b.BranchCode

  WHERE b.BankCode IS NULL

Try running the SELECT portion by itself... if the performance is similar to the performance of the whole INSERT/SELECT, then you might try using the INDEX TUNING WIZARD (and a...

Just for grins...

DECLARE @Num1 FLOAT

DECLARE @Num2 FLOAT

    SET @Num1 = -1.2

    SET @Num2 = -3.4

 SELECT Largest = (ABS(Num2-Num1)+(Num2+Num1))/2

Dunno if this is what you are looking for... and I haven't tested it 'cause I'm on vacation with no access to SQL...

declare @recipe table (recipeID numeric(18,0) NOT NULL)

insert...

I don't have access to SQL Server right now so I couldn't test this... I think it may work...

select 

     OrderDate,    

     ShipCountry,

     ShipCity,

     Freight,

     /* how do I get...

Thanks for the feedback, Gopi...

Ok... I get it... David Burrows beat me to the punch... take a look at his posting... I think that may be what you want.  When you re-import, you'll probably...

Yep... copy and paste error... the cascade rename should look like...

--====== Cascade rename the tables.... (takes about 65 milliseconds)
TRUNCATE TABLE dbo.INV_Barcodes --Saves log space because is not logged
    DROP TABLE...

That won't help either (the Created_by) because it is not automatically updated during an update unless you have a trigger to do that... and, as you pointed out, even that...

Move all DECLARE's to the beinning of the function where they belong.... you cannot include DECLARE's in a WHILE LOOP.

There is no "modify date" for schema changes in SQL Server 7, 2000, or 2005.  You can however, add a new database trigger in SQL Server 2005 that will allow...

Nope, sorry Gopi... Serqiy has it right (once you correct the typeo) and you have it wrong... here's the proof... run this in the grid mode so you can "see"...

August 23, 2006 at 7:06 pm