SQL Job Property Name Property Description
  • Category: Gets or sets the category to which the job belongs.
  • CategoryID: Gets the ID value that uniquely identifies the job category.
  • CategoryType: Gets or sets the type of category, with respect to local or multiserver jobs.
  • CurrentRunRetryAttempt: Gets the number of times Microsoft SQL Server Agent has attempted to run the job unsuccessfully.
  • CurrentRunStatus: Gets the current execution status of the job.
  • CurrentRunStep: Gets information about the job step that is currently running.
  • DateCreated: Gets the date and time when the job was created.
  • DateLastModified: Gets the date and time when the job was last modified.
  • DeleteLevel: Gets or sets the completion action that determines whether to delete the job definition when the job finishes execution.
  • Description: Gets or sets the textual description of the job.
  • EmailLevel: Gets or sets the completion action that determines whether to send an e-mail notification to an operator when the job finishes execution.
  • EventLogLevel: Gets or sets the completion action that determines whether to generate an operating system event log entry when the job finishes execution.
  • ExecutionManager: Gets the object to execute to the manager.(Inherited from SqlSmoObject.)
  • HasSchedule: Gets the Boolean property value that specifies whether the job has at least one schedule.
  • HasServer: Gets the Boolean property value that specifies whether the job has a target server assigned for multiple-server operations.
  • HasStep: Gets the Boolean property value that specifies whether the job has at least one job step.
  • IsEnabled: Gets or sets the Boolean property value that specifies whether the job is enabled.
  • JobID: Gets the job ID value.
  • JobSchedules: Gets a collection of JobSchedule objects that represent the schedules assigned to the job.
  • JobSteps: Gets a collection of JobStep objects that represent the job steps defined for the job.
  • JobType: Gets the job type, which specifies whether the job is local or multiserver.
  • LastRunDate: Gets the date and time when the job was last run.
  • LastRunOutcome: Gets the result of the job from the last time it completed execution.
  • Name: Gets or sets the name of the Job.(Overrides NamedSmoObject.Name.)
  • NetSendLevel: Gets or sets the completion action that determines whether to net-send a notification to an operator when the job finishes execution.
  • NextRunDate: Gets the date and time when the job is next scheduled to run.
  • NextRunScheduleID: Gets the ID value of the schedule that is responsible for the next execution of the job.
  • OperatorToEmail: Gets or sets the operator that receives notification by e-mail when the job finishes execution.
  • OperatorToNetSend: Gets or sets the operator that receives a net-send notification when the job finishes execution.
  • OperatorToPage: Gets or sets the operator that receives a pager notification when the job finishes execution.
  • OriginatingServer: Gets the name of the server that is acting as the master server in a multiserver job.
  • OwnerLoginName: Gets or sets the owner of the job.
  • PageLevel: Gets or sets the completion action that determines whether to send a pager notification to an operator when the job finishes execution.
  • Parent: Gets or sets the JobServer object that is the parent of the Job object.
  • Properties: Gets a collection of Property objects that represent the object properties.(Inherited from SqlSmoObject.)
  • StartStepID: Gets or sets the ID value of the first job step in the sequence to be executed.
  • State: Gets the state of the referenced object.(Inherited from SmoObjectBase.)
  • Urn: Gets the Uniform Resource Name (URN) address value that uniquely identifies the object.(Inherited from SqlSmoObject.)
  • UserData: Gets or sets user-defined data associated with the referenced object.(Inherited from SmoObjectBase.)
  • VersionNumber: Gets a system-maintained value that is incremented every time the job is modified.

Combining LDAP, SMO, DDE and CMS with PowerShell

Restructuring your entire approach to SQL Server DatabaseMaintenance Practices, SQL Server Performance Tuning, SQL Log File Consolidation and Analysis as well as Auditing for Best Practices and Compliance Requirements will pay dividends now and in the future.

Applying Consistent Design Principles

Incorporating the various components of our solutions, including some or all of our 400 PowerShell Scripts and SQL Stored Procedures combined with SQL Management Objects (SMO) with all data extracts going directly into Excel Workbook Tabs in real time updated using Dynamic Data Exchange (DDE) is a winning combination that must be seen to be fully appreciated. Consistent, Predictable and Repeatable Results are what Auditors and Compliance Staff are striving for today.


Benefits of Implementing Our PowerShell Based Consulting Services

Creation of an Integrated and Consistent Solution to SQL Server Management

  • Adherence to Accepted Microsoft Best Practices for SQL Server
  • Consistently Addressing Data Governance, Compliance and Auditing Issues
  • Innovative Approaches to Automation of Database Maintenance Processes
  • Rigorous Consistency Applied to All SQL Server Properties and Settings
  • Usage of PowerShell with SQL Management Objects (SMO) and Excel Reporting
  • Optimization of the Viewing and Analysis of All SQL and Windows Logs
  • Adoption of the Central Management Server Tools, Methods and Techniques
  • Implement Single Click Sign-Ons for DBAs for Query Windows and RDP Access
  • Replacing Risks of SQL Server Exchange eMail with the SMTP Equivalents

Application of Consistent and Innovative Approaches to SQL Automation

Utilization of the Newest Techniques within the Microsoft SQL Server Stack

Making a commitment to evaluating a PowerShell drive approach to SQL Server Maintenance Management will yield many benefits
Investing the time to overcome the PowerShell Learning Curve will not take as much time as you might think. PowerShell techniques build on familiar scripting tools We provide the frameworks and templates to assist developers in converting legacy scripts into more powerful and dynamic PowerShell equivalents.

Implement proven Dynamic Management Views (DMV) techniques for Performance Tuning and Trouble Shooting, install dynamically optimized Index Maintenance Routines, use a new and improved Who-Is-Active-Now routine, use innovative PowerShell CmdLets with Excel Exports using Dynamic Data Exchange (DDE), add scheduled Database Maintenance Integrity Checks and implement Microsoft Best Practice Techniques.