Search
Subscribe
Categories
- Backup and Restore
- Capacity Planning
- Compression
- Configure
- Contact me
- CPU
- Data Architecture
- Data Import and Export
- Database Mirroring
- DBA
- DBA Scripts
- DBCC
- Deadlocks
- Default Trace
- Development
- Disaster Recovery
- Disk Storage
- DMV
- Documentation
- Event Log
- Execution Plan
- Function
- High Availability
- Indexes
- Install & Setup
- Interviews
- IO Subsystem
- Isolation levels
- Jobs
- Latches
- Links
- Locking
- Memory
- Monitor Performance
- MS DTC
- MSDB
- Network
- Object Management
- Pagination
- Partitioning
- Performance
- Powershell
- Security Management
- SQL Agent
- SQL Azure
- SQL Blocking
- SQL Cachestore
- SQL DAC
- SQL Default Trace
- SQL DTS
- SQL Error Logs
- SQL Execution Plan
- SQL Optimizer
- SQL problems
- SQL Query Tuning
- SQL Server Error Tips
- SQL Server Management Studio
- SQL Server Profiler
- SQL Server Tuning
- SQL Trigger
- SQL View
- SQLServer-DBA News
- SSIS
- Statistics
- Stored Procedure
- T-SQL
- TempDB
- Tools
- TPC-H
- Transaction Logs
- View
- Virtualization
- Wait Stats
SQLServer-DBA.com Links
Recent Posts
- Forgotten sa password
- Sql server installation is either corrupt or has been tampered with error getting instance id from name
- Find Weak passwords in SQL Server
- Event ID 55 : The file system structure on the disk is corrupt and unusable on volume
- Career in DBA
- Error 3254 – The volume on device BACKUP_PATH is empty
- SQL auto close - Keep it turned off
- Windows Pagefile size for dedicated SQL Servers
- SQL Database Corruption
- max server memory and sql server memory – why is total memory greater than max memory?
15 August,2011 by Jack Vamvas
A developer asked me if he could install “microsoft.office.interop.excel.dll” 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 Recover 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
BCP
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?
Author: Jack Vamvas (http://www.sqlserver-dba.com)
Verify your Comment
Previewing your Comment
This is only a preview. Your comment has not yet been posted.
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.
Posted by: |