• sibir1us (4/20/2009)


    I like your article. Seems interesting, and also a good idea. However, a several drawbacks could be:

    1. getting that "own SQL Server "SQL_Admin"" might be a bit hard

    2. how many DBAs are actually savvy .NET coders?

    3. creating how MANY linked servers

    Hi, thanks sibir1us. I agree getting your own server may not be easy but it's not a must, you could use an existing one. The procs aren't resource hungry at all.

    Hey, you don't need to be .Net savvy as these articles will be step by step guides. It's an intro to .Net that I'm hoping will tempt DBAs to use their own existing T-SQL skills to build anything they want. With .Net the world is your oyster. And once you're building in ASP.Net, you can build .Net windows forms or anything on the framework, it's all the same. I have deliberately chosen pure .Net and purposely tried to keep away from standard SQL Server tools to monitor, as programatically .Net opens up the world to anything and everything.

    SSIS and SSRS are very thorough tools and can achieve the same. But as a DBA (and not a developer) I think it's more fun using .Net. As a side project, it has taken me over a year to build this suite of reports, to cover *all* my needs, graphs, bells and all, totalling 39 reports. Maybe you could kindly share some of your reports with us. It would be good to bounce ideas.

    Kind regards

    Drew