I learned something today about SQL 2008 and BizTalk's SQL agent jobs. You must leave all BizTalk databases recovery model to "Full". I encounted a database set with the recovery model that was changed to "Simple" and it caused the agent's jobs to fail.
The reason for this is that "TRUNCATE_ONLY" has been deprecated for SQL Server 2008. This flag forces you to keep the recovery model as full. When I changed it back everything began funtioning normally again.
Showing posts with label sql agent. Show all posts
Showing posts with label sql agent. Show all posts
Thursday, January 28, 2010
Tuesday, January 26, 2010
How to solve "Unable to determine if the owner has server access" error
This error message popped up all of a sudden during a load test with heavy volume.
Turns out to be a well known culprit to lots of BizTalk errors: the SQL Agent jobs were not running. Since we had just deployed to a test environment, and it was a new server, I didn't check to the Agent to see if it was running.
When I teach the class, I always mention this check, so I didn't follow my own advice. Anyway, the database server logs grew wildly and caused a shutdown.
When I configured and ran the jobs everything was fine, but it took a while for everything to complete.
Turns out to be a well known culprit to lots of BizTalk errors: the SQL Agent jobs were not running. Since we had just deployed to a test environment, and it was a new server, I didn't check to the Agent to see if it was running.
When I teach the class, I always mention this check, so I didn't follow my own advice. Anyway, the database server logs grew wildly and caused a shutdown.
When I configured and ran the jobs everything was fine, but it took a while for everything to complete.
Subscribe to:
Posts (Atom)
