Tag: Stored Procedures

Most seasoned SQL Server administrators and developers will tell you to include SET NOCOUNT ON in all your stored procedure code. The reason generally given is to turn off the unnecessary “n rows affected” message that appears so often in the Management Studio Message pane. However, the “rows affected” message is only the visible tip […]

Perhaps the title should be the disadvantages of sending SQL batches from client applications. Many people think that the primary advantage to stored procedures arises from the fact that they are optimized and compile once and then remain in memory, hopefully to be used again and again. While this can be an advantage, there are […]

In the previous blog on SQL Server’s OPENROWSET function we observed that while OPENROWSET is most often encountered in relation to linked servers, it is also valuable for directly reading flat files. It’s worth taking a moment to mention another less common application of OPENROWSET ( ). If you wanted to write code that returned […]