Hi,

we installed BES on a SQL2000 DB.
What is the procedure to move the DB to a new SQL2005 server?

Thanks,

Marc

Welcome to BBF!

Try this article:

BlackBerry Search Results

That should cover everything.

Let us know if you have any questions.

You can always move the database without running the create a new database utility but you will need to add the sysmessages to the 2005 master database or you will get a schema error and the dispatcher service will not start. Below is the code to retrieve those messages from the SQL 2000 database.

select 'exec sp_addmessage '+convert(varchar,error)+
', '+convert(varchar,severity)+', '+''''+description+''''
from master..sysmessages
where error > 49999
order by 1

you should get something that looks like this:
exec sp_addmessage 60002, 16, 'Unable to add new BlackBerry Agent "%s" AgentID=%d Machine Name=%s'
exec sp_addmessage 60003, 16, 'Unable to add MDS Mapping. Duplicate Pin: [%d]'
exec sp_addmessage 60004, 16, 'Unable to enable/disable MDS server as push server - entry does not exist.'
exec sp_addmessage 60005, 16, 'Unable to add new ServerConfig entry for ServiceName "%s" MachineName "%s".'
exec sp_addmessage 60006, 16, 'Unable to %s ServerStats entry for ServiceName "%s".'
exec sp_addmessage 60007, 16, 'Unable to %s UserConfig entry for SMTPAddr "%s" ServiceName "%s".'
exec sp_addmessage 60008, 16, 'Unable to %s UserStats entry for SMTPAddr "%s".'
exec sp_addmessage 60009, 16, 'Unable to add SyncDeviceMgmt entry because there is no UserConfig entry for %d.'
exec sp_addmessage 60010, 16, 'Unable to %s entry because there is no UserConfig entry for %s.'
exec sp_addmessage 60011, 16, 'PendingServerConfigId [%d] not found in ServerConfig table - User not added'
exec sp_addmessage 60012, 16, 'Deleting of the default Policy is not allowed.'
exec sp_addmessage 60103, 16, 'Unable to update the License record for BESRouter [%s]'
exec sp_addmessage 70000, 1, '%s TableName=%s'
exec sp_addmessage 70001, 1, '%s TableName=%s'
exec sp_addmessage 70010, 1, '%s,%i TableName=%s'
exec sp_addmessage 70011, 1, ' TableName=%s'

It's just as easy to run createdb.exe as it is to do what you have suggested. Especially if the person is not versed in SQL. But that is the first time I've seen that before. Pretty neat as a workaround to running createdb.exe, but you're not skipping any steps or making the process any faster.

Not trying to rain on your parade here though, so don't take this as an attack on your post. Mind if I ask where you got the command?