Working with dynamic SQL is all well and good, but avoid the risks that can lead to your code being susceptible to a SQL injection attack. As much as making your T-SQL work smarter for you, a la ...

In this third in a series on working smarter with T-SQL, let's give the built-in sp_executesql stored proc a go. In my previous posts, I've described some methods for generating and executing T-SQL ...

So it came up that several of our devs are writing their TSQL entirely in code using ADO.NET and submitting their queries that way.<BR><BR>Initially the idea was sprocs for all inserts, updates, etc..

Building on the DATETIMEFROMPARTS, DATETIME2FROMPARTS offers similar functionality, but yields more precise DateTime2 data type, containing fractions of a second to a specified precision. Naturally, ...

this will return: "(1 row(s) affected)" But now I need to know, what data was actually inserted? SQL Server has answered this question in 2005 with the OUTPUT statement: This will return a dataset ...