We help IT Professionals succeed at work.

Can Backup Exec 10d co-exist with SQL Express 2005?

I have a Windows 2003 R2 server running Backup Exec 10d. There is currently no other SQL instances installed or running on that server, although I do have Backup Exec running a backup of some SQL 2000 databases on another server (remote agent).

I would like to install SQL Express 2005 on the Backup Exec server, but I'm worried it may break or interfere with the Backup Exec database. Will there be any conflicts or should I keep anything in mind while installing SQL Express 2k5? I don't want to convert the Backup Exec database or anything like that... just leave it untouched.

Nightly backups are 10x more important than this little project, so I'm just trying to play it safe here.

Watch Question

SQL Express can be installed on different editions of Windows, including XP.

There shouldn't be a conflict with Backup Exec 10d, if you have already installed SP1, and SQL Express on the same computer, but why risk it?

There is also a Hotfix that you can apply, if you want to backup the SQL Express



I need somewhere to house a SQL Express 2005 database for a prototype intranet project. The backup server is currently our best option since it a powerful machine and isn't doing much beyond running backup exec and file sharing.

My main concern was installing SQL Express 2005 making some kind of changes to Backup Exec or interfering with it's communication to it's own database.


You would install SQL Express to its own instance, so that should not be a problem. The backup exec is configured to talk to its database and won't know that another one exists on the server.

You should monitor your resources on that server during the prototype project.

I would make it known to the powers that be that if they decide to develop the project, that the Backup Exec server is too important for development work. What are your options if the developers create a runaway query and you have to shut the server down to stop it?

Another issue that you must consider is that you are allowing access to that important server to other people. Even in an Intranet project, you should lock down the extended procedures (xp), so that no developer can create anything to do with xp_cmdshell, and lock away the SA user. Developers have a lazy habit of creating everything to access the SQL Server as SA, which has far too many permissions for something as mundane as looking at a view.


Good points and definitely something to think about.

I may just start pushing again for a cheap but upgradeable server with Windows 2003 Web Edition for my intranet project. The other current servers are completely out of the question, one being Exchange/DC and one holding the company's accounting databases.

Thank you so much