SSMS Tools PACK is featured in May issue of SQL Server Magazine
Just as the title says :)
You can read the article here.
Thanx to Kevin Kline for publishing it!
Legacy Comments
|
Bill Graziano
2008-05-05 |
re: SSMS Tools PACK is featured in May issue of SQL Server Magazine Hey, congratuluations! |
|
Mladen
2008-05-05 |
re: SSMS Tools PACK is featured in May issue of SQL Server Magazine thanx :) |
|
Peso
2008-05-07 |
Old version for review? He didn't mention the other cools tools you've incorporated? The image copy? The multiple server execution? |
|
Mladen
2008-05-07 |
re: SSMS Tools PACK is featured in May issue of SQL Server Magazine that's because they're in version 1.0 which will go out tommorow. you got the honor of a pre-release build, Peter. :) |
|
Tony Small
2008-07-15 |
re: SSMS Tools PACK is featured in May issue of SQL Server Magazine Hi, I notice that you always specify SET NOCOUNT ON in your CRUD code. This is to assume that there is never use for SET NOCOUNT OFF which is in fact the default behaviour. For a long time all my stored procedure specified SET NOCOUNT ON until I learned that it prevents Visual Studio client applications from receiving how many rows were inserted, updated or deleted with the .AffectedRows property when calling the stored procedure. This means you can properly determine that the stored proc call worked and is much better than the -1 that is returned when SET NOCOUNT is set to ON. SET NOCOUN ON is only fine for select statements if you don't want this information returned. Kind regards Tony S. p.s. It might be useful to include support for BEGIN TRY...END TRY BEGIN CATCH END CATCH construct. Also maybe considering specifying RETURN @@ERROR in your generated code. Useful tool |