Archive for the ‘ Database ’ Category

SQL Server 2008 R2 – Unattended Silent Install


There is existing documentation on MSDN about How to: Install SQL Server 2008 R2 from the Command Prompt, but this post focuses on creating a silent unattended install of SQL Server 2008 R2 (Standard or Enterprise) using a configuration file. With the instructions below, you’ll be able to create a new customized SQL silent installation in minimal time. Note that the configuration below doesn’t work with the Express edition of SQL Server 2008 R2.

  • Run setup.exe
  • Click on the installtion tab
  • Click “New Installation”
  • Go through the wizard: Enter product key, accept license, install setup support files, and select the features you want to install:
  • Continue the installation until you reach the “Ready To Install” step. Notice the path to the configuration file highlighted below in blue.

  • Now that you have the configuration file, copy it to your own folder or network share where you want to start the unattended installation.
  • Cancel setup since we’re interested in the unattended silent mode of installation; not the UI one.
  • Edit the configuration file as follows:
    • Set QUIET to “True”. This specifies that Setup will run in a quiet mode without any user interface (i.e. unattended installation)
      QUIET="True"
    • Set SQLSYSADMINACCOUNTS to “BUILTIN\ADMINISTRATORS”. This will ensure that administrators on the machine are added as members of the sysadmin role. You can set its value based on your needs (Ex: SQLSYSADMINACCOUNTS=”domain\YourUser”), but this is the more generic approach.
      SQLSYSADMINACCOUNTS="BUILTIN\ADMINISTRATORS"
    • Add PID and set its value to your product license key. If your setup.exe already comes preloaded with the key, there is no need to add this option to the configuration file.
    • Add IACCEPTSQLSERVERLICENSETERMS and set its value to “True”. This is to required to acknowledge acceptance of the license terms when the /Q (i.e. QUIET) parameter is specified for unattended installations.
      IACCEPTSQLSERVERLICENSETERMS="True"
    • Remove the ADDCURRENTUSERASSQLADMIN parameter. The reason is that this parameter can’t be used when SQLSYSADMINACCOUNTS is specified, and it only applies to Express installations.
    • Remove the UIMODE parameter as it can’t be used with the QUITE parameter.
    • Remove INSTALLSHAREDDIR, INSTALLSHAREDWOWDIR, INSTANCEDIR parameters since we want to install on the default installation directories.
    • That’s it. If you want to change the features that this setup will install, there is no need to go with the full steps again. You can simply change the value for the FEATURES parameter. For example, the features I selected (shown in first screenshot above) will generate FEATURES=SQLENGINE,SSMS,ADV_SSMS in the configuration file.  You can change that based on your needs. The full list of available feature parameters and their descriptions is located here.

After getting the configuration file ready, you’ll need to create a batch file that will run the silent unattended setup. Simply, create a new file  “InstallSQL2008R2.bat” with extension = “.bat” with the following content, and make sure you replace <path to SQL setup folder> and <path to config file> with the proper values.

@ECHO off
echo Installing SQL Server 2008 R2
date/t
time /t
"<path to SQL setup folder>\setup.exe" /ConfigurationFile="<path to config file>"
date/t
time /t

All we’re doing in the script above is running SQL setup.exe and passing the configuration file as an argument to it. You can download both the batch and config files here.

Content DB Attach using PowerShell


In this post, I’ll talk about how to attach\mount a SharePoint content database to a SharePoint web application after it has been restored\attached to the SQL server. See my previous post for details on how to restore a database using PowerShell.

SharePoint provides a cmdlet to do the content db attach. This cmdlet is called Mount-SPContentDatabase. I will create a script block wrapper for this cmdlet and show how to call it remotely. The script block below adds the SharePoint PowerShell snapin if it’s not already added, selects a web application in the farm, then calls the Mount-SPContentDatabase to do the content db attach.

