在遷移或升級SQL Server數據庫服務器時,不少場景下咱們不能還原msdb,因此咱們必須手工遷移SQL Server相關做業。若是手工生成每個做業的腳本話,費時又費力,其實SQL Server中有好幾種方法能夠批量生成做業腳本的方法, 下面介紹一下。php
1:SSMS客戶端工具批量生成建立做業腳本html
1:在SSMS—>SQL Server Agent下,單擊Jobs。sql
2: 按快捷鍵F7,在Object Explorer Details裏面,你會看到全部的做業數據庫
3: 全選全部做業(CTRL+A),而後右鍵單擊「Script Job as」,而後選項「CREATE TO"就會生成全部做業的腳本。服務器
這個方法實際上是很是簡潔方便的。不足之處就是全部做業的腳本位於同一個Script,沒有按做業名生成相關對應的腳本。app
2:使用PowerShell腳本生成全部做業的腳本ide
有一個現成的PowerShell腳本,相關介紹以及腳本下載具體參考下面連接:函數
https://gallery.technet.microsoft.com/scriptcenter/How-to-get-the-of-all-the-81859696工具
PS C:\Users> M:\GetJobScripts\GetAllAgentJobs.ps1測試
cmdlet GetAllAgentJobs.ps1 at command pipeline position 1
Supply values for the following parameters:
ServerName: YourServerName
FilePath: M:\GetJobScripts
Scripting out xxxxxxxxxxxx successfully!
Scripting out xxxxxxxxxxxx successfully!
.........................................
使用該PowerShell腳本能夠生成各個做業的各自腳本。很是簡潔方便。不過該腳本要求Windows PowerShell 2.0或更高的版本,另外,有些平臺是沒有測試過的,須要參考上面連接說明。 GetAllAgentJobs.ps1的腳本以下:
<#
The sample scripts are not supported under any Microsoft standard support
program or service. The sample scripts are provided AS IS without warranty
of any kind. Microsoft further disclaims all implied warranties including,
without limitation, any implied warranties of merchantability or of fitness for
a particular purpose. The entire risk arising out of the use or performance of
the sample scripts and documentation remains with you. In no event shall
Microsoft, its authors, or anyone else involved in the creation, production, or
delivery of the scripts be liable for any damages whatsoever (including,
without limitation, damages for loss of business profits, business interruption,
loss of business information, or other pecuniary loss) arising out of the use
of or inability to use the sample scripts or documentation, even if Microsoft
has been advised of the possibility of such damages.
#>
Param(
[Parameter(Mandatory = $true, position = 0)][string] $ServerName,
[Parameter(Mandatory = $true, position = 1)][string] $FilePath
)
if(Test-Path $FilePath)
{
#check if the instance name is available on the server
[System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SqlServer.Smo") |Out-Null
$srv = New-Object ('Microsoft.SqlServer.Management.Smo.Server') $ServerName
if($ServerName.contains($env:COMPUTERNAME) -and ($srv.VersionString))
{
$jobs = $srv.JobServer.Jobs | Where-Object {$_.category -notlike "*repl*" -and $_.category -notlike "*shipping*" -and $_.category -notlike "*Maintenance*" }
ForEach ( $job in $jobs)
{
$jobname = $FilePath +'\' + $job.Name.replace(" ","_").replace("\","_").replace("[","_").replace("]","_").replace(".","_").replace(":","_").replace("*","_") + ".sql"
$job.Script() | Out-File $jobname
Write-Host 'Scripting out ' $job ' successfully!'
}
}
else
{
Write-Host 'The server name you entered is not available!'
}
}
else
{
Write-Host 'The path does not exist, please retype again!'
}
方法3:經過SqlDmo組件相關函數生成數據庫對象腳本,不過有些版本因爲沒有安裝"Backward Compatibility Components" 致使該腳本不能建立相關腳本文件,我的測試時也遇到很多問題,有興趣能夠試試。
http://www.databasejournal.com/features/mssql/article.php/2205291/Generate-Scripts-for-SQL-Server-Objects.htm
參考資料:
https://stackoverflow.com/questions/3361163/automatically-create-scripts-for-all-sql-server-jobs
https://gallery.technet.microsoft.com/scriptcenter/How-to-get-the-of-all-the-81859696