Installing the PC-Kits SQL Database

1 Installing the PC-Kits SQL Database The Network edition of VHI PC-Kits uses a SQL database. Microsoft SQL is a database engine that allows multiple users to connect to the same database. This document will discuss how to install Microsoft SQL and Microsoft SQL Management Studio, and how to attach and configure the VHI PC-Kits SQL database. When you install the VHI PC-Kits Network edition, you have to choose where the SQL database will be installed, either on a Database Server or a Primary workstation (Peer to Peer install). In either case, the PC-Kits installer will normally handle all the configuring and installing of SQL and the database. But occasionally, something goes wrong and SQL is not correctly configured. Also, many customers will already have a designated SQL server and will not want to use the PC-Kits installer. Hopefully this document will provide enough details that a user can install and configure SQL and setup the database without needing VHI Tech support (primarily for customers that need assistance outside of our support hours).

2 Table of contents A. Installing Microsoft SQL 2014 Express. 3 B. Installing Microsoft SQL Management Studio.. 15 C. Launching SQL Management Studio... 19 D. Attaching the VHI PC-Kits database to SQL. 21 E. Setting up the PC-Kits database logins.. 26 F. Verify that SQL is configured for Mixed Mode Authentication. 31 G. Upgrading the PC-Kits database from an older version of PC-Kits.. 33 H. Backing up your PC-Kits database.... 36 I. Restoring the PC-Kits database... 37 J. Moving the PC-Kits database from one server to another... 43 K. Changing the database settings in the PC-Kits License Manager. 46 L. PC-Kits 3.0 thru 4.1 and SQL 2008 or later (SQL DMO)... 50

3 Installing Microsoft SQL 2014 Express Microsoft SQL comes in many editions but basically there are the paid editions (Standard, Enterprise, etc.) and the free edition which is SQL Express. PC-Kits comes with SQL 2014 Express which is free but it will also work with the paid editions if you prefer. There are also many versions of SQL: 2000, 2005, 2008, 2014, 2016. Version 4 of PC-Kits will work with SQL 2005, thru SQL 2014. SQL 2016 is probably fine, we just have not completed a test run with it yet. Version 3 of PC-Kits will work with SQL 2000 thru SQL 2014. While the PC-Kits program works with most versions of SQL, the PC-Kits installer did not until PC-Kits version 4.2. Prior to that, the installer would only work with a default instance of SQL 2000 or SQL 2005. So it was often necessary to manually install and configure SQL 2008 and later. We are currently shipping SQL 2014 Express with PC-Kits 4.2. This section details how to install SQL 2014 Express. Use these instructions if you need to manually install SQL. You do not need to run this install if SQL was already installed when you ran the PC-Kits install or you already have a copy of SQL on the machine that you wish to use. We use a 32 bit version of SQL but you are welcome to use the 64 bit version if you want.

4 The install files for SQL 2014 Express are included on the PC-Kits DVD and also in the PC-Kits download. Browse through our install files and locate: SQLEXPR_x86_ENU.exe. Double click this file to start the SQL install. You can also download the install files directly from Microsoft if you do not have our DVD handy or wish to use a different version of SQL. I recommend that you download the With Tools choice because that also includes SQL Management Studio. Look for the file called SQLEXPRWT_x64_ENU.exe (get the x86 version if you are on a 32 bit computer).

5 When you start the install, it will ask you were you want to extract the files too, you can accept the default option or choose another location. Next you are presented with the Installation Center. Choose New Install. Next is the License Agreement, accept it.

The install will now check your computer to make sure it meets all the SQL requirements. 6

If it finds any issues, you will have to fix them before you can continue with the install. Next you are asked if you want to use Microsoft Update. I recommend that you do select updates but it is not required. 7

8 On the feature Selection screen, accept the default choices. If you don t want SQL to install on the C: drive, you can change the install directories. You can also unselect SQL Server Replication if you want as it is not required by PC-Kits.

Instance Configuration: Microsoft allows you to install multiple copies of SQL on a single computer. Each copy is called an Instance. When you install SQL, you have to give a name to the instance you are installing. You can choose either a Default Instance (the generic name that Microsoft used to default to) or a Named Instance where you specify a name. For PC-Kits, we normally name our instance VHI_PCKITS but PC-Kits will also work with a Default Instance or an instance name of your choosing. 9

