Home > Articles > Data > SQL Server

📄 Contents

  1. SQL Server Reference Guide
  2. Introduction
  3. SQL Server Reference Guide Overview
  4. Table of Contents
  5. Microsoft SQL Server Defined
  6. SQL Server Editions
  7. SQL Server Access
  8. Informit Articles and Sample Chapters
  9. Online Resources
  10. Microsoft SQL Server Features
  11. SQL Server Books Online
  12. Clustering Services
  13. Data Transformation Services (DTS) Overview
  14. Replication Services
  15. Database Mirroring
  16. Natural Language Processing (NLP)
  17. Analysis Services
  18. Microsot SQL Server Reporting Services
  19. XML Overview
  20. Notification Services for the DBA
  21. Full-Text Search
  22. SQL Server 2005 - Service Broker
  23. Using SQL Server as a Web Service
  24. SQL Server Encryption Options Overview
  25. SQL Server 2008 Overview
  26. SQL Server 2008 R2 Overview
  27. SQL Azure
  28. The Utility Control Point and Data Application Component, Part 1
  29. The Utility Control Point and Data Application Component, Part 2
  30. Microsoft SQL Server Administration
  31. The DBA Survival Guide: The 10 Minute SQL Server Overview
  32. Preparing (or Tuning) a Windows System for SQL Server, Part 1
  33. Preparing (or Tuning) a Windows System for SQL Server, Part 2
  34. Installing SQL Server
  35. Upgrading SQL Server
  36. SQL Server 2000 Management Tools
  37. SQL Server 2005 Management Tools
  38. SQL Server 2008 Management Tools
  39. SQL Azure Tools
  40. Automating Tasks with SQL Server Agent
  41. Run Operating System Commands in SQL Agent using PowerShell
  42. Automating Tasks Without SQL Server Agent
  43. Storage – SQL Server I/O
  44. Service Packs, Hotfixes and Cumulative Upgrades
  45. Tracking SQL Server Information with Error and Event Logs
  46. Change Management
  47. SQL Server Metadata, Part One
  48. SQL Server Meta-Data, Part Two
  49. Monitoring - SQL Server 2005 Dynamic Views and Functions
  50. Monitoring - Performance Monitor
  51. Unattended Performance Monitoring for SQL Server
  52. Monitoring - User-Defined Performance Counters
  53. Monitoring: SQL Server Activity Monitor
  54. SQL Server Instances
  55. DBCC Commands
  56. SQL Server and Mail
  57. Database Maintenance Checklist
  58. The Maintenance Wizard: SQL Server 2000 and Earlier
  59. The Maintenance Wizard: SQL Server 2005 (SP2) and Later
  60. The Web Assistant Wizard
  61. Creating Web Pages from SQL Server
  62. SQL Server Security
  63. Securing the SQL Server Platform, Part 1
  64. Securing the SQL Server Platform, Part 2
  65. SQL Server Security: Users and other Principals
  66. SQL Server Security – Roles
  67. SQL Server Security: Objects (Securables)
  68. Security: Using the Command Line
  69. SQL Server Security - Encrypting Connections
  70. SQL Server Security: Encrypting Data
  71. SQL Server Security Audit
  72. High Availability - SQL Server Clustering
  73. SQL Server Configuration, Part 1
  74. SQL Server Configuration, Part 2
  75. Database Configuration Options
  76. 32- vs 64-bit Computing for SQL Server
  77. SQL Server and Memory
  78. Performance Tuning: Introduction to Indexes
  79. Statistical Indexes
  80. Backup and Recovery
  81. Backup and Recovery Examples, Part One
  82. Backup and Recovery Examples, Part Two: Transferring Databases to Another System (Even Without Backups)
  83. SQL Profiler - Reverse Engineering An Application
  84. SQL Trace
  85. SQL Server Alerts
  86. Files and Filegroups
  87. Partitioning
  88. Full-Text Indexes
  89. Read-Only Data
  90. SQL Server Locks
  91. Monitoring Locking and Deadlocking
  92. Controlling Locks in SQL Server
  93. SQL Server Policy-Based Management, Part One
  94. SQL Server Policy-Based Management, Part Two
  95. SQL Server Policy-Based Management, Part Three
  96. Microsoft SQL Server Programming
  97. An Outline for Development
  98. Database
  99. Database Services
  100. Database Objects: Databases
  101. Database Objects: Tables
  102. Database Objects: Table Relationships
  103. Database Objects: Keys
  104. Database Objects: Constraints
  105. Database Objects: Data Types
  106. Database Objects: Views
  107. Database Objects: Stored Procedures
  108. Database Objects: Indexes
  109. Database Objects: User Defined Functions
  110. Database Objects: Triggers
  111. Database Design: Requirements, Entities, and Attributes
  112. Business Process Model Notation (BPMN) and the Data Professional
  113. Business Questions for Database Design, Part One
  114. Business Questions for Database Design, Part Two
  115. Database Design: Finalizing Requirements and Defining Relationships
  116. Database Design: Creating an Entity Relationship Diagram
  117. Database Design: The Logical ERD
  118. Database Design: Adjusting The Model
  119. Database Design: Normalizing the Model
  120. Creating The Physical Model
  121. Database Design: Changing Attributes to Columns
  122. Database Design: Creating The Physical Database
  123. Database Design Example: Curriculum Vitae
  124. NULLs
  125. The SQL Server Sample Databases
  126. The SQL Server Sample Databases: pubs
  127. The SQL Server Sample Databases: NorthWind
  128. The SQL Server Sample Databases: AdventureWorks
  129. The SQL Server Sample Databases: Adventureworks Derivatives
  130. UniversalDB: The Demo and Testing Database, Part 1
  131. UniversalDB: The Demo and Testing Database, Part 2
  132. UniversalDB: The Demo and Testing Database, Part 3
  133. UniversalDB: The Demo and Testing Database, Part 4
  134. Getting Started with Transact-SQL
  135. Transact-SQL: Data Definition Language (DDL) Basics
  136. Transact-SQL: Limiting Results
  137. Transact-SQL: More Operators
  138. Transact-SQL: Ordering and Aggregating Data
  139. Transact-SQL: Subqueries
  140. Transact-SQL: Joins
  141. Transact-SQL: Complex Joins - Building a View with Multiple JOINs
  142. Transact-SQL: Inserts, Updates, and Deletes
  143. An Introduction to the CLR in SQL Server 2005
  144. Design Elements Part 1: Programming Flow Overview, Code Format and Commenting your Code
  145. Design Elements Part 2: Controlling SQL's Scope
  146. Design Elements Part 3: Error Handling
  147. Design Elements Part 4: Variables
  148. Design Elements Part 5: Where Does The Code Live?
  149. Design Elements Part 6: Math Operators and Functions
  150. Design Elements Part 7: Statistical Functions
  151. Design Elements Part 8: Summarization Statistical Algorithms
  152. Design Elements Part 9:Representing Data with Statistical Algorithms
  153. Design Elements Part 10: Interpreting the Data—Regression
  154. Design Elements Part 11: String Manipulation
  155. Design Elements Part 12: Loops
  156. Design Elements Part 13: Recursion
  157. Design Elements Part 14: Arrays
  158. Design Elements Part 15: Event-Driven Programming Vs. Scheduled Processes
  159. Design Elements Part 16: Event-Driven Programming
  160. Design Elements Part 17: Program Flow
  161. Forming Queries Part 1: Design
  162. Forming Queries Part 2: Query Basics
  163. Forming Queries Part 3: Query Optimization
  164. Forming Queries Part 4: SET Options
  165. Forming Queries Part 5: Table Optimization Hints
  166. Using SQL Server Templates
  167. Transact-SQL Unit Testing
  168. Index Tuning Wizard
  169. Unicode and SQL Server
  170. SQL Server Development Tools
  171. The SQL Server Transact-SQL Debugger
  172. The Transact-SQL Debugger, Part 2
  173. Basic Troubleshooting for Transact-SQL Code
  174. An Introduction to Spatial Data in SQL Server 2008
  175. Performance Tuning
  176. Performance Tuning SQL Server: Tools and Processes
  177. Performance Tuning SQL Server: Tools Overview
  178. Creating a Performance Tuning Audit - Defining Components
  179. Creating a Performance Tuning Audit - Evaluation Part One
  180. Creating a Performance Tuning Audit - Evaluation Part Two
  181. Creating a Performance Tuning Audit - Interpretation
  182. Creating a Performance Tuning Audit - Developing an Action Plan
  183. Understanding SQL Server Query Plans
  184. Performance Tuning: Implementing Indexes
  185. Performance Monitoring Tools: Windows 2008 (and Higher) Server Utilities, Part 1
  186. Performance Monitoring Tools: Windows 2008 (and Higher) Server Utilities, Part 2
  187. Performance Monitoring Tools: Windows System Monitor
  188. Performance Monitoring Tools: Logging with System Monitor
  189. Performance Monitoring Tools: User Defined Counters
  190. General Transact-SQL (T-SQL) Performance Tuning, Part 1
  191. General Transact-SQL (T-SQL) Performance Tuning, Part 2
  192. General Transact-SQL (T-SQL) Performance Tuning, Part 3
  193. Performance Monitoring Tools: An Introduction to SQL Profiler
  194. Performance Tuning: Introduction to Indexes
  195. Performance Monitoring Tools: SQL Server 2000 Index Tuning Wizard
  196. Performance Monitoring Tools: SQL Server 2005 Database Tuning Advisor
  197. Performance Monitoring Tools: SQL Server Management Studio Reports
  198. Performance Monitoring Tools: SQL Server 2008 Activity Monitor
  199. The SQL Server 2008 Management Data Warehouse and Data Collector
  200. Performance Monitoring Tools: Evaluating Wait States with PowerShell and Excel
  201. Practical Applications
  202. Choosing the Back End
  203. The DBA's Toolbox, Part 1
  204. The DBA's Toolbox, Part 2
  205. Scripting Solutions for SQL Server
  206. Building a SQL Server Lab
  207. Using Graphics Files with SQL Server
  208. Enterprise Resource Planning
  209. Customer Relationship Management (CRM)
  210. Building a Reporting Data Server
  211. Building a Database Documenter, Part 1
  212. Building a Database Documenter, Part 2
  213. Data Management Objects
  214. Data Management Objects: The Server Object
  215. Data Management Objects: Server Object Methods
  216. Data Management Objects: Collections and the Database Object
  217. Data Management Objects: Database Information
  218. Data Management Objects: Database Control
  219. Data Management Objects: Database Maintenance
  220. Data Management Objects: Logging the Process
  221. Data Management Objects: Running SQL Statements
  222. Data Management Objects: Multiple Row Returns
  223. Data Management Objects: Other Database Objects
  224. Data Management Objects: Security
  225. Data Management Objects: Scripting
  226. Powershell and SQL Server - Overview
  227. PowerShell and SQL Server - Objects and Providers
  228. Powershell and SQL Server - A Script Framework
  229. Powershell and SQL Server - Logging the Process
  230. Powershell and SQL Server - Reading a Control File
  231. Powershell and SQL Server - SQL Server Access
  232. Powershell and SQL Server - Web Pages from a SQL Query
  233. Powershell and SQL Server - Scrubbing the Event Logs
  234. SQL Server 2008 PowerShell Provider
  235. SQL Server I/O: Importing and Exporting Data
  236. SQL Server I/O: XML in Database Terms
  237. SQL Server I/O: Creating XML Output
  238. SQL Server I/O: Reading XML Documents
  239. SQL Server I/O: Using XML Control Mechanisms
  240. SQL Server I/O: Creating Hierarchies
  241. SQL Server I/O: Using HTTP with SQL Server XML
  242. SQL Server I/O: Using HTTP with SQL Server XML Templates
  243. SQL Server I/O: Remote Queries
  244. SQL Server I/O: Working with Text Files
  245. Using Microsoft SQL Server on Handheld Devices
  246. Front-Ends 101: Microsoft Access
  247. Comparing Two SQL Server Databases
  248. English Query - Part 1
  249. English Query - Part 2
  250. English Query - Part 3
  251. English Query - Part 4
  252. English Query - Part 5
  253. RSS Feeds from SQL Server
  254. Using SQL Server Agent to Monitor Backups
  255. Reporting Services - Creating a Maintenance Report
  256. SQL Server Chargeback Strategies, Part 1
  257. SQL Server Chargeback Strategies, Part 2
  258. SQL Server Replication Example
  259. Creating a Master Agent and Alert Server
  260. The SQL Server Central Management System: Definition
  261. The SQL Server Central Management System: Base Tables
  262. The SQL Server Central Management System: Execution of Server Information (Part 1)
  263. The SQL Server Central Management System: Execution of Server Information (Part 2)
  264. The SQL Server Central Management System: Collecting Performance Metrics
  265. The SQL Server Central Management System: Centralizing Agent Jobs, Events and Scripts
  266. The SQL Server Central Management System: Reporting the Data and Project Summary
  267. Time Tracking for SQL Server Operations
  268. Migrating Departmental Data Stores to SQL Server
  269. Migrating Departmental Data Stores to SQL Server: Model the System
  270. Migrating Departmental Data Stores to SQL Server: Model the System, Continued
  271. Migrating Departmental Data Stores to SQL Server: Decide on the Destination
  272. Migrating Departmental Data Stores to SQL Server: Design the ETL
  273. Migrating Departmental Data Stores to SQL Server: Design the ETL, Continued
  274. Migrating Departmental Data Stores to SQL Server: Attach the Front End, Test, and Monitor
  275. Tracking SQL Server Timed Events, Part 1
  276. Tracking SQL Server Timed Events, Part 2
  277. Patterns and Practices for the Data Professional
  278. Managing Vendor Databases
  279. Consolidation Options
  280. Connecting to a SQL Azure Database from Microsoft Access
  281. SharePoint 2007 and SQL Server, Part One
  282. SharePoint 2007 and SQL Server, Part Two
  283. SharePoint 2007 and SQL Server, Part Three
  284. Querying Multiple Data Sources from a Single Location (Distributed Queries)
  285. Importing and Exporting Data for SQL Azure
  286. Working on Distributed Teams
  287. Professional Development
  288. Becoming a DBA
  289. Certification
  290. DBA Levels
  291. Becoming a Data Professional
  292. SQL Server Professional Development Plan, Part 1
  293. SQL Server Professional Development Plan, Part 2
  294. SQL Server Professional Development Plan, Part 3
  295. Evaluating Technical Options
  296. System Sizing
  297. Creating a Disaster Recovery Plan
  298. Anatomy of a Disaster (Response Plan)
  299. Database Troubleshooting
  300. Conducting an Effective Code Review
  301. Developing an Exit Strategy
  302. Data Retention Strategy
  303. Keeping Your DBA/Developer Job in Troubled Times
  304. The SQL Server Runbook
  305. Creating and Maintaining a SQL Server Configuration History, Part 1
  306. Creating and Maintaining a SQL Server Configuration History, Part 2
  307. Creating an Application Profile, Part 1
  308. Creating an Application Profile, Part 2
  309. How to Attend a Technical Conference
  310. Tips for Maximizing Your IT Budget This Year
  311. The Importance of Blue-Sky Planning
  312. Application Architecture Assessments
  313. Transact-SQL Code Reviews, Part One
  314. Transact-SQL Code Reviews, Part Two
  315. Cloud Computing (Distributed Computing) Paradigms
  316. NoSQL for the SQL Server Professional, Part One
  317. NoSQL for the SQL Server Professional, Part Two
  318. Object-Role Modeling (ORM) for the Database Professional
  319. Business Intelligence
  320. BI Explained
  321. Developing a Data Dictionary
  322. BI Security
  323. Gathering BI Requirements
  324. Source System Extracts and Transforms
  325. ETL Mechanisms
  326. Business Intelligence Landscapes
  327. Business Intelligence Layouts and the Build or Buy Decision
  328. A Single Version of the Truth
  329. The Operational Data Store (ODS)
  330. Data Marts – Combining and Transforming Data
  331. Designing Data Elements
  332. The Enterprise Data Warehouse — Aggregations and the Star Schema
  333. On-Line Analytical Processing (OLAP)
  334. Data Mining
  335. Key Performance Indicators
  336. BI Presentation - Client Tools
  337. BI Presentation - Portals
  338. Implementing ETL - Introduction to SQL Server 2005 Integration Services
  339. Building a Business Intelligence Solution, Part 1
  340. Building a Business Intelligence Solution, Part 2
  341. Building a Business Intelligence Solution, Part 3
  342. Tips and Troubleshooting
  343. SQL Server and Microsoft Excel Integration
  344. Tips for the SQL Server Tools: SQL Server 2000
  345. Tips for the SQL Server Tools – SQL Server 2005
  346. Transaction Log Troubles
  347. SQL Server Connection Problems
  348. Orphaned Database Users
  349. Additional Resources
  350. Tools and Downloads
  351. Utilities (Free)
  352. Tool Review (Free): DBDesignerFork
  353. Aqua Data Studio
  354. Microsoft SQL Server Best Practices Analyzer
  355. Utilities (Cost)
  356. Quest Software's TOAD for SQL Server
  357. Quest Software's Spotlight on SQL Server
  358. SQL Server on Microsoft's Virtual PC
  359. Red Gate SQL Bundle
  360. Microsoft's Visio for Database Folks
  361. Quest Capacity Manager
  362. SQL Server Help
  363. Visual Studio Team Edition for Database Professionals
  364. Microsoft Assessment and Planning Solution Accelerator
  365. Aggregating Server Data from the MAPS Tool

