Hi,

I've inherited a pilot of 20 7250 devices running on BES 4.0.3 and using exchange. The 20 users are across 4 different Exchange servers.

The BES server connects to a SQL 2000 database hosted on another machine.

Last week, we finished 2 weeks of troubleshooting to move the SQL database from one machine to another (a dedicated SQL database server). Main reason for the move was due to ODBC connectivity issues being reported in event log.

I've spent a large part of this week on calls with Telstra and RIM to troubleshooting activation issues that now appear to relate to the DB.

When we cut over, we had ODBC connectivity from the System DSN and the BES config tool showed connectivity. During troubleshooting this week we found the ODBC connectivity failed.

On further investigation we found the default database for the "besadmin" user that is in SQL had a different default database. Our DBA reckons this changed as part of a reboot and is a "known issue with SQL".

When we changed the default database and ran the 3 jobs on the SQL server manually and normal service was restored on the BES.

This seems a bit suspect to me - just wondering if anyone else had experience of this?

Thanks,

Chris

Hi,

It looks like i am just about to do excatly what you did. Did you find anymore problems trying to move the database?

Thanks.

Lee.

Hi Lee,

Once we restored the connectivity the database side of things appeared to be OK. We're now starting a fresh installation of BES 4.1 pointing to a SQL 2005 database and will retire the SQL 2000 installation.

Chris

We're now starting a fresh installation of BES 4.1 pointing to a SQL 2005 database and will retire the SQL 2000 installation.

Don't forget upgrade the schema to 4.1 standard before pointing 4.1 Server to the SQL 2005,from what you mentioned it seems you still running a 4.0.1 database

We still have most users on the 4.0.1 BES using the SQL 2000 database. We now have a clean set up of BES 4.1 that is pointing to a new SQL 2005 database and will migrate all users across.

Decision was made to start a fresh new database as we are closing the pilot to make this a prod env plus there was some suggestion by RIM of corruption in our SQL 2000 database.

Cheers,

Chris