Quote:
Originally Posted by juwaack68
We started out with MSDE (Exchange shop) and I moved to a remote SQL server earlier this year. My primary reasons for doing so were:
- Automatic backup of the SQL database (kinda handy in the case of a failure)
|
This one is easy to get around...just run a scheduled task that executes the OSQL backup command, and you can have it run weekly backups with no issue. Other command line parameters are available if you wish to perform incremental, etc.
Quote:
Originally Posted by juwaack68
- Too many users on the box (we were at approx 225 users at the time, now at close to 400 on that BES)
|
We were actually running 330 on MSDE with no issue. The database (this was Exchange) was sitting at around 220Mb or so, and this was including wireless backups.
There is a 2Gb limitation to MSDE (4 Gb to SQL Express), so there is something to think about. There is also a limitation to how many transactions you can process at one time, so this should really be the reason to go to SQL.
If you have SQL, I would definitely move to it, but I would perform an installation with the same version of BES, have it create the database and all the required tables, stored procedures, triggers, etc., then restore your database backup to it (pending you are moving forward or laterally in technology - - i.e. don't try to move from SQL Express 2005 to SQL 2000,
although not many folks I would imagine have tried this).
Rob