The Apex database will work great with all versions of SQL Server 2000 and above (including the new SQL Server 2008) if you follow these notes. This includes the "free" versions MSDE and SQL Express. Our preliminary testing shows that performance is as good or better than SQL Server 2000.
- Be sure that your hardware can support SQL Server 2005/2008. You need considerably more powerful hardware to run the newer versions of SQL Server, and in our experience if you do not have adaquate hardware you will get very poor results.
- Apex will only run in a "default instance". Named instances are not supported.
- Leave the Apex database in Database Compatability Mode 80 (SQL Server 2000).
- Be sure to load the Microsoft SQL Server 2005 Backward Compatibility Components. Note that the 2005 version is applicable to 2008 as well. You only need to install the SQL-DMO portion. Install this both on the server and on any Apex workstaton that will be doing Advanced User Security user maintenance, SQL Query operations, or backups.
- Remember that once the database has been used by SQL Server 2005 or SQL Server 2008 you can no longer detach it and run it on a SQL Server 2000 system. This is not an Apex issue -- it is true for any database. Once SQL Server touches a database regardless of the compatability mode it can not be moved back to an earlier server version. Note also that backups cannot be moved backwards, so you will want to carefully plan your migration.
If you are installing a new Apex database on SQL Server 2005 or SQL Server 2008 using the setup program on the Apex CD you will run into one minor problem. The database will install correctly and will be fully operational, but the setup program will not be able to create the ApexProg user account. This is because of a difference in how SQL Server 2005/2008 handles user security. You will need to manually create the ApexProg account and give it dbOwner access to the Apex database. Call Vulcan Software support if you need to do this and we will be happy to help you.