[ScriptBlock] $global:AttachSPContentDB =
{
    param([string] $dbName, [string] $dbServer)

    try
    {
        # Load the Sharepoint Cmdlets
        Write-Host "Loading SharePoint PowerShell Snapin"
        $spSnapin = Get-PSSnapin | where {$_.Name -eq "Microsoft.SharePoint.PowerShell"}
        if($spSnapin -eq $null)
        {
            Add-PSSnapin Microsoft.SharePoint.PowerShell
            Write-Host -ForegroundColor "Green" -Object "SharePoint PowerShell Snapin loaded"
        }
        else
        {
            Write-Host -ForegroundColor "Gray" -Object "SharePoint PowerShell Snapin already loaded"
        }

        # Get  web applciation url
        Write-Host "Selecting a web application in the farm"
        $webAppUrl = (Get-SPWebApplication | select -Index 0).Url

        # Mount the database at the specified SQL server to the web application
        Write-Host "Mounting database '$dbName' at SQL server '$dbServer' to web application '$webAppUrl'"
        $newDB = Mount-SPContentDatabase $dbName -DatabaseServer $dbServer -WebApplication $webAppUrl -AssignNewDatabaseId
        Write-Host -ForegroundColor "Green" -Object "Database mounted successfully with ID: " + ($newDB.Id)

        # Return content DB Id
        return $newDB.Id.ToString()
    }
    catch [Exception]
    {
        Write-Host -ForegroundColor "Red" -Object $_.Exception

        return $null
    }
}

To call this script block, pass the name of the Sql server and the name of the content database. Make sure that the content database is already restored\attached to the SQL server.

.$AttachSPContentDB "ContentDBName" "SqlServerName"

To call the script block on a remote SharePoint WFE, you can simply run

Invoke-Command -ComputerName "WFEName" -ScriptBlock { .$AttachSPContentDB "ContentDBName" "SqlServerName" }

Note that the New-SPContentDatabase cmdlet has the same effect as Mount-SPContentDatabase. The only difference is that New-SPContentDatabase creates a new SQL database if there is no database with the same name already available on the SQL server.

SQL DB Restore using PowerShell


If you are looking for a PowerShell script that lets you restore a database from a backup (.bak) file to MSSQL server, then this is the right place for you.

Database Restore - SQL

Let’s say you have a .bak file (Ex: AdventureWorks), and you would like to restore it to an SQL server using PowerShell. If you use SQL Server 2008 Management Studio and click on the “Script” button, you will get th SQL statement that will do that restore for you.

Here is the SQL RESTORE statement that will allow you to restore the AdventureWorksLT2008R2.bak to the new database ‘NewDatabaseName’.

RESTORE DATABASE [NewDatabaseName]
FROM DISK = N'C:\.etc..\AdventureWorksLT2008R2.bak'
WITH FILE = 1,
MOVE N'AdventureWorksLT2008R2_Data'
TO N'C:\.etc..\MSSQL\DATA\NewDatabaseName.mdf',
MOVE N'AdventureWorksLT2008R2_Log'
TO N'C:\.etc..\MSSQL\DATA\NewDatabaseName_1.ldf',
NOUNLOAD, STATS = 10

If you use SQL Server 2008 R2 Management Studio, the generated SQL statement would look like this.

RESTORE DATABASE [NewDatabaseName]
FROM  DISK = N'C:\.etc..\AdventureWorksLT2008R2.bak'
WITH  FILE = 1,  NOUNLOAD,  STATS = 10

Running this statement is almost the same as the previous statement, except that the MDF and LDF files would be named AdventureWorksLT2008R2_Data.mdf and AdventureWorksLT2008R2_Log.ldf respectively (instead of having NewDatabaseName in the file names).

If we want to create a simple PowerShell function to run the SQL Restore command, we can do so using the OSQL Utility:

function global:RestoreDB ([string] $newDBName, [string] $backupFilePath)
{
    [string] $dbCommand = "RESTORE DATABASE [$newDBName] " +
    "FROM    DISK = N'$backupFilePath' " +
    "WITH    FILE = 1, NOUNLOAD, STATS = 10"

    OSQL.EXE -E -Q $dbCommand
}

We can also take advantage of the Invoke-Sqlcmd command to do the same thing. Here is how the function would look like:

