A PowerShell related post today.<\/p>\n
If you need to create a new site collection and ensure it uses a specific content database, this little script will get that done for you. No messing about in Central Administration disabling content databases and all that good stuff, just a simple script that gets the job done, hassle free.<\/p>\n
\r\n$hostIP = $ENV:ComputerName\r\n$hostURL = \"http:\/\/$hostIP\/sites\/Site Collection Name\"\r\n$user = [Security.Principal.WindowsIdentity]::GetCurrent().Name\r\n$dbServer = \"$hostIP\"\r\n$contentDbName = \"Your_Content_Db_Name\"\r\n$webAppName = \"SharePoint - 80\"\r\n$lcid = 1033\r\n$templateName = \"STS#0\"\r\n$siteName = \"Site Collection Name\"\r\n\r\nfunction Add-Site {\r\n\tWrite-Host (\"Creating new ComplianceSP site '\", $siteName, \"' at \", $hostURL -join \"\") -NoNewline\r\n\t$newSite = New-SPSite $hostURL -OwnerAlias $user -name $siteName -Template $templateName -Language $lcid -ContentDatabase $contentDbName\r\n\t$newSite.RootWeb.CreateDefaultAssociatedGroups($newSite.Owner, $null, $null)\r\n\tWrite-Host \" - Done.\" -ForegroundColor Green\r\n}\r\n\r\nfunction Add-ContentDatabase {\r\n\t$contentDatabase = Get-SPContentDatabase -WebApplication $webAppName | Where { $_.Name -eq $contentDbName }\r\n\tif ($contentDatabase -eq $null) {\r\n\t\tWrite-Host (\"Creating new content database '\", $contentDbName, \"' in '\", $dbServer, \"' for web application '\", $webAppName, \"'\" -join \"\") -NoNewline\r\n\t\tNew-SPContentDatabase -Name $contentDbName -DatabaseServer $dbServer -WebApplication $webAppName -MaxSiteCount 1 -WarningSiteCount 0 -Confirm:$false\r\n\t\tWrite-Host \" - Done.\" -ForegroundColor Green\r\n\t}\r\n\telse {\r\n\t\tWrite-Host (\"Content database '\", $contentDbName, \"' in '\", $dbServer, \"' associated with web application '\", $webAppName, \"' already exists.\" -join \"\") -NoNewline\r\n\t}\r\n}\r\n\r\ntry {\r\n\tAdd-ContentDatabase\r\n\tAdd-Site\r\n}\r\ncatch {\r\n\tWrite-Host \"\"\r\n\tWrite-Host \"Error : \" $Error[0] -ForegroundColor Red\r\n\tthrow\r\n\tExit 1\r\n}\r\n<\/pre>\nLets walk through the code.
\n
\nFirst off we declare a number of variables that are used to create the site collection and associate it with a specific content database.<\/p>\n
$hostURL stores the fully qualified URL of the site collection you want to create.
\n$dbServer references the database server, as you probably guessed \ud83d\ude42
\n$contentDbName should contain the name of the content database you want to associate with the site collection
\n$webAppName is the name of the web application the site collection will belong to.
\n$lcid is the locale id to be used when creating the site collection.
\n$templateName is the name of the SharePoint template to use for the root of the new site collection.
\n$siteName contains the name of the root site.<\/p>\n
The first section of code that is called is to Add-ContentDatabase. What this method does is attempt to retrieve the content database specified by $contentDbName within the configured web application. If the content database exists the method exits without doing anything else. If it does not exist, it then calls New-SPContentDatabase and creates the content database with a maximum site count of 1, this will allow it to only be used by the site collection that’s created next.<\/p>\n
The final piece of the script is a call to the Add-Site method.<\/p>\n
Here, we call New-SPSite and importantly set the content database parameter to $contentDbName. Once this has completed we ensure the new site’s owner is a member of the site owners group.<\/p>\n
Nothing too complicated by handy to know.<\/p>\n","protected":false},"excerpt":{"rendered":"
A PowerShell related post today. If you need to create a new site collection and ensure it uses a specific content database, this little script will get that done for you. No messing about in Central Administration disabling content databases … Continue reading