In a previous tutorial, I explained how important automation is to the database professional. Automation speeds tasks, can be scaled across multiple systems, and reduces errors. It’s such an important concept that Microsoft includes a tool within SQL Server that provides an automation process, called the SQL Server Agent. It combines steps of work and schedules into something called a “job”, and job information is logged into tables in the msdb system database. In fact, the jobs, steps, schedules and logs are all stored in the msdb database, making the system completely database-driven. That combines with a Windows Service to run either on-demand or through a scheduling mechanism.

In some cases, however, you don’t have access to the SQL Server Agent. The “lower” editions of SQL Server (MSDE, Express and CE) don’t have the Agent enabled. In the most recent versions you will in fact see the components there, but you won’t be able to start the service or use the Agent. In other cases you may not want to use the SQL Server Agent, because you have another automation system that you want to use for more than just SQL Server, you don’t have enough privileges to run on the system, or to have more granular control of the system.

If that’s the case for you, there are options. I’ll explain various tools you have at your disposal, but first I think it’s important to understand what sections of the automation services that the SQL Server Agent provides are useful to duplicate. You don’t have to use all of these, but understanding why they are valuable is important to your final architecture.

I’ll also mention here that I won’t cover third-party automation features. I have a section here at InformIT dedicated to talking about software that doesn’t come “in the box” – meaning in the Windows Operating System or with SQL Server itself. Also, vendor products change quite frequently, so it makes sense to read up on what they offer directly from their documentation. You should, however, read this tutorial to ensure you know what you’re looking to automate, and the components of that automation that you care about.