On the Server configuration screen, you will see that the SQL Server Browser is Disabled. Click the down arrow and set it to Automatic. If you chose a Default Instance on the previous page, then it is not necessary to enable the Browser Service. 10

11 On this screen, change the Authentication Mode to Mixed Mode. Create a password for SQL. The password must meet your server complexity requirements. Be sure to record your password in case you need it in the future to manage SQL. The current user account should be listed in the SQL Server Administrators box, this user will have full permissions to SQL. If desired, you can click Add to add other users or Active Directory groups. If you do not want the SQL data files to be stored on the local C: drive, you can click the Data Directories tab and change the default locations.

12 The next screen shows you the install progress. Be patient. Some versions of SQL can take up to 30 minutes to install. When finished, SQL will show you a list of everything it installed and whether it succeeded or not. If everything succeeded then you are done installing SQL.

13 Next, you have to configure SQL to allow connections from other computers. Go to Start, All Programs or Apps, and open the SQL Server Configuration Manager. Open SQL Server Network Configuration. Click on Protocols for VHI_PCKITS. On the right side of the screen, right click on TCP/IP and choose Enable.

14 After TCP is enabled, you have to restart the service. On the left side of the screen, click on SQL Server Services. On the right side of the screen, right click on SQL Server (VHI_PCKITS) and choose Restart. After it has restarted, close the SQL Server Configuration Manager. At this point, SQL should be installed and ready to use. If you manually installed SQL because it failed when you ran the PC-Kits setup, you can now uninstall PC-Kits and then reinstall it and everything should be working. Otherwise, the next step in a manual install is to install SQL Management Studio.

15 Installing Microsoft SQL Management Studio Management Studio is the graphical interface to SQL that allows you to manage databases. We will use it to attach the pckits database to SQL and setup all the logins. If you downloaded and installed SQLEXPRWT_x64_ENU.exe in the previous section, you can skip this section because SQL Management Studio should already be installed. We include the setup file for SQL Management Studio on our DVD. Due to the large size of this file, we do not include it in our PC-Kits download. If you downloaded PC-Kits, then you will need to download SQL Management Studio directly from Microsoft. Search the internet for SQL 2014 Express SP2. Click the link for Microsoft SQL Server 2014 Service Pack 2 (SP2) Express. Then click Download. Scroll to the bottom of the list and choose SQLManagementStudio_x64_ENU.exe (only choose the _x86 file if you are on a 32 bit computer). If you have our DVD, launch it from there.

16 When you start the install, it will ask you where you want to extract the files to, you can accept the default option or choose another location. Next you are presented with the Installation Center. Choose New Install.

As in the previous install of SQL, accept the license agreement, fix any issues found by the rule check, and allow Microsoft updates. When you get to the installation Type, select Perform a new installation of SQL Server 2014. 17

18 On the feature selection screen, leave all items selected. Finish the install, the last screen should indicate if everything installed correctly. Reboot if asked.

19 Launching SQL Management Studio Open SQL Management Studio but be sure to right click it and choose Run as Administrator when you open it. Connect to the VHI_PCKITS instance (unless you customized the instance name when you installed SQL). The Server Name will be the name of your server \VHI_PCKITS. If you are connecting to a Default instance of SQL, just use the server name. If your user account has admin rights to SQL, you can connect using Windows Authentication. If you do not have admin rights, change it to SQL Authentication and use sa as the user name and then enter the password for SQL (this password was created by the person who installed SQL). Note that you can enter a different computer name in the connect window. Management Studio does not need to be installed on the same computer as the SQL server. You can manage multiple SQL servers from a single install. It is also backwards compatible with older versions of SQL. So with the 2014 edition of

Management Studio you can also connect to SQL 2012, 2008, 2005, and 2000. If you are moving the pckits database from one server to another, you can connect to the original server and do a Backup and then connect to the new server and do a Restore. 20

21 Attaching the VHI PC-Kits database to SQL There is an empty pckits SQL database on our DVD or download. This empty database needs to be attached to SQL. Note: You cannot just go to SQL and create an empty pckits database. Such a database would not have any of the tables or stored procedures needed by PC- Kits. If you ran the PC-Kits setup and installed the Database Server option but setup failed or SQL did not install, then the empty pckits database may already be on your hard drive waiting to be attached. If you are doing a manual install, then you need to copy the empty database from the PC-Kits DVD or download to your hard drive. Browse the install files and locate MSDESE~1.cab. Double click the cab file to open it. You will see a file called pckits or pckits.mdf. Right click this file and choose Extract. Browse to a folder on your hard drive and save the file. The default location for the PC-Kits data folder is C:\Program Files (x86)\visual Health Information\VHI PC-Kits\Data. However, you can place the file anywhere on the local hard drive that SQL has access to. You can use the default data folder for SQL if you prefer.

