| Author |
Topic |
|
blindman
Master Smack Fu Yak Hacker
2365 Posts |
 Posted - 2007-07-06 : 14:43:11
|
| I open up the SQL Server Agent Job window, and I can't see details under the General, Steps, Schedules, or other tabs unless I am running SSMS directly on that server. So much for remote management, eh?Anybody else experiencing this problem?Anybody else notice that jobs may fail to complete correctly without raising any errors or logging any issues?Anybody else remember when, a year ago, SQL Server was a good product?Anybody think Microsoft is listening?Anybody? Buehler? Buehler?e4 d5 xd5 Nf6 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2007-07-06 : 14:57:20
|
| I am not having any of these issues with my SQL Server 2005 database servers. I almost never connect to the server via SSMS directly on the server. I do everything remotely.I would suggest checking the obvious things such as permissions, but I'm sure you've already done that.Tara Kizerhttp://weblogs.sqlteam.com/tarad/ |
 |
|
|
blindman
Master Smack Fu Yak Hacker
2365 Posts |
Posted - 2007-07-06 : 15:31:33
|
| Yeah. I've got full permissions. And I've seen this issue on every 2005 server I administer at every one of my client sites.e4 d5 xd5 Nf6 |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2007-07-06 : 15:36:51
|
| I've got 56 SQL Server Enterprise Edition instances installed with half of them in production. Most are running sp2 with GDR2, some are running sp1. Most are on clusters, but not all.Perhaps it's just a client issue though. Have you installed sp1 or sp2 on your client?Do you have a premier contract with MS, perhaps you could get your TAM working on this?Tara Kizerhttp://weblogs.sqlteam.com/tarad/ |
|
|
|
Michael Valentine Jones
Yak DBA Kernel (pronounced Colonel)
7020 Posts |
Posted - 2007-07-06 : 15:39:29
|
| I have never seen those issues SQL Server 2005, and we have it installed on 18 servers.I assume you have SQL Server Service Pack 2 installed with the SP2 critical update?http://support.microsoft.com/?kbid=933508CODO ERGO SUM |
|
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-07-06 : 16:14:29
|
| Does client have same sp level as servers do? |
|
|
|
blindman
Master Smack Fu Yak Hacker
2365 Posts |
Posted - 2007-07-06 : 17:31:47
|
| Well, now I see that when I double-click on the job or right-click and select properties, instead of bringing up the properties for the job or informing me that I can't edit the job it simply brings up a New Job window.Again, no error messages or warnings.My login has full administrative privileges to the database server. The jobs run maintenance plans that I created under my login.I'm really fed up with this crap. 2005 is one half-assed product. I'd go back to rolling my own backup and maintenance scripts except that I have to be able to implement standard solutions at multiple clients.e4 d5 xd5 Nf6 |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2007-07-06 : 17:42:08
|
| Bruce,You didn't answer whether or not you've got sp1, sp2, sp2 with GDR2 on your client. I always patch my client anytime I roll out a new service pack or patch. Updating the client has been recommended starting at SQL Server 7.0, I believe.Tara Kizerhttp://weblogs.sqlteam.com/tarad/ |
|
|
|
Michael Valentine Jones
Yak DBA Kernel (pronounced Colonel)
7020 Posts |
Posted - 2007-07-06 : 17:51:50
|
| I would think that you should be able to identify right away if it is a client issue by trying it from a different PC that has the client software installed. If it works Ok from a different PC, then your problem is most likely on the client side.CODO ERGO SUM |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2007-07-06 : 17:56:05
|
| And hopefully the different PC with the client software installed would be one that is patched.Tara Kizerhttp://weblogs.sqlteam.com/tarad/ |
|
|
|
|
Can't see Job Details unless logged into server.