Downloads:

31,592

Downloads of v 14.0.3048.4:

210

Last Update:

19 Dec 2018

Package Maintainer(s):

Software Author(s):

  • Microsoft Corporation

Tags:

SQL Server Cumulative Update 2017

Microsoft SQL Server 2017 Cumulative Update 13

This is not the latest version of Microsoft SQL Server 2017 Cumulative Update 13 available.

  • 1
  • 2
  • 3

14.0.3048.4 | Updated: 19 Dec 2018

Downloads:

31,592

Downloads of v 14.0.3048.4:

210

Maintainer(s):

Software Author(s):

  • Microsoft Corporation

  • 1
  • 2
  • 3
Microsoft SQL Server 2017 Cumulative Update 13 14.0.3048.4

This is not the latest version of Microsoft SQL Server 2017 Cumulative Update 13 available.

  • 1
  • 2
  • 3

This Package Contains an Exempted Check

Not All Tests Have Passed


Validation Testing Passed


Verification Testing Passed

Details

Scan Testing Exemption for this package version only:

Details

To install Microsoft SQL Server 2017 Cumulative Update 13, run the following command from the command line or from PowerShell:

>

To upgrade Microsoft SQL Server 2017 Cumulative Update 13, run the following command from the command line or from PowerShell:

>

To uninstall Microsoft SQL Server 2017 Cumulative Update 13, 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://community.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://community.chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade sql-server-2017-cumulative-update -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 sql-server-2017-cumulative-update -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 sql-server-2017-cumulative-update installed
  win_chocolatey:
    name: sql-server-2017-cumulative-update
    state: present
    version: 14.0.3048.4
    source: STEP 3 URL

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


chocolatey_package 'sql-server-2017-cumulative-update' do
  action    :install
  version  '14.0.3048.4'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: sql-server-2017-cumulative-update,
    Version: 14.0.3048.4,
    Source: STEP 3 URL
);

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


cChocoPackageInstaller sql-server-2017-cumulative-update
{
   Name     = 'sql-server-2017-cumulative-update'
   Ensure   = 'Present'
   Version  = '14.0.3048.4'
   Source   = 'STEP 3 URL'
}

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


package { 'sql-server-2017-cumulative-update':
  provider => 'chocolatey',
  ensure   => '14.0.3048.4',
  source   => 'STEP 3 URL',
}

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


salt '*' chocolatey.install sql-server-2017-cumulative-update version="14.0.3048.4" 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 as a trusted package on 26 Feb 2019.

Description

The latest Cumulative Update (CU) download is the most recent CU released for SQL Server 2017 and contains all updates released since the release of SQL Server 2017 RTM.

  • Each new CU contains all the fixes that were included in the previous CU for the installed version of SQL Server.
  • SQL Server CUs are certified to the same levels as Service Packs, and should be installed at the same level of confidence.
  • Microsoft recommends ongoing, proactive installation of CUs as they become available:
    • Historical data shows that a significant number of support cases involve an issue that has already been addressed in a released CU.
    • CUs may contain added value over and above hotfixes. This includes supportability, manageability, and reliability updates.
  • We recommend that you test CUs before you deploy them to production environments.

Uninstalling

Uninstalling with Chocolatey is known to not be reliable, as the uninstaller wants to locate sql_engine_core_inst_loc.msi from the original installation media.

Should you need to uninstall this cumulative update, you may need to revert to manual uninstallation via Programs and Features, Installed Updates.


tools\chocolateyinstall.ps1
$ErrorActionPreference = 'Stop';
$toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"

$url        = 'https://download.microsoft.com/download/C/4/F/C4F908C9-98ED-4E5F-88D5-7D6A5004AEBD/SQLServer2017-KB4466404-x64.exe'
$checksum   = '7ba817cf8c5dce3f267f6e720a2d3a19c34280464eb126af638c8cb833af0406'
$softwareName = 'Hotfix 3048 for SQL Server 2017*(KB4466404)*'

$filename = [IO.Path]::GetFileName($url)

# Download like Install-ChocolateyPackage (so we can restart from cached download)
$chocTempDir = $env:TEMP
$tempDir = Join-Path $chocTempDir "$($env:chocolateyPackageName)"
if ($env:chocolateyPackageVersion -ne $null) { $tempDir = Join-Path $tempDir "$($env:chocolateyPackageVersion)"; }
$tempDir = $tempDir -replace '\\chocolatey\\chocolatey\\', '\chocolatey\'
if (![System.IO.Directory]::Exists($tempDir)) { [System.IO.Directory]::CreateDirectory($tempDir) | Out-Null }
$downloadFilePath = Join-Path $tempDir "$($packageName)Install.$fileType"

$fullFilePath = Join-Path $toolsDir $filename

$packageArgs = @{
  packageName   = $env:ChocolateyPackageName
  url           = $url
  FileFullPath  = $downloadFilePath
  checksum      = $checksum
  checksumType  = 'sha256'
}

$filePath = Get-ChocolateyWebFile @packageArgs

# Copy into tools to keep for uninstall
Copy-Item $filePath -Destination $fullFilePath

$packageArgs = @{
  packageName   = $env:ChocolateyPackageName
  file  = $fullFilePath
  softwareName  = $softwareName
  silentArgs    = "/q /IAcceptSQLServerLicenseTerms /Action=Patch /AllInstances"
  validExitCodes= @(0, 3010, 1641)
}

Install-ChocolateyInstallPackage @packageArgs

$files = get-childitem $toolsDir -include *.exe -recurse

foreach ($file in $files) {
  # generate an ignore file
  New-Item "$file.ignore" -type file -force | Out-Null
}

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 2017 Cumulative Update 24 14.0.3391.2 6097 Monday, May 10, 2021 Approved
Microsoft SQL Server 2017 Cumulative Update 23 14.0.3381.3 1135 Saturday, February 27, 2021 Approved
Microsoft SQL Server 2017 Cumulative Update 22 14.0.3356.20 1946 Wednesday, September 16, 2020 Approved
Microsoft SQL Server 2017 Cumulative Update 21 14.0.3335.7 10049 Thursday, July 2, 2020 Approved
Microsoft SQL Server 2017 Cumulative Update 20 14.0.3294.2 1517 Wednesday, April 8, 2020 Approved
Microsoft SQL Server 2017 Cumulative Update 19 14.0.3281.20200208 618 Saturday, February 8, 2020 Approved
Microsoft SQL Server 2017 Cumulative Update 18 14.0.3281.6 304 Wednesday, February 5, 2020 Approved
Microsoft SQL Server 2017 Cumulative Update 18 14.0.3257.3 393 Tuesday, December 10, 2019 Approved

This package has no dependencies.

Discussion for the Microsoft SQL Server 2017 Cumulative Update 13 Package

Ground Rules:

  • This discussion is only about Microsoft SQL Server 2017 Cumulative Update 13 and the Microsoft SQL Server 2017 Cumulative Update 13 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 2017 Cumulative Update 13, 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