function global:RestoreDB ([string] $newDBName, [string] $backupFilePath)
{
    [string] $dbCommand = "RESTORE DATABASE [$newDBName] " +
                          "FROM    DISK = N'$backupFilePath' " +
                          "WITH    FILE = 1, NOUNLOAD, STATS = 10"

    Invoke-Sqlcmd -Query $dbCommand
}

If using Invoke-Sqlcmd fails, make sure the SqlServerCmdletSnapin100 snapin is added. You can put the below snippet in the function above before the call to Invoke-Sqlcmd.

$sqlSnapin = Get-PSSnapin | where {$_.Name -eq "SqlServerCmdletSnapin100"}
if($sqlSnapin -eq $null)
{
Add-PSSnapin SqlServerCmdletSnapin100
}

Calling this function is as simple as:

RestoreDB "NewDatabaseName" "C:\.etc..\AdventureWorksLT2008R2.bak"

Remote SQL Server

In case your SQL Server is on a remote machine that doesn’t have the SQL client installed, you can use the Invoke-Command to restore the database on the remote machine. However, the function needs to be loaded to be invoked on the remote machine, so either put it in a separate file and load it remotely or convert it to a script block that can be directly passed to Invoke-Command.

Assuming the remote SQL server name is SQLServer01, here are the two approaches to do this.

Using a Function

Put the RestoreDB function in a new PowerShell file; Let’s call it DatabaseRestore.ps1. To call remotely, first we need to create a PowerShell session on the remote SQL Server machine.

$session = New-PSSession -ComputerName "SQLServer01"

If you are using SQL Server 2008 R2, you might get the following error: “Connecting to remote server failed with the following error message : The WinRM client cannot complete the operation within the time specified. Check if the machine name is valid and is reachable over the network and firewall exception for Windows Remote Management service is enabled“. The resolution is located here. In short, go to your SQL Server 2008 R2 machine, launch the Command Prompt as administrator then run this command: winrm quickconfig.

After creating the session, we need to load the DatabaseRestore.ps1 script on the remote machine to be able to call the RestoreDB function.

$scriptPath = "C:\..etc..\DatabaseRestore.ps1"
Invoke-Command -Session $session -FilePath $scriptPath

If you get an error that the file cannot be loaded because the execution of scripts is disabled on the system, then you should make sure that the execution policy is remotesigned or unrestricted (Set-ExecutionPolicy unrestricted).

Next step would be to simply call the function. Note that the path to the backup file must be accessible to the remote SQL machine.

Invoke-Command -Session $session -ScriptBlock { RestoreDB "NewDatabaseName" "C:\..etc..\AdventureWorksLT2008R2.bak" }
Using a Script Block

In our case, using a script block is simpler. All we need to do is define the script block, then run one single Invoke-Command to do the database restore. The script block definition is almost the same as the function definition, as shown below:

[ScriptBlock] $global:RestoreDB = {

    param ([string] $newDBName, [string] $backupFilePath)

    [string] $dbCommand = "RESTORE DATABASE [$newDBName] " +
                          "FROM    DISK = N'$backupFilePath' " +
                          "WITH    FILE = 1, NOUNLOAD, STATS = 10"

    $sqlSnapin = Get-PSSnapin | where {$_.Name -eq "SqlServerCmdletSnapin100"}
    if($sqlSnapin -eq $null)
    {
         Add-PSSnapin SqlServerCmdletSnapin100
    }

    Invoke-Sqlcmd -Query $dbCommand
}

Make sure you don’t forget the equal sign (=) in the first line of the above script block definition. Now, to restore the DB, we call a single Invoke-Command cmdlet. Make sure that the -ArgumentList parameters are separated by comma (,) or the script will fail.

Invoke-Command -ComputerName "SQLServer01" -ScriptBlock $RestoreDB -ArgumentList "NewDatabaseName", "C:\AdventureWorksLT2008R2.bak" 
Function vs. Script Block

Here are some simple guidelines on when to use a function and when to use a script block.

  • To call a function on a remote machine, it must first be defined on the remote machine. That’s why we need an Invoke-Command to load the PowerShell file containing the function, then another Invoke-Command to call the function.
  • To call a script block remotely, it doesn’t have to be defined on the remote machine. When the script block is passed as a parameter to Invoke-Command, the whole script block actually gets copied to the remote machine.
  • If your logic has any dependency on any global variable or function (Ex: it calls another script block or it calls a helper function), then it makes most sense to use a function. Define the function, global variables and helper functions in one file, then load them on the remote machine.
  • If your logic is self-contained, then use a script block. The whole logic will get copied to the remote machine.

Database Restore – SMO

To have more control on how we do the database restore, we should use the SMO object model. For example, our script above restores the database with name “NewDatabaseName” but the MDF and LDF file names are still AdventureWorksLT2008R2_Data.mdf and AdventureWorksLT2008R2_Log.ldf. Now, you would think, why not use the SQL statement below in our script?

RESTORE DATABASE [NewDatabaseName]
FROM DISK = N'C:\.etc..\AdventureWorksLT2008R2.bak'
WITH FILE = 1,
MOVE N'AdventureWorksLT2008R2_Data'
TO N'C:\.etc..\MSSQL\DATA\NewDatabaseName.mdf',
MOVE N'AdventureWorksLT2008R2_Log'
TO N'C:\.etc..\MSSQL\DATA\NewDatabaseName_1.ldf',
NOUNLOAD, STATS = 10

To put this in a script block, it will look as follows:

[ScriptBlock] $global:RestoreDB = {

param ([string] $newDBName, [string] $backupFilePath, [string] $sqlDataPath, [string] $dataLogicalName, [string] $logLogicalName)

[string] $dbCommand = "RESTORE DATABASE [$newDBName] " +
"FROM    DISK = N'$backupFilePath' " +
"WITH    FILE = 1, " +
"MOVE N'$dataLogicalName' " +
"TO N'$sqlDataPath\$newDBName.mdf', " +
"MOVE N'$logLogicalName' " +
"TO N'$sqlDataPath\$newDBName.ldf', " +
"NOUNLOAD, STATS = 10"

$sqlSnapin = Get-PSSnapin | where {$_.Name -eq "SqlServerCmdletSnapin100"}
if($sqlSnapin -eq $null)
{
Add-PSSnapin SqlServerCmdletSnapin100
}

Invoke-Sqlcmd -Query $dbCommand
}

Ok, this might be good enough, but it’s not dynamic\generic. You can get the SQL data path from the registry, but you cannot get the logical names of the data and log files unless you find a way to open the .bak file and read the logical names of those files. Instead of hardcoding the logical names of the Data and Log files (i.e. pass “AdventureWorksLT2008R2_Data” and “AdventureWorksLT2008R2_Log”), we can read the file list from the .bak file using SMO (ReadFileList() method).

PowerShell comments below provide enough details. Note that if the backup file is on a network share, the ReadFileList() method would fail. So in that case, we need to copy the file locally. That’s why the script block takes “$isNetworkPath” boolean variable to take that into consideration.

