You mean table variables - sorry, i was thinking of conventional temporary tables - that's a different thing.

I still would recommend permanent tables.  About the only benefit of table variables is...

I think you mean SELECT * FROM @TempTable

... but you can't do this - it's invalid syntax.  You may not use a variable for the table name.

To reemphasise other posters,...

As a developer, never mind any marginal gain/loss in performance - I think of the blood, sweat and tears of trying to debug it in future.  As a general rule,...

You can use SET QUOTED_IDENTIFIER ON.  This will allow you to use double quotes as string delimiters so that you could write :

select * from My_Table where show_name =  "My hunter's...

Remember that GETDATE() returns a date-TIME.  Are you sure that this query is giving you exactly what you want or are you losing records at the extremes?

If I run GETDATE() now, it...

It is recommended to use table variables only for small amounts of data.  Both temporary tables and table variables are held in memory while there is space to do so...

I assume that you have looked into the Index Tuning Wizard (if not, see BOL).  What extra are you looking for?

To deal with the advertising issue and demonstrate true independence, create a dedicated advertising newsletter in which anyone can promote their SQL tools.  The main site remains uncluttered if this...

You're right - but I thought the warning wouldn't go amiss.  It looked as if he wasn't aware of this feature so doesn't hurt to pre-empt any future issues. 🙂

The key to remember is that Unicode takes two bytes per character so all your Unicode fields take twice as much space (and you can only get half as many...

Congratulations and good luck for the future.  Most of (the little) that I know about SQL Server I've learnt from your site - so a big thankyou.

Begging letter follows 🙂

I received it and deleted it immediately as I am a developer and not responsible for this area.

If the foreign key is null, does not this just indicate an orphaned child?

Look at SQL LiteSpeed - its faster and gives smaller backups than the native process.

Simple solution would be to do a search and replace substituting angle brackets with {}