SQL Server Diaries

Once your databases are live and your production SQL Server instance is functioning to it’s best, a user might decide to transfer large amounts of data into a database using SSIS, BCP, or some other custom application.  When such data transfers occur SQL Server logs activity in the transaction log. ... [Read More]

This must have happened to most DBAs: you’re working on the usual stuff, monitoring your SQL Server instances, trying to keep everything oiled and running smoothly when you receive a phone call from a developer who tells you about some new module that has to be implemented soon.  You schedule... [Read More]

A common post-implementation requirement is the checking or verification of database privileges granted to logins.  This is usually triggered by an audit, a security breach, or (preferably) a proactive approach to security.  In SQL Server 2000 permissions were quite simple.  A login had access to a database or not.  The... [Read More]

Client-facing applications which require that a user choose say, a month or weekday name from a list usually rely on hard-coded lists or by the values in a table, config file, or other location.  Unless the original design allows for multiple languages, it can easily get messy when extending the... [Read More]

SQL Server Agent job definitions, schedules and other information are stored in the MSDB system database.  A DBA can retrieve details about the outcome of the scheduled jobs, when the job was executed, how long it took, etc.  This information is stored in the sysjobhistory (Transact-SQL) table.  The schema of... [Read More]