You can also use LinqPad...

You can also use LINQpad...

Temporary tables are an external dependency. They can be particularly troublesome when connection pooling is used. SSIS also has issues with them. Instead, use table-typed parameters to push data into your stored procs and use a separate result set...

And this will work only as long as DoSomeWork() is not dependent on DoSomeWork2(). As your example shows, the order of execution is not predictable. Although DoSomeWork() was called first, DoSomeWork2() completed first....

Using HOSTNAME in this manner is likely to cause confusion. If I were to look in DNS or DHCP for 'SSMS01' (or just use "ping -a SSMS01"), I wouldn't be able to find it. I might start to wonder if a rogue machine is connecting to my servers. If the...

Dishdy: The SQL Server debugger in versions prior to 2008 was much harder to use and set up. It really required the full version of Visual Studio. The Microsoft Knowledge Base will give you the details. SQL Server 2008 Management Studio Express do...

Here's a major problem with PIVOT: You must know the values in the IN clause when you write the query. It's possible to make this dynamic, but it's complex and non-performant....

how about only using the compression when you are transferring data from off-premises to on-premises? I wouldn't suggest storing and querying compressed data on a day-to-day basis.... the compression/decompression overhead could limit scalability and r...

Have you considered using a SQLCLR function that leverages System.IO.Compression and store the output in a varbinary(max) column?...

SQL Server doesn't support putting data or transaction log files on compressed drives or setting the Compressed attribute unless the Filegroup is marked as read-only. Have you tried restoring a database backup where the filegroups were marked readonly ...