I want some Moore

Blog about stuff and things and stuff. Mostly about SQL server and .Net
posts - 216, comments - 2277, trackbacks - 33

My Links

Advertisement

News

Hi! My name is 
Mladen Prajdić  I'm from Slovenia and I'm currently working as a .Net (C#) and SQL Server developer.

I also speak at local user group meetings and conferences like SQLBits and NT Conference
Welcome to my blog.
SQL Server MVP

My Books

SQL Server MVP Deep Dives 2
The Red Gate Guide to SQL Server Team based Development Free e-book
My Blog Feed via Email
Follow MladenPrajdic on Twitter
Users Online: who's online

Article Categories

Archives

Post Categories

Cool software

Other Blogs

Other stuff

SQL stuff
<< SQL Server 2005: Get full information about transaction locks | Home | Ease your SSMS experience: SSMS Tools PACK 1.0 is out! >>

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!

Print | posted on Sunday, May 04, 2008 1:57 PM | Filed Under [ SQL Server Misc SSMS Tools Pack ]

Feedback

Gravatar

# re: SSMS Tools PACK is featured in May issue of SQL Server Magazine

Hey, congratuluations!
5/5/2008 1:22 PM | Bill Graziano
Gravatar

# re: SSMS Tools PACK is featured in May issue of SQL Server Magazine

thanx :)
5/5/2008 3:33 PM | Mladen
Gravatar

# Old version for review?

He didn't mention the other cools tools you've incorporated?
The image copy? The multiple server execution?
5/7/2008 4:44 PM | Peso
Gravatar

# 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. :)
5/7/2008 4:45 PM | Mladen
Gravatar

# 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
7/15/2008 10:30 AM | Tony Small
Comments have been closed on this topic.

Powered by:
Powered By Subtext Powered By ASP.NET

Copyright © Mladen Prajdić