September 10, 2006 at 11:48 pm
Since a few weeks I am working with SQL2005. Bought some books, read BOL and did some tutorials. I am not unanimously happy with the new stuff of 2005. There always is the question, why things have to be rearranged and done differently then in previous version.
To be sure, there are a lot of nice improvements, but there is also a lot of irritations. To be very specific: it seems I can not see at a glance if jobs have failed or not. Ofcourse I can run a script whcih tells me the jobstatus, but that's not an improvement.
Is there an option which shows me jobstatus, which I have missed?
Greetz,
Hans Brouwer
September 11, 2006 at 6:10 am
Hans,
while I can agree wwith you on the point that not all of the changes made in SQL 2005 are a real improvement, I must say the the job management is one of the things I like quite a lot. What's wrong with Job Activity Monitor?
Markus
[font="Verdana"]Markus Bohse[/font]
September 11, 2006 at 6:40 am
Ah right, job activity... As you guessed, I am fairly new at 2005.
What is wrong? Well, for instance, you have to start something extra, which opens in its own window? It's getting used to it, I guess.
Tnx for responding though.
Greetz,
Hans Brouwer
September 12, 2006 at 3:56 am
Hmm,
I actually like the fact that it opens in it's own window. Gives me the possibility to leave it open while doing other tasks in SSMS.
Markus
[font="Verdana"]Markus Bohse[/font]
September 18, 2006 at 9:14 pm
The thing that ticks me off the most is the lack of ability to debug a stored procedure without the full Visual Studio 2005 Professional (i.e. not the lightweight version that ships with the product).
I really can't imagine what the Program Damager that thought of that was thinking!
September 19, 2006 at 1:06 am
I really can't imagine what the Program Damager that thought of that was thinking!
He probably didn't...
Greetz,
Hans Brouwer
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply