Downloads:

16,048

Downloads of v 11.0.2100.61:

11,856

Last Update:

25 Sep 2016

Package Maintainer(s):

Software Author(s):

  • Microsoft

Tags:

SQL SQL2012 SMO .NET XML CLR

Microsoft SQL Server 2012 Management Objects

11.0.2100.61 | Updated: 25 Sep 2016

Downloads:

16,048

Downloads of v 11.0.2100.61:

11,856

Maintainer(s):

Software Author(s):

  • Microsoft

Tags:

SQL SQL2012 SMO .NET XML CLR

Microsoft SQL Server 2012 Management Objects 11.0.2100.61

All Checks are Passing

2 Passing Test

Validation Testing Passed

Verification Testing Passed

Details

To install Microsoft SQL Server 2012 Management Objects, run the following command from the command line or from PowerShell:

>

To upgrade Microsoft SQL Server 2012 Management Objects, run the following command from the command line or from PowerShell:

>

To uninstall Microsoft SQL Server 2012 Management Objects, run the following command from the command line or from PowerShell:

>

NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://chocolatey.org/api/v2. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to https://chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade sql2012.smo -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade sql2012.smo -y --source="'STEP 3 URL'"
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode


- name: Ensure sql2012.smo installed
  win_chocolatey:
    name: sql2012.smo
    state: present
    version: 11.0.2100.61
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'sql2012.smo' do
  action    :install
  version  '11.0.2100.61'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: sql2012.smo,
    Version: 11.0.2100.61,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller sql2012.smo
{
   Name     = 'sql2012.smo'
   Ensure   = 'Present'
   Version  = '11.0.2100.61'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'sql2012.smo':
  provider => 'chocolatey',
  ensure   => '11.0.2100.61',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install sql2012.smo version="11.0.2100.61" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package was approved by moderator gep13 on 17 Oct 2016.

Description

The SQL Server Management Objects (SMO) is a .NET Framework object model that enables software developers to create client-side applications to manage and administer SQL Server objects and services. This object model will work with SQL Server 2000, SQL Server 2005, SQL Server 2008, SQL Server 2008 R2 and SQL Server 2012.

README.md 
SQL2012.SMO
===========

Chocolatey package for SQL2012.SMO
SQL2012.png
tools\chocolateyInstall.ps1 
$params = @{
  packageName = 'sql2012.smo';
  fileType = 'msi';
  silentArgs = '/quiet';
  url = 'http://download.microsoft.com/download/F/E/D/FEDB200F-DE2A-46D8-B661-D019DFE9D470/ENU/x86/SharedManagementObjects.msi';
  checksum='AFC0ECCB35C979801344B0DC04556C23C8B957F1BDEE3530BC1A59D5C704CE64'
  checksumType='Sha256'
}

Install-ChocolateyPackage @params

# install both x86 and x64 editions of SMO since x64 supports both
# to install both variants of p owershell, both variants of SMO must be present
if (Get-ProcessorBits -eq 64) {
  $params['url'] = ''
  $params['url64'] = 'http://download.microsoft.com/download/F/E/D/FEDB200F-DE2A-46D8-B661-D019DFE9D470/ENU/x64/SharedManagementObjects.msi'
  $params['checksum64'] = 'ED753D85B51E7EAE381085CAD3DCC0F29C0B72F014F8F8FBA1AD4E0FE387CE0A'
  $params['checksumType64'] = 'Sha256'
  Install-ChocolateyPackage @params
}

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
Microsoft SQL Server 2012 Management Objects 11.0.2100.61 11856 Sunday, September 25, 2016 Approved
Microsoft SQL Server 2012 Management Objects 11.0.2100.60 3518 Tuesday, September 30, 2014 Unknown
Discussion for the Microsoft SQL Server 2012 Management Objects Package

Ground Rules:

  • This discussion is only about Microsoft SQL Server 2012 Management Objects and the Microsoft SQL Server 2012 Management Objects package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or Microsoft SQL Server 2012 Management Objects, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus