Yes pretty easy, follow the steps listed below, I compiled them from several posts on the forums . . . works like a champ. --------------------------------------------------------------------------- Ensure your servers are using TCPIP to connect to your SQL database and not Named Pipes. You can check this by opening the file C:\Program Files\Citrix\Independant Management Architecture\MF20.DSN The file should have the following lines: Address=YOURSERVERNAME,1433 Network=DBMSSOCN If not include the above two lines in your MF20.DSN file then run the following command: dsmaint config /user:SQLusername /pwd:password /dsn:C:\PROGRA~1\Citrix\INDEPE~1\MF20.DSN This should successfully connect to the DS via TCPIP. Stop and restart the IMA service. You should check you are now connecting to the DS via TCPIP by the netstat -a command. This should show: on Win2K: TCP yourwtsname:2162 yoursqlservername:ms-sql-s ESTABLISHED on TSE: TCP yourwtsname:2162 yoursqlservername:1433 ESTABLISHED To migrate the DS: 1) On your old SQL server, backup the database using the Enterprise Manager. Select your SQL database which holds the DS and select All Tasks > Backup Database. Select a file location. Select the Verify backup upon completion on the Options tab. 2) On your new SQL server select All Tasks > Restore Database. Type in the name of the database (should be the same as the database name on the old server). You may also need to change the restore location if your database is located in a different path than the old server. 3) Now follow the steps on page 73 of the MetaFrame Admin Guide to create an Admin user for the database. We found you needed to create a new user even though you had an Admin user defined on your old SQL server. Say citrixadmin on your old SQL server, and citrixadmin2 on your new SQL server 4) On each of your terminal servers edit the MF20.DSN file: [ODBC] DRIVER=SQL Server UID=citrixadmin2 <-put in new admin name Address=NEWSQLSERVERNAME,1433 <- enter new SQL server name Network=DBMSSOCN WSID=YOURTSNAME APP=Citrix IMA SERVER=EWSQLSERVERNAME <- put in new SQL server name Description=citrix Run the following command: dsmaint config /user:citrixadmin2 /pwd:password /dsn:C:\PROGRA~1\Citrix\INDEPE~1\MF20.DSN Stop and restart the IMA service. The server should now be accessing the DS on your new SQL server. Create a test published app. Your old Terminal servers in the farm won't see this new published app, but as you migrate your servers to the new DS they will see this test published app. Repeat step 4 for each Terminal Server in the farm finishing with the Data Collector. -------------------------------------------------------------------------- J -----Original Message----- From: Schneider, Chad M. [mailto:CMSchneider@xxxxxxxxx] Sent: Monday, August 19, 2002 6:07 AM To: 'thin@xxxxxxxxxxxxx' Subject: [THIN] DB move from one SQL to another How easy is this? Any pointers? Is it simply a "dsmaint" on one server in the farm, the DS? Our DS is standard, and the SQL DB then resides on a separate SQL server. Chad M. Schneider Technology Analyst II Curwood, Inc. 920-303-7609 - Office 920-909-7609 - Pager =================================== This weeks Sponsor: ThinPrint - High resolution, DRIVER FREE PRINTING with no loss of quality in color. - Removes print spooling and rendering tasks from your terminal server. http://www.thinprint.com =================================== For Archives, to Unsubscribe, Subscribe or set Digest or Vacation mode use the below link. http://thethin.net/citrixlist.cfm =================================== This weeks Sponsor: ThinPrint - High resolution, DRIVER FREE PRINTING with no loss of quality in color. - Removes print spooling and rendering tasks from your terminal server. http://www.thinprint.com =================================== For Archives, to Unsubscribe, Subscribe or set Digest or Vacation mode use the below link. http://thethin.net/citrixlist.cfm