Replacing the Components of SQL Server Agent

The first place to start is to break out the functions within SQL Server Agent (or any automation feature, actually) and list what benefits they provide. This serves as your “specification” when you write your replacement code. I say “write the code”, even though the choice you make might be graphical in nature.

After you detail the components you want to implement, you can choose the mechanism to code. Keep in mind that you might end up with a “mix and match” scenario – not all mechanisms are suited for both code logic and scheduling or logging, for instance.

The components that I took away from SQL Server Agent are as follows:

  • Steps
  • Schedules
  • Security
  • Logging

Let’s examine each one of these components.

Steps

Within SQL Server Agent Jobs are the atomic bits of the system called “steps”. These units, which can be anything from Transact-SQL (T-SQL) statements to PowerShell scripts (in version 2008 and higher) are the basic units of work for your system. While this is the most important section of your system, it’s the most problematic, because most often you’re looking to work with more than just SQL Server in an automation process.

For instance – you may want to back up a database, run a ZIP operation on the file to compress it, copy that file to a new location, and delete files older than today’s backup (or some other interval). While the first part of that process is something that you can do easily in Transact-SQL, the rest is better done at the Operating System level. So when you are making your choices, you need to keep in mind the breadth of operations you need to perform. This is also the place where you think about using more than one mechanism to create your system.

In SQL Server Agent, the Steps have basic branching functionality. For instance, you can have a Step serve as an exit for the Job, continue on success or do something else on failure. You’ll need to consider this as well for your replacement, although I normally consider error handling and flow control as two separate functions. In any case, make sure your system handles this function.

Schedules and Security

As I created my early SQL Server Agent replacement systems years ago, I considered these two functions separately. Schedules dealt with time, and Security had to do with which “principal” account ran the equivalent of a job. As time went on, I learned that the scheduling process often determined the security account, and so I started to think about them together. Even so, security has layers, and your system should as well. Even if you have security set on the scheduling system, if the mechanism for each step can send credentials, you can have each step use the proper level of security as well.

But I’ll consider the scheduling mechanism first. It’s difficult to separate the function from the actual tool you’ll use to schedule things, so I’ll leave until later the discussion of the scheduling feature in the Windows Operating system. The keys are that you think about the ability to schedule based on a re-usable basis (Weekly, Daily at Midnight, that sort of thing) and a specific, ad-hoc, one-time schedule (like Thursday the 10th at 11:00).

Within your scheduling decision think about the granularity of the time unit. For instance, do you want to schedule the whole “job”, or logical package, or each step? If you schedule the job, the steps can be chained together such that one starts after another. If you decide to schedule each step, you’ll need to “set state”, meaning a marker of some sort in memory or on disk, or as a software broadcast (called an “event”) that tells the next step where it is in the process. Let’s look at a concrete example.

