Thanks for the information.

I hope the end of support means that they wont be developing / selling the product anymore, but still would provide support for the existing customers.

Though the...

I use the Administrator's Pocket consultant book

http://www.microsoft.com/learning/en/us/book.aspx?ID=12755&locale=en-us#

cppwiz (4/26/2011)

---

Congratulations! Good writeup of your study resources! It seems like you put a lot of time and effort into studying for this certification.

Did you view your new...

that was the easiest!! Thanks :smooooth:

yes, I could see that I am able to view that report not only in the monitor server, but also in the primary and secondary servers in the log shipping...

When we ran the setup in SQL 2005 and older versions, we used to see the Edition in the welcome screen of setup.

maybe Microsoft had started hating to add that...

well, I would take it as there is no other way possible :hehe:

Thanks for your replies.

But I guess my question has not been put clear. I didnt want to know about the edition of the installed instances. I have "SQL server 2008...

The article was very informative, but I would like to rephrase the below clause in modern terms.

When combining VBScript with DTS and SQL-DMO, I bet almost all administration work can...

I had been thinking that SQL 6.0 was the first version developed for NT. but seems there had been a version 4.21 also :hehe:

these evolutionary versions 4.21, 6.0, 6.5 really...

an accidental cross join is usually the culprit

thats right.. even i had faced a similar issue wherein a large cross join was the troublemaker.

As with all Microsoft products, SQL server 2005 needed a service pack 3 too. And now its already up and running fine!!

Steve, Thanks for caring to reply for this one..

The problem is, I can run the jobs on any server from any other server connected using the TCP protocol (registered with...

No, I didnt have the option to get back that RAM.

Still that problem had not been solved in that workstation, and no one who have seen it had been able...

This issue occurs even if I attempt to run the jobs remotely using sp_start_job.

The same jobs run without issues if I invoke them manually from inside the servers or from...