Should libraries be installed on database servers ?

15 August,2011 by Jack Vamvas

A developer asked me if he could install “” on a Production database server. This dll is part of the Microsoft Excel 11.0 Object Library.

This would satisfy his requirement to run a transformation on an Excel file , as part of a SSIS job.

The database server policy is to not install extra libraries unless they are part of a standardised  database server build.  

One of the main reasons for standardising all builds is to improve management. Including rebuilds and Disaster Recovery situations.

A sample of the standard builds for database servers include:

Tivoli Endpoint

Virus Scan         

Resource Kit 

Tivoli Storage Mgr

Tivoli Workload Scheduler

Tivoli Data Protection

SQL Management Studio

OSQL & sqlcmd


Prior client version compatibility with 2005 release of RDBMS (8.0)

SQL Server binaries

What I’d like to know is how you manage requests for ad-hoc libraries ? Do you have a policy? If you do allow , then what sort of documentation standards do you maintain?

Read More

Powershell and Disaster Recovery preparation – T-SQL Tuesday

TechEd Europe 2013 lessons learnt :SQL Server 2014,powershell,performance,automation

Author: Jack Vamvas (


Verify your Comment

Previewing your Comment

This is only a preview. Your comment has not yet been posted.

Your comment could not be posted. Error type:
Your comment has been posted. Post another comment

The letters and numbers you entered did not match the image. Please try again.

As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.

Having trouble reading this image? View an alternate.


Post a comment on Should libraries be installed on database servers ? | SQL Server Performance Tuning | SQL Server DBA:Everything | FAQ | Contact|Copyright & Disclaimer