[ScriptBlock] $global:RestoreDBSMO = {
    param([string] $newDBName, [string] $backupFilePath, [bool] $isNetworkPath = $true)

    try
    {
        # Load assemblies
        [System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SqlServer.SMO") | Out-Null
        [System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SqlServer.SmoExtended") | Out-Null
        [Reflection.Assembly]::LoadWithPartialName("Microsoft.SqlServer.ConnectionInfo") | Out-Null
        [Reflection.Assembly]::LoadWithPartialName("Microsoft.SqlServer.SmoEnum") | Out-Null

        # Create sql server object
        $server = New-Object ("Microsoft.SqlServer.Management.Smo.Server") "(local)"

        # Copy database locally if backup file is on a network share
        if($isNetworkPath)
        {
            $fileName = [IO.Path]::GetFileName($backupFilePath)
            $localPath = Join-Path -Path $server.DefaultFile -ChildPath $fileName
            Copy-Item $backupFilePath $localPath
            $backupFilePath = $localPath
        }

        # Create restore object and specify its settings
        $smoRestore = new-object("Microsoft.SqlServer.Management.Smo.Restore")
        $smoRestore.Database = $newDBName
        $smoRestore.NoRecovery = $false;
        $smoRestore.ReplaceDatabase = $true;
        $smoRestore.Action = "Database"

        # Create location to restore from
        $backupDevice = New-Object("Microsoft.SqlServer.Management.Smo.BackupDeviceItem") ($backupFilePath, "File")
        $smoRestore.Devices.Add($backupDevice)

        # Give empty string a nice name
        $empty = ""

        # Specify new data file (mdf)
        $smoRestoreDataFile = New-Object("Microsoft.SqlServer.Management.Smo.RelocateFile")
        $defaultData = $server.DefaultFile
        if (($defaultData -eq $null) -or ($defaultData -eq $empty))
        {
            $defaultData = $server.MasterDBPath
        }
        $smoRestoreDataFile.PhysicalFileName = Join-Path -Path $defaultData -ChildPath ($newDBName + "_Data.mdf")

        # Specify new log file (ldf)
        $smoRestoreLogFile = New-Object("Microsoft.SqlServer.Management.Smo.RelocateFile")
        $defaultLog = $server.DefaultLog
        if (($defaultLog -eq $null) -or ($defaultLog -eq $empty))
        {
            $defaultLog = $server.MasterDBLogPath
        }
        $smoRestoreLogFile.PhysicalFileName = Join-Path -Path $defaultLog -ChildPath ($newDBName + "_Log.ldf")

        # Get the file list from backup file
        $dbFileList = $smoRestore.ReadFileList($server)

        # The logical file names should be the logical filename stored in the backup media
        $smoRestoreDataFile.LogicalFileName = $dbFileList.Select("Type = 'D'")[0].LogicalName
        $smoRestoreLogFile.LogicalFileName = $dbFileList.Select("Type = 'L'")[0].LogicalName

        # Add the new data and log files to relocate to
        $smoRestore.RelocateFiles.Add($smoRestoreDataFile)
        $smoRestore.RelocateFiles.Add($smoRestoreLogFile)

        # Restore the database
        $smoRestore.SqlRestore($server)

        "Database restore completed successfully"
    }
    catch [Exception]
    {
        "Database restore failed:`n`n " + $_.Exception
    }
    finally
    {
        # Clean up copied backup file after restore completes successfully
        if($isNetworkPath)
        {
            Remove-Item $backupFilePath
        }
    }
}

Here is how to call this script block (Don’t forget the dot (.) infront of the script block variable):

.$RestoreDBSMO "NewDatabaseName" "C:\.etc..\AdventureWorksLT2008R2.bak" $false

Same story goes for calling this function remotely.

Generating a GUID


A GUID is a 128-bit integer (16 bytes) that can be used across all computers and networks wherever a unique identifier is required. Such an identifier has a very low probability of being duplicated. The term is usually referred to as GUID (Globally Unique Identifier) when working with Microsoft technologies. Otherwise, it is referred to as UUID (Universally Unique Identifier).

Here are multiple ways to generate a GUID:

Visual Studio

Run guidgen.exe. There are two ways to run guidgen:

  1. Open Visual Studio IDE, go to Tool menu, and select the Create Guid menu item. This option is available in VS 2008 but not in VS 2010. So use method 2 if you have VS 2010 installed.
  2. Open Visual Studio Command Prompt (from start menu) and enter the following command: guidgen.

Using any of the methods above, you get the following:

guidgen

You can use any of the 4 formats available, but usually the Registry format (currently selected) is the mostly used one. To generate a new GUID, click New GUID. To copy the GUID to the clipboard, click Copy.

.Net

You can generate a Guid using any .Net language. Here is how you can do it with C#.

Guid myGuid = System.Guid.NewGuid();

SQL Server

A GUID is represented as type uniqueidentifier in T-SQL. It is generated as shown below.

SELECT newid()

Online

If none of the above methods are available for you, you can get one generated online at http://www.guidgenerator.com/.

Follow

Get every new post delivered to your Inbox.

%d bloggers like this: