Since you have a 30GB insert comming up, may I suggest you run the shrink after the insert is done.. soo you don't shrink / regrow the files for nothing?

Why do you need to do this??  Formatting is usually better off done client side!

SELECT RIGHT('0' + CONVERT(VARCHAR(2), DATEPART(n, GETDATE())), 2) AS StrMin

I can't believe my eyes on this one... it may even have a huge impact on a very high transaction environement. Keep in mind that I have a celeron...

They don't even need to know the IP or the name of the server.

Build 'em a developpment server and grant them dbo there.  You can grant 'em public on the...

How would the OS affect this?!?!.

A date is a date is a date.  No matter which YEAR [] windows was made in.

The regional settings might...

First of all it's not MY best practice but A best practice.  I'll keep adhering to it because it's still valid client side where I pass over 50% of my...

Actually it's a bit different with something like an order system.  While it's wise to keep the id of the products in the details.  You also have to keep all...

So we all agree to disagree. Let's close this one before it gets out of hand .

Let me put it this way.  I drop all instanciated objects application side.  I also trust the server to do its job.  But being true to myself and my style I do...

If that can make you feel better, then Thanx .

Also you might want to limit his ideas to a certain number of columns like 4 or 5.  Or you could get suggestions for 3-4 indexes with 10+ columns (PER TABLE)...

Can't wait to hear this answer... .

DELETE FROM dbo.USP_Demo WHERE Name in ('@UserID', '@UserName')

No seriously.  I've always seen that any instanciated object should be explicitly destroyed in application design after you finished using it. ...

Thanx guys.  So I guess it's settled then. I'll see you at PASS next year .

As if developpment work is easy on a machine... it can be much worse than produciton environement depending on the IN-experience of the user