MSDE to Full SQL database
I/NET site currently using MSDE and wanting to convert to Full SQL database
The size of a site may have grown beyond the limits imposed by the existing SQL database.
The site may want more information available in the database thus pushing beyond the size of the current database limits.
Lessons Learned Article 4006: For information on your current SQL compatibility
Here is a list of Lessons Learned articles which may be useful with installations of I/NET:
- Lessons Learned Article #8274: Installing I/NET Seven 2.42 on a 64-bit operating system
- Lessons Learned Article #11292: Equalize Client in Windows 7 64-bit with I/NET 2.42
- Lessons Learned Article #7191: SQL 2008 and Windows 7
- Lessons Learned Article #8152: SQL 2008 Install Tips
- Lessons Learned Article #8235: Installing 2008 SQL R2 Express for 2.42
The Windows 7 HAS to be the professional version to work with I/NET. The Home Edition will not work.
Assuming the site is using File Equalization it requires FULL SQL 2005 on the 32Bit and Full SQL 2008 R2 on the 64Bit on the File Master. The other PCs can have the express version of SQL, but the Express has to be the same version.
If database size is expected to get above 4Gig, then full SQL would be needed on the FileMaster as well as each Equalized Client
There is really no way to make a comprehensive list of every single step required at every site. Site knowledge is key but this list may be beneficial. It is assumed the site has a Filemaster (FM) and several Equalized Clients (EQ).
- Make a backup of db, then make a second backup. Copy those onto another location for safekeeping.
- Make sure all firmware at site is at correct revision
- Save archive information on each computer
- Make note of each pc for I/O configuration information
- Bring each EQ computer to a stand alone state including Filemaster
- Make backup of each pc’s db and archive info, graphics pages, etc for safe keeping
- Discover what database is on each EQ and FM. I assume the FM has MSDE, which all the others would have as well.
- From FM uninstall I/NET
- Remove all the I/NET folders from FM
- Remove SQL on FM
- Install Full SQL on FM
- Install I/NET and use Full SQL instance on FM
- Create blank database on FM
- Check that db from SQL Management Studio Express
- Restore db from backup on FM
- Repeat steps 8 – 13 on each of the StandAlones except using SQL Express
- In I/O configuration, point each StandAlone at FM which makes them EQs
- Setup your archiving config for site
- Go through each link in Network Configuration and check for communication
- Go to AMT and check messages