Assume that your “job” has two simple “steps”. The first backs up the database, and the second performs an Index Reorganization. You don’t want those two events to happen at the same time. Both of these processes are T-SQL based, so they will work in a “batch” mode and not simultaneously – as long as they know about each other. So, of your mechanism allows for batch-like processing, then when the backup completes, the re-organization will start. That means you can schedule the whole “job” as a unit.

However, if your mechanism will launch both processes simultaneously (sometimes called parallel operations) then you could end up with a backup running while a re-organization happens. In that case, you might want to either create a schedule for both tasks, with enough time for one to complete before the other, or have the first task create a marker in memory or on disk or through an event notification that the second task checks to see when it can start.

Logging

I like a LOT of logging capability. My normal process is to turn on a lot of logging, and trim it if the process completes successfully. If there’s an issue, then I have the logging and I know what stopped and where.

Think about the granularity you want for your process. Some developers like to code for multiple levels of logging, meaning a “standard” or basic level where only failures are logged, an “enhanced” level where starts and stops of steps are recorded, and a “full” or “debug” set of logging takes place, detailing every operation. They code the process such that you can select the level of logging when you call the code. Personally I don’t find this as useful in automation since I can’t predict when something might fail, and that’s when I want a higher level of logging. I also don’t always want a complete level of logging, even when I am troubleshooting, since that much information isn’t helpful for me.

