I've migrated a notification service solution from SQL 2000 to SQL 2005. The solution works fine but when I start the NS-Instance on SQL 2005 the CPU goes up to 100% and stays there.
I could not follow the migration advice on MSDN because the new SQL 2005 DB is on a different server than SQL 2000. So i figured out my own workaround. The solution works fine but I don't know why the CPU goes up on 100% !!
Here's my migration szenario:
1. I made a backup of the two instance databases from SQL 2000
2. On a diferrent server I installed SQL 2005
3. I adapted the ADF-file (changed the notify syntax and in my case new server name and paths)
4. In SQL mmanagement Studio 2005 I created a new Instance with the adapted ADF-file
5. I Restored the two instance DB's in SQL 2005 to get the old data
6. Upgrade of the NS-Instance
7. Update of the Instance DB's with the new ADF file in NS-Console
8. Once again update in SQL Managament Studio (without it it would't work!)
9. Registeration of the Instance
10. Enabling Instance
11. Start Instance
Can anybody help ?
Hi Semilogic -
Here's a link to an article I wrote for Simple-Talk a while back that discusses upgrading an instance to 2005 from 2000. Maybe it'll help prove your methodology.
As for the 100% CPU utilization - it may be trying to catch up. When an instance goes offline for a while and is then started, it immediately attempts to try to catch up by processing all of those quantums that it missed while stopped.
HTH...
Joe
|||
Well, duh!!!
Here's the link:
http://simple-talk.com/sql/sql-server-2005/building-effective-sql-server-notification-applications-part-i/
|||It works now!!
The transaction log file was full !!
Thankssql
No comments:
Post a Comment