22 Once the empty data file has been copied to your hard drive, open SQL Management Studio and connect as detailed previously. Right click on the Database folder and choose Attach.

On the Attach Databases screen, click the Add button. 23

Browse to the folder where the empty pckits.mdf is located (C:\Program Files (x86)\visual Health Information\VHI PC-Kits\Data, by default). Click on the pckits.mdf file and then click Ok. 24

25 In the lower half of the Attach Databases window you will now see a pckits.mdf and a pckits_log.ldf. Notice that the path listed for the LDF file is invalid. Click on the LDF file to highlight it. Click the Remove button. SQL will create a new log file in the same folder as the MDF file unless you select a different folder. Click Ok. The pckits database should now be listed under the Database folder.

26 Setting up the PC-Kits database logins Before PC-Kits can connect to SQL and access the pckits database, you must first create a login and give it permission to access the database. SQL allows access either through a SQL Login or through Windows Authentication. By default, Pc- Kits is configured to use a SQL login but you can switch to Windows Authentication if you prefer. The default SQL login for the pckits database is; Login = pckits_login, Password = pckits_password, User Mapping = pckits_user. The database name, login name, and password can all be customized if you wish. You will need to enter your customized values into the PC-Kits license manager under the database settings. You can also change the database Authentication to Windows. Then you need to add your Active Directory users/groups to SQL and give them access to the pckits database with the User Mapping = pckits_user. To create the default login, open SQL Management Studio as described previously. Open \databases\pckits\programmability\stored procedures\. Right click on createclientaccount and execute it.

You are prompted for parameters, just click Ok. 27

28 If you wish to verify the login was created properly, go to the Security folder (Note: There are two Security folders, one in the pckits folder and one below the Databases folder, you want the second one). Open Logins and you should see a login called pckits_login. Right click it and select Properties (if you are manually creating the login, right click the Login folder and choose New Login). You can see that it is set to SQL Server Authentication and that Enforce password policy is unselected. That is because our default password is not complex enough. If you want a complex password, enter your own and turn on Enforce password policy. Be sure to enter your custom password into the PC-Kits license manager database settings.

29 Under the Select a page menu, click User Mapping. Select or highlight the pckits database in the upper window. Make sure pckits_user is selected in the lower window (leave Public checked also). Click Ok. If the database has been restored from another server, you may get an error message that the login cannot be created because it already exists. In this case, click Cancel. Then go to \databases\pckits\security\users. You will see a pckits_login. Right click and delete it. If asked, say ok to delete the associated schema. Now you can go back to the instructions above to create the new login.

30 It is also possible to create the login from a command prompt if you do not have SQL Management Studio installed. Run an elevated command prompt (right click cmd.exe and choose Run as Administrator). Type the following commands: Sqlcmd E S servername\vhi_pckits 1> use pckits 2> go 1> createclientaccount 2> go 1> quit

31 Verify that SQL is configured for Mixed Mode Authentication When SQL is installed, you choose to allow either Windows Authentication (default setting) or both SQL and Windows Authentication (Mixed Mode). PC-Kits uses SQL authentication by default. If you installed SQL, you may want to verify that Mixed Mode is enabled. Open SQL Management Studio as discussed previously. In the upper left column you see your SQL server name. Right click on the server and choose Properties.

Click the Security option. Make sure that SQL Server and Windows Authentication mode is selected. Click Ok. If you change this setting, you will have to restart the SQL service before it takes effect. Make sure that no users are connected to any of the SQL databases before restarting. You can right click the server name and choose Restart. 32

33 Upgrading the PC-Kits database If you upgrade your version of PC-Kits from an older version, for example, 3.4 to 4.2 or 4.1 to 4.2, it is usually required that the pckits SQL database is upgraded as well. If you used the PC-Kits setup to install your pckits database, then running setup will upgrade the database for you. These instructions are for manually upgrading the database. There is a file called migrate.sql on our DVD or download that is used to upgrade the database. Open SQL Management Studio as previously discussed. Go to File and choose Open, and then File.

Browse to the PC-Kits install files and open migrate. 34