The simplest option for logging in most instances is to create a text file of the results of the operation. I use this option pretty regularly, but I try and opt for the Windows Event Logs (Application) if I can. It is a standard, always-available, easily read and secured option, and folds in with the other tools I use in the operating system. That way I have a single location to review for all operations on my server.

Options for tools

No matter what option you select, you’ll need the Windows Operating system. It provides the basis for all tools, of course, at least for SQL Server. But this isn’t a limitation. Windows provides a full scheduling engine, a logging facility, and a command-shell to run batch files.

For the scheduler part of my SQL Agent replacements, I use the Windows Task Scheduler.

It has a lot of richness, including security, monitoring, conditions, triggers and more. In fact, I find it more useful than the SQL Server Agent scheduler. When you locate this tool on your server, run it and press F1 for more help and a tutorial on how to create basic or advanced tasks. Again, depending on how you architect your solution, these tasks can either be conceptually treated as Jobs or you can split them up into steps. You’ll find that with the triggers and conditions you can do some basic branching and routing, emulating a job in a limited way.

As a second option, you can use the AT command at the command line. To find out its parameters, simply type AT /? and press RETURN or ENTER at the command line. You get a lot of options, but I find that working in the Windows Task Scheduler to be superior for setting up this kind of schedule.

SQLCMD, osql and isql

