Nice troll bait... I'm a little hungry...

Anyone advocating stance within the development and technicals sphere that says ALWAYS or NEVER is usually wrong. So, saying "ALWAYS use stored procedures" is...

Storing data into different operational areas doesn't add any actual benefits unless those different operational areas also have different loads, different stresses, needs to be backed up at different times......

Yes, you absolutely can. It's a pretty common design method. The one place almost everyone will agree that something like this applies is in a many-to-many relationship. There are other...

What I meant was, automated processes, such as a checkpoint, can pop up in the middle of a query and affect the overall performance (not by much, I'll grant you)...

It really depends on the system you're working on. Most of the systems I have experience with have a pretty common set of data in cache the majority of the...

Key word and tricky phrase in the question is "similar"

Variations in memory, cpu, disk I/O, cache, cache size, statistics, index fragmentation, yada, yada, yada, will result in differences in execution...

For testing, and for testing only, don't do this in Production, I'll run DBCC FREEPROCCACHE to clean out all the procedures and force recompiles. Then try running CHECKPOINT followed by...

You can only have one NULL value in those columns with the constraint.

Just to add a tiny wrinkle to what everyone else said... I've frequently found situations where the foreign key was the best candidate for the clustered index. It was the...

It really depends, on the query, on the selectivity of the column that defines the leading edge of the index... Generally, if the criteria that defines the index scan in...

Maybe I don't understand the question. Are you looking for cool things to do with it?

Here are some examples and explanations that I found useful:

http://sqlblog.com/blogs/allen_white/archive/tags/PowerShell/default.aspx

http://blogs.msdn.com/mwories/archive/2008/06/14/SQL2008_5F00_Powershell.aspx

http://blogs.technet.com/industry_insiders/pages/powershell-in-sql-server-2008.aspx

If you must do this, parameterize the query and use sp_executesql. You can then capture output parameters. Something like this:

DECLARE @sql NVARCHAR(MAX)

DECLARE @count INT

DECLARE @tablename NVARCHAR(MAX)

SET @tablename = N'TestTable'

SET @sql...

Powershell is, to all intents and purposes, the replacement for the DOS prompt. What it really is though, is a very extensive scripting language that allows you to take direct...

You can associate a table or an index with a filegroup. This allows you to control placement on various disks, setting groups to be read only, backing up by group....

The problem is, the error isn't some little connection error or a tsql error. The program isn't initializing. You've got something mucked up at a low level.