Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
dmaxj
Posting Yak Master
174 Posts |
 Posted - 2012-03-01 : 17:17:17
|
| I recently recycled the SQL Error Logs using 'sp_cycle_errorlog' proc. When I try to view the log in SSMS, I still see the previous logs and not a new log. I can read the new log correctly with 'xp_readerrorlog' - so why is SSMS not updating with the current error logs - the other DBA's can see the logs in SSMS, but I cannot.I even checked the physical location of the error logs - and I can read them in notepad with no problem. Any ideas?Regards |
|
|
GilaMonster
Master Smack Fu Yak Hacker
4507 Posts |
Posted - 2012-03-01 : 17:25:03
|
| Did you refresh object explorer? (right click -> refresh) It doesn't happen automatically--Gail ShawSQL Server MVP |
 |
|
|
dmaxj
Posting Yak Master
174 Posts |
Posted - 2012-03-02 : 09:44:12
|
| Yes, I did refresh :) - this is why this issue is so strange. |
|
|
|
dmaxj
Posting Yak Master
174 Posts |
Posted - 2012-03-05 : 12:34:43
|
| After working with this more, I have determined that I am having the same problem on other SQL Servers. This is very odd. I have searched for updates to SSMS. I am running SSMS 2008 R2 (10.50.1790.0) - Any ideas???Thanks |
|
|
|
dmaxj
Posting Yak Master
174 Posts |
Posted - 2012-03-05 : 14:01:48
|
| Problem solved - I was looking at the SQL Agent Logs and instead of the SQL Server Logs... All is in order. |
|
|
|
|
|
|
missing sql error log files in SSMS