The first place you can start for the step logic is with the SQLCMD feature found in SQL Server versions 2005 and higher. SQL Server 2000 and lower include the isql command-line feature, which work in a similar way, but unless you don’t have access to SQLCMD, I don’t recommend you use those. The osql feature is similar, and should also be upgraded to use SQLCMD.

SQLCMD accepts T-SQL commands and passes them through to the Engine just like SQL Server Management Studio (SSMS). There are “switches” that control how that information is passed, security and more. To see a list of these switches, at a command-prompt type:

SQLCMD /?

You should get something like this back:

Microsoft (R) SQL Server Command Line Tool
Version 10.50.1600.1 NT INTEL X86
Copyright (c) Microsoft Corporation.  All rights reserved.

usage: Sqlcmd            [-U login id]          [-P password]
  [-S server]            [-H hostname]          [-E trusted connection]
  [-N Encrypt Connection][-C Trust Server Certificate]
  [-d use database name] [-l login timeout]     [-t query timeout]
  [-h headers]           [-s colseparator]      [-w screen width]
  [-a packetsize]        [-e echo input]        [-I Enable Quoted Identifiers]
  [-c cmdend]            [-L[c] list servers[clean output]]
  [-q "cmdline query"]   [-Q "cmdline query" and exit]
  [-m errorlevel]        [-V severitylevel]     [-W remove trailing spaces]
  [-u unicode output]    [-r[0|1] msgs to stderr]
  [-i inputfile]         [-o outputfile]        [-z new password]
  [-f <codepage> | i:<codepage>[,o:<codepage>]] [-Z new password and exit]
  [-k[1|2] remove[replace] control characters]
  [-y variable length type display width]
  [-Y fixed length type display width]
  [-p[1] print statistics[colon format]]
  [-R use client regional setting]
  [-b On error batch abort]
  [-v var = "value"...]  [-A dedicated admin connection]
  [-X[1] disable commands, startup script, enviroment variables [and exit]]
  [-x disable variable substitution]
  [-? show syntax summary]

That’s a lot of information, and you don’t actually need it all. Let’s assume for a moment that you’re working from a default instance of SQL Server where the databases are local, and your Windows account has access to that server. You can simply type two parameters to send a query to the server you’re on to retrieve the version of SQL Server you are running (or run a backup, or any other command you’re allowed to type):

