Blackberry SQL Issues

Overview

This section are issues that relate more to the blackberry and SQL than just blackberry

Dispatcher Service Terminated

In a large company we have a shared SQL service. We have some sandboxes that we can have SA Priv access to but we don't have this level of access to the production servers. They don't trust us and I don't blame them.
We need to move from an old SQL 2000 server to a new SQL 2005 server. We moved the SQL DB and pointed the BES server to the new SQL 2005 server.
When the BES came up the Dispatcher Service Terminated with service-specific error 5608 (0x15E8)
This is the only service that failed to start. When I contacted RIM support I was told this was a known error. I needed to run the install and create a new blank DB with an SA Priv ID on the 2005 server. This would update the master table on the 2005 server. I could then point the BES servers back to the database I moved and everything would work.
Our shared service team will not give us SA Priv. They ask that RIM tell us what table they update with what info and the will manually do the update. (out side the DB used by the BES) Rim have said SA Priv is a pre-req and if we need this info we must work it out for ourselves. (So helpfull)

Our shared service will not even give us SA Priv for the install and take it away after.
What I have found is that :-
In this instance not running createdb.exe on a new server can cause 2 issues: no sql jobs being created and entries are not placed in the sysmessages table resulting in a 5608 error on service start up.
The job that runs is called errors.sql You can sarch for this on the server. We then gave it to our SQL team and they ran it to put the messages into the sysmessages queue. But we still got the same problem. We got no soluton for this. In the end the SQL Team had to give us SA Priv. We created a dummy db then deleted it and then when we moved the db from 2000 to 2005 it worked.