35 In the middle window you see the script that we are about to run. You do not need to make any changes to the script unless you have customized the database name. If so, change the line that says use pckits to use custom_name. On the menu bar click!execute. Now the database should be upgraded. You can close the migrate.sql window. It is also possible to run migrate from a command prompt if you do not have SQL Management Studio installed. Run an elevated command prompt (right click cmd.exe and choose Run as Administrator). Type the following command: Sqlcmd E S servername\vhi_pckits -i c:\temp\migrate.sql -d pckits This assumes that the migrate.sql file has been copied to the c:\temp folder.

36 Backing up your PC-Kits database Your PC-Kits database should be backed up on a daily basis. There are several ways to properly backup a SQL database. You should not rely on a backup program that copies files from the hard drive. SQL runs as a service and the physical file on the hard drive is often in use and may not copy properly. If you have backup software that is SQL Aware, then you should see a list of available SQL databases to backup. Select the pckits database. If you have installed Full SQL (not SQL Express) then you can create a SQL Agent job to backup the pckits database. If you have the PC-Kits client installed on your SQL server, you can open PC-Kits and sign in as Administrator. Go to the File menu and choose Backup database. If you have SQL Management Studio installed, you can right click the pckits database, chose Tasks, and then choose Back Up. You can click the Add or Remove buttons if you want to change the location of the backup file. Read the topic Installing Microsoft SQL Management Studio if you want to install it. From a command prompt: Run an elevated command prompt (right click cmd.exe and choose Run as Administrator). Type the following command: Sqlcmd E S servername\vhi_pckits -Q"backup database pckits to disk='c:\temp\pckits.bak' with init" The backup would be placed in the C:\temp folder. Change the path if you wish. Once the pckits.bak file is created, it can be backed up with your normal backup software or moved to a backup device. If you need to create your own automated backup, you can run the above command from a batch file and then use Windows Task Scheduler to run it as often as you like. Be sure to run it with elevated privileges.

37 Restoring the PC-Kits database Just like backing up the database, there are a variety of ways to restore a SQL database. If you have the PC-Kits client installed on the SQL Server and you previously created a backup using the PC-Kits client, then you can just use the client to restore the database. Right click the PC-Kits icon and choose Run as Administrator and then sign in as the Administrator. Go to the File menu and choose Restore Database. Choose Path and then browse to the folder were the PC-Kits backup files are, click OK and then select the backup that you want to restore. After you click Restore, you are asked to close the PC-Kits program. Close it. Right click the PC-Kits icon and choose Run as Administrator. Your data should now be restored. Note: You cannot restore a backup from an older version of PC-Kits using this method (i.e. restore a version 3.4 backup to a current 4.2 version of PC-Kits). After restoring an older version database, follow the instructions in the Upgrading the PC-Kits database from an older version of PC-Kits section of this document. To restore a backup using SQL Management Studio, open Management Studio as described previously. Right click the Databases folder and choose Restore Database.

38 Under Source, click the Device option. To the far right of Device, click the three dots [ ]. This opens the Select backup Devices window.

Click Add and browse to your backup file. In my example, the file is located in c:\temp. Be aware that SQL will not browse to all folders on your computer. For example, it will not let you browse to your Desktop. So you may need to move the backup file to a folder that SQL will open. 39

40 Select the backup file and click OK. This returns you to the Select backup Devices window. You will see the backup file listed. Click Ok to return to the main Restore Database window. You can see that the database was named pckits on the source server and it will also be named pckits on the destination server. If you want to see the paths where the database files will go, click the Files option under Select a Page. You can see the path of the files from the source server and you can also see the new path for this server. You can change the new path if you want.

41 If this SQL server already has a pckits database and you are replacing it with the backup, be sure to click the Options menu under Select Pages. Then click the Overwrite option to replace the pckits database. Click OK and the database will be restored. If you need to upgrade the version of the pckits database, be sure to read the Upgrading the PC-Kits database from an older version of PC-Kits section of this document. Once the database has been restored, you have to recreate the database login. Read the Setting up the PC-Kits database logins section of this document.

42 If you do not have SQL Management Studio installed, you can restore a database from a command prompt. Run an elevated command prompt (right click cmd.exe and choose Run as Administrator). Type the following command: Sqlcmd E S servername\vhi_pckits -Q"restore database pckits from disk='c:\temp\pckits.bak' with replace" After the restore, follow the instructions for creating the login and upgrading the version if needed.

43 Moving the PC-Kits database from one server to another The basic process to move the pckits database from one machine to another is to do a backup on the old machine and then do a restore on the new machine and then change the name of the database server in the license manager. There are instructions in this document for doing each of those steps. Sounds simple right? But it can quickly become complicated if the version of PC-Kits is changing, if the version of SQL is changing, or if the Windows operating system is changing. If the version of PC-Kits changes, then the pckits database must also be updated. Read Upgrading the PC-Kits database from an older version of PC-Kits in this document for instructions. Version 3 of PC-Kits came with MSDE 2000 (SQL 2000 Express). That version of SQL is not supported on any of the operating systems currently supported by Microsoft. So if you are moving PC-Kits from a machine that is using SQL 2000, you will have to install a newer version of SQL on the new server. Version 4.2 will install SQL 2014 Express on the new server. This creates a problem because a SQL 2000 database is not compatible with SQL 2014. A SQL 2000 database can only be moved to SQL 2005 or SQL 2008. Then if you want, you can take another backup and move it to SQL 2012 or later. So if you don t already have a copy of SQL 2005 or 2008 that you can use temporarily, then I recommend that you install SQL 2008 Express on the new server before moving the PC-Kits database. You can always upgrade to a newer version of SQL later if you want. Moving the pckits database from one server to another usually falls in one of two categories: 1. Your company has a SQL server that is separate from all other PC-Kits components. In this case, the SQL DBA that is in charge of the server will already know how to backup and restore a database and create the logins as discussed in this document. 2. The pckits database is installed on the same computer as the PC-Kits license Server. The remainder of this section deals with this case.

44 When PC-Kits was originally installed, you had to choose either the Server install or the Workstation install. Under the Server choice, there are three options: License Server, Database Server, Application Server. Under the Workstation install there are also three choices, the first one is Peer To Peer (PTP) with a database. The other two choices are workstations without a database and will not be covered in this document. A PTP with database install is essentially equivalent to the Server install with all three servers selected. The License Server has all the serial numbers, the Database Server installs SQL and the database, and the Application Server installs the Workstation (client) components. Anytime you move the PC-Kits license server from on machine to another, you must first contact VHI and ask for your serial numbers to be released. Otherwise you will not be able to activate the PC-Kits software on the new machine. Also, once the license server is moved, you generally need to reinstall all your PC-Kits workstations to point them to the new license server. As mentioned above, there could be many combinations of the version of PC- Kits, the version of SQL, and the version of the Microsoft operating system between the old machine and the new machine. I will not try to cover all the combinations but just touch on a few examples. Read the previous sections on how to backup the database, restore the database, upgrade the database and create the database logins. You can only use the PC-Kits built in Backup and Restore if the PC-Kits client is installed on the SQL server. Case 1: You have PC-Kits version 4.2 or later installed on the original machine. You are moving to another machine and you are installing the same version of PC-Kits on the new computer. This is the easiest case to discuss. Backup the pckits database on the original machine and copy that backup to the new server. Install and activate PC-Kits. Restore the backup to the new server. Case 2: You have PC-Kits version 4.0 or 4.1 installed on the old computer and you are installing PC-Kits version 4.2 or later on the new computer. In this case, SQL 2005 is installed on the original computer and SQL 2014 will be installed on the new computer. This is not a problem because those versions

45 of SQL are compatible. What does have to be dealt with is the version of PC- Kits is changing so the database must be upgraded. There are two ways to do this. Option one is to run the 4.2 upgrade on the original computer first. Then do a backup. Install 4.2 on the new computer and do a restore. Option two is to not upgrade the original server. Make a backup of the pckits database on the original server. Install 4.2 on the new computer and do the restore. At this point, PC-Kits will not open because the database has not been upgraded. Then use the instructions in this document under Upgrading the PC-Kits database from an older version of PC-Kits. Case 3: You have PC-Kits version 3 on the original computer and you are installing version 4.2 or later on the new computer. The issue here is that version 3 of PC-Kits used SQL 2000 and version 4.2 uses SQL 2014. These versions are not compatible. It will not help you to upgrade the original computer to version 4.2 first because that does not upgrade the version of SQL. Option 1 would be to install PC-Kits version 4.1 on the new computer with SQL 2005. Then you would be able to backup and restore the database and then manually upgrade it. However, SQL 2005 is also so old that it is not supported on Windows 7 or later. You can usually get a successful install on Windows 7 but not Windows 8 or 10 or Server 2012. Option 2 is to manually install SQL 2008 Express on the new server (use the same instructions in this document for installing SQL 2014 Express). Then install PC-Kits 4.2 or later on the new machine and tell it to use the SQL 2008 that you just installed. Do a backup on the original computer and then do a restore on the new computer. At this point, PC-Kits will not open because the database has not been upgraded. Then use the instructions in this document under Upgrading the PC-Kits database from an older version of PC-Kits. Option 3 is to temporarily use a copy of SQL 2005 or 2008. Maybe you already have 2005 or 2008 on one of these computers or some other computer or you can install a new copy of it. You would use the instructions in this document to backup the SQL 2000 database, restore it to SQL 2005 or 2008, and then take another backup. Then you can install PC-Kits 4.2 or later with SQL 2014. Use the instructions in this document to restore the database and upgrade it.

46 Changing the database settings in the PC-Kits License Manager All of the PC-Kits database settings can be accessed in the PC-Kits license manager which is on the PC-Kits license server. Since the database settings are passed to the PC-Kits client by the PC-Kits license service, database changes only need to be made on the server. If you are not sure which machine is running the PC-Kits license service, open a PC-Kits client and sign in. Go to the File menu and choose Network Parameters. The first box is the license server. If the PC-Kits license manager is already running, you will see a small VHI icon in the system tray. Double click the icon to open it. If there is no icon in the system tray, go to Start and All Programs\Visual Health Information\ and open the license manager (for newer computers, go to start and choose All Apps).

47 Go to the file menu and choose Configure Client Settings. Click Ok on the warning. This only applies if you have the client installed on this server AND the client is currently open.

48 On the Database tab, you will see all the PC-Kits database settings. Driver: SQLOLEDB.1 This is the driver that PC-Kits uses to connect to SQL. Do not change it. Source: This is the name of your SQL server. If you are using a named instance of SQL (like VHI_PCKITS), then use ServerName\InstanceName. Catalog: pckits This is the name of the SQL database. The default name is pckits. Do not change this unless you have renamed the database to something else.

49 Windows Authentication (SSPI): If you select this option, PC-Kits will connect to SQL with the users Active Directory credentials. Before this will work, you must go into SQL and add all your Active Directory users/groups and give them access to pckits with the User Mapping: pckits_user. Default Authentication: This uses a SQL account to connect to the database. User ID: pckits_login This is the default SQL login name. Password: The default SQL password is pckits_password. You do not need to enter the default password, it is assumed by PC-Kits. If you wish to customize the SQL login name and/or password, go into SQL and setup the login using your customized values. Be sure to assign the User Mapping = pckits_user. Then enter you custom values into the license manager.

50 PC-Kits 3.0 thru 4.1 and SQL 2008 or later (SQL DMO) The installer for PC-Kits versions 3.0 thru 4.1 uses SQL DMO to configure the pckits SQL database. SQL 2008 and later do not come with SQL DMO by default so our older installers cannot connect to the newer SQL versions. Also, the PC- Kits installer would only connect to a default instance of SQL. Because of this, you may find yourself in a situation where you have PC-Kits installed but you cannot run the install again because the installer cannot connect to SQL. This situation usually occurs when you install PC-Kits with an older version. The PC-Kits install succeeds but the SQL install fails. Then you manually install a newer version of SQL. The next time you run the PC-Kits setup, you have an older version of PC-Kits and a newer version of SQL and they cannot talk to each other. There are several ways to try and fix this. If you are using a Default instance of SQL 2008 or later, you can install the SQL 2005 Backwards Compatibility Pack with SQL DMO. Once DMO is installed, the PC-Kits installer can connect to SQL. You could upgrade to PC-Kits 4.2. The new installer uses SQL DMO and should be able to connect to SQL 2008 or later, even if it is a named instance of SQL. If you are trying to uninstall PC-Kits, you can try to uninstall SQL first. If that does not work, search the internet for the Microsoft FixIT tool Fix problems that block programs from being installed or removed. Run the tool and use it to uninstall PC-Kits. You can download the SQL DMO installer from Microsoft, Feature Pack for Microsoft SQL Server 2005. Click the Download button and choose SQLServer2005_BC.msi if you have 32 bit SQL or choose SQLServer2005_BC_x64.msi if you have 64 bit SQL. You only need to install the DMO component.