SQLCMD -E -Q “SELECT @@VERSION;”

The –E sets “trusted” authentication, and the –Q (case matters) runs a query and gets out. Everything that is in between the quotes is the query.

But life is rarely that simple. Let’s assume now that you’re on a workstation, and you have an instance called INSTANCE1 on a server named SERVER1. You have a domain user called MyDomain\Bob with a password of Pass@word1. Here’s the same query, this time using a few more paremeters:

SQLCMD -U Mydomain\Bob -P Pass@word1 -S Serveri\Instance1 -Q “SELECT @@VERSION;”

I’ve added the -U (user name) -P (password) and -S (server and instance name) to complete the query.

Most of your steps, however, will be the kind that can be re-used. So you may want to store the actual T-SQL as a script, and have the SQLCMD program read that script for the work. And since it’s an automated step, you need to have somewhere to put the results, since you’re not looking at the screen when it runs. Two final switches are all you need.

Let’s assume now that you have a script called “CheckVersion.SQL” in your “Scripts” directory, and it has this line in it:

SELECT @@VERSION;

To run that query and put the results in a “VersionResults.txt” file in your “Results” directory, here’s all you need:

SQLCMD -U Mydomain\Bob -P Pass@word1 -S Serveri\Instance1 -i c:\Scripts\CheckVersion.SQL
 -o c:\results\VersionResults.txt

Assuming you actually have all of those directories, servers and instances with that name, and security correct, this will return the correct result. You can create .CMD files (Windows batch files) with this kind of information in it, schedule that through the Windows Task Scheduler, and you have the makings of a rudimentary SQL Server Agent replacement.

PowerShell

The problem with using only SQLCMD and the Windows Task Scheduler is that you don’t have great error control, branching and routing. Plus, while you are able to log what SQL Server is up to (with the -o switch) you don’t have insight into what the batch file itself is doing.

Enter PowerShell. PowerShell provides the richness of a programming language (I know, it isn’t a programming language) with the benefits of a batch file (I know, it isn’t a batch file) and the power of a command-shell (I know, it isn’t a shell). While it technically isn’t any of those, it comes very close, and certainly close enough to do all of your maintenance, performance logging and other tasks.

Not only that, PowerShell speaks “natively” to anything .NET - meaning it can read and write Windows registries and logs, work with SQL Server, across domains, through networks y mucho mas. You have better error handling, logging and branching, remoting and other programmatic features.

I’ve written a great deal about PowerShell and SQL Server, and using it and the Windows Task Scheduler you can actually accomplish more than with SQL Server Agent alone. Check the article series out here. Also check the links below for the SQLPSX extensions that make working with SQL Server and PowerShell very easy.

Coding with DMO and SMO

Although working with PowerShell and SQL Server technically involves the Server Management Objects (SMO) library, a lot of its complexities are hidden from you. I’m not a developer, but I have played one once or twice in my career. If you really want a robust, graphical, complete customizable solution, you may want to investigate learning more about SMO. I’ll post references to that at the bottom of this article.

The older version of SMO is the Database Management Objects library, or DMO. I have a series of articles here on InformIT on that library that you can also reference for that.

These are only three of the primary features you have available as a replacement for SQL Server Agent as an automation engine for SQL Server. There are others, such as Perl, RoboScript and many third-party scripting, coding and access programs that can “talk” to SQL Server and provide logging, error handling and more. The key is to clearly define the requirements you need for your system, line up your options, and test, test, test.

InformIT Articles and Sample Chapters

I have an entire series on PowerShell that will explain everything you need to know to get started with this powerful subsystem.

Books and eBooks

My friend Bob Beauchemin and his co-author Dan Sullivan cover the SMO library in greater depth in their book A Developer's Guide to SQL Server 2005. Check it out here.

Online Resources

The SQLCMD utility, along with a full tutorial, is explained here.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020