Unpacking Software Livestream

Join our monthly Unpacking Software livestream to hear about the latest news, chat and opinion on packaging, software deployment and lifecycle management!

Learn More

Chocolatey Product Spotlight

Join the Chocolatey Team on our regular monthly stream where we put a spotlight on the most recent Chocolatey product releases. You'll have a chance to have your questions answered in a live Ask Me Anything format.

Learn More

Chocolatey Coding Livestream

Join us for the Chocolatey Coding Livestream, where members of our team dive into the heart of open source development by coding live on various Chocolatey projects. Tune in to witness real-time coding, ask questions, and gain insights into the world of package management. Don't miss this opportunity to engage with our team and contribute to the future of Chocolatey!

Learn More

Calling All Chocolatiers! Whipping Up Windows Automation with Chocolatey Central Management

Webinar from
Wednesday, 17 January 2024

We are delighted to announce the release of Chocolatey Central Management v0.12.0, featuring seamless Deployment Plan creation, time-saving duplications, insightful Group Details, an upgraded Dashboard, bug fixes, user interface polishing, and refined documentation. As an added bonus we'll have members of our Solutions Engineering team on-hand to dive into some interesting ways you can leverage the new features available!

Watch On-Demand
Chocolatey Community Coffee Break

Join the Chocolatey Team as we discuss all things Community, what we do, how you can get involved and answer your Chocolatey questions.

Watch The Replays
Chocolatey and Intune Overview

Webinar Replay from
Wednesday, 30 March 2022

At Chocolatey Software we strive for simple, and teaching others. Let us teach you just how simple it could be to keep your 3rd party applications updated across your devices, all with Intune!

Watch On-Demand
Chocolatey For Business. In Azure. In One Click.

Livestream from
Thursday, 9 June 2022

Join James and Josh to show you how you can get the Chocolatey For Business recommended infrastructure and workflow, created, in Azure, in around 20 minutes.

Watch On-Demand
The Future of Chocolatey CLI

Livestream from
Thursday, 04 August 2022

Join Paul and Gary to hear more about the plans for the Chocolatey CLI in the not so distant future. We'll talk about some cool new features, long term asks from Customers and Community and how you can get involved!

Watch On-Demand
Hacktoberfest Tuesdays 2022

Livestreams from
October 2022

For Hacktoberfest, Chocolatey ran a livestream every Tuesday! Re-watch Cory, James, Gary, and Rain as they share knowledge on how to contribute to open-source projects such as Chocolatey CLI.

Watch On-Demand

Downloads:

615

Downloads of v 1.10:

67

Last Update:

21 Nov 2019

Package Maintainer(s):

Software Author(s):

  • Devart

Tags:

database index fragmentation rebuild sql tools trial

dbForge Index Manager for SQL Server (Trial)

Downloads:

615

Downloads of v 1.10:

67

Maintainer(s):

Software Author(s):

  • Devart

dbForge Index Manager for SQL Server (Trial)

  • 1
  • 2
  • 3

This Package Contains an Exempted Check

Not All Tests Have Passed


Validation Testing Passed


Verification Testing Exemption:

Dependency requires reboot

Details

Scan Testing Successful:

No detections found in any package files

Details
WARNING

This package was rejected on 01 Jan 2020. The reviewer chocolatey-ops has listed the following reason(s):

Devart (maintainer) on 14 Nov 2019 14:12:49 +00:00:

User 'Devart' (maintainer) submitted package.

chocolatey-ops (reviewer) on 14 Nov 2019 14:44:34 +00:00:

dbforge-sql-im has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.

Notes

Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.

  • The package maintainer field (owners) matches the software author field (authors) in the nuspec. The reviewer will ensure that the package maintainer is also the software author. More...

chocolatey-ops (reviewer) on 14 Nov 2019 16:48:00 +00:00:

dbforge-sql-im has failed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/5697f600f5dadb50394b2162d32fc1f1 for details.
The package status will be changed and will be waiting on your next actions.

  • NEW! We have a test environment for you to replicate the testing we do. This can be used at any time to test packages! See https://github.com/chocolatey/chocolatey-test-environment
  • Please log in and leave a review comment if you have questions and/or comments.
  • If you see the verifier needs to rerun testing against the package without resubmitting (a issue in the test results), you can do that on the package page in the review section.
  • If the verifier is incompatible with the package, please log in and leave a review comment if the package needs to bypass testing (e.g. package installs specific drivers).
  • Automated testing can also fail when a package is not completely silent or has pop ups (AutoHotKey can assist - a great example is the VeraCrypt package).
  • A package that cannot be made completely unattended should have the notSilent tag. Note that this must be approved by moderators.

Devart (maintainer) on 15 Nov 2019 07:56:11 +00:00:

Request to skip automated testing for this package.
Reason: Requires .NET 4.5.2. Chocolatey package dotnet4.5.2 included as dependency, but it
is not completly silent and it require reboot. That is why automated testing is failed.
Many thanks.
Auto Verification Change - Verification tests have been set to rerun.

Pauby (reviewer) on 15 Nov 2019 14:34:09 +00:00:

.NET 4.7.2 also required.

Devart (maintainer) on 21 Nov 2019 15:32:38 +00:00:

User 'Devart' (maintainer) submitted package.

chocolatey-ops (reviewer) on 21 Nov 2019 16:07:43 +00:00:

dbforge-sql-im has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.

Notes

Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.

  • The package maintainer field (owners) matches the software author field (authors) in the nuspec. The reviewer will ensure that the package maintainer is also the software author. More...

chocolatey-ops (reviewer) on 21 Nov 2019 19:33:03 +00:00:

dbforge-sql-im has failed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/364ad95f1300c2bc84abe8462b02d713 for details.
The package status will be changed and will be waiting on your next actions.

  • NEW! We have a test environment for you to replicate the testing we do. This can be used at any time to test packages! See https://github.com/chocolatey/chocolatey-test-environment
  • Please log in and leave a review comment if you have questions and/or comments.
  • If you see the verifier needs to rerun testing against the package without resubmitting (a issue in the test results), you can do that on the package page in the review section.
  • If the verifier is incompatible with the package, please log in and leave a review comment if the package needs to bypass testing (e.g. package installs specific drivers).
  • Automated testing can also fail when a package is not completely silent or has pop ups (AutoHotKey can assist - a great example is the VeraCrypt package).
  • A package that cannot be made completely unattended should have the notSilent tag. Note that this must be approved by moderators.

Devart (maintainer) on 22 Nov 2019 07:29:20 +00:00:

Request to skip automated testing for this package.
Reason: Requires .NET 4.7.2. Chocolatey package dotnet4.7.2 included as dependency, but it
is not completly silent and it require reboot. That is why automated testing is failed.
Many thanks.
Auto Verification Change - Verification tests have been set to rerun.

Pauby (reviewer) on 27 Nov 2019 18:01:23 +00:00:

Hi,

Can you confirm this has been tested in the Chocolatey Test Environment? Several other packages required Visual Studio - can you also confirm that this does not?

Thanks.

chocolatey-ops (reviewer) on 17 Dec 2019 18:04:22 +00:00:

We've found dbforge-sql-im v1.10 in a submitted status and waiting for your next actions. It has had no updates for 20 or more days since a reviewer has asked for corrections. Please note that if there is no response or fix of the package within 15 days of this message, this package version will automatically be closed (rejected) due to being stale.

Take action:

  • Log in to the site and respond to the review comments.
  • Resubmit fixes for this version.
  • If the package version is failing automated checks, you can self-reject the package.

If your package is failing automated testing, you can use the chocolatey test environment to manually run the verification and determine what may need to be fixed.

Note: We don't like to see packages automatically rejected. It doesn't mean that we don't value your contributions, just that we can not continue to hold packages versions in a waiting status that have possibly been abandoned. If you don't believe you will be able to fix up this version of the package within 15 days, we strongly urge you to log in to the site and respond to the review comments until you are able to.

chocolatey-ops (reviewer) on 01 Jan 2020 18:08:46 +00:00:

Unfortunately there has not been progress to move dbforge-sql-im v1.10 towards an approved status within 15 days after the last review message, so we need to close (reject) the package version at this time. If you want to pick this version up and move it towards approval in the future, use the contact site admins link on the package page and we can move it back into a submitted status so you can submit updates.

Status Change - Changed status of package from 'submitted' to 'rejected'.

Devart (maintainer) on 28 Oct 2020 00:31:45 +00:00:

We kindly request you to disable/skip the automatic testing for this package.
The reason: dependency from the .NET 4.7.2 which requires PC reboot to be installed successfully.

Devart (maintainer) on 21 Aug 2021 14:07:13 +00:00:

We kindly request you to disable/skip the automatic testing for this package.
The reason: dependency from the .NET 4.7.2 which requires PC reboot to be installed successfully.
Verification Status Change - Verification tests have been set to rerun.

Description

dbForge Index Manager for SQL Server is an SSMS add-in for analyzing the status of SQL indexes and fixing issues with index fragmentation. The tool allows you to quickly collect index fragmentation statistics and detect databases that require maintenance. You can instantly rebuild and reorganize SQL indexes in visual mode or generate SQL script for the future use.


tools\chocolateyinstall.ps1
$ErrorActionPreference = 'Stop'; 
$toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$url        = 'https://www.devart.com/dbforge/sql/developer-bundle/developerbundlesql.exe' 
$packageArgs = @{
  packageName   = $env:ChocolateyPackageName
  unzipLocation = $toolsDir
  fileType      = 'exe' 
  url           = $url 
  softwareName  = 'dbForge Index Manager for SQL Server, v1.10 Standard Edition' 
  checksum      = '781431FD546CA1AE6F547FFD1DE58D356AAB7F442F54C1D3A1FE528C307F4FEA'
  checksumType  = 'sha256' 
  silentArgs    = '/VERYSILENT'
  validExitCodes= @(0, 3010, 1641)
}
Install-ChocolateyPackage @packageArgs 
tools\chocolateyuninstall.ps1
$ErrorActionPreference = 'Stop';
$packageArgs = @{
  packageName   = $env:ChocolateyPackageName
  softwareName  = 'dbForge Index Manager for SQL Server, v1.10 Standard Edition'
  fileType      = 'exe'

  silentArgs    = '/VERYSILENT'
  validExitCodes= @(0, 3010, 1605, 1614, 1641)  
}

[array]$key = Get-UninstallRegistryKey -SoftwareName $packageArgs['softwareName']


if ($key.Count -eq 1) {
  $key | % { 
    $packageArgs['file'] = "$($_.UninstallString)"
    if ($packageArgs['fileType'] -eq 'MSI') {
      $packageArgs['silentArgs'] = "$($_.PSChildName) $($packageArgs['silentArgs'])"
      $packageArgs['file'] = ''
    }

    Uninstall-ChocolateyPackage @packageArgs
  }
} elseif ($key.Count -eq 0) {
  Write-Warning "$packageName has already been uninstalled by other means."
} elseif ($key.Count -gt 1) {
  Write-Warning "$($key.Count) matches found!"
  Write-Warning "To prevent accidental data loss, no programs will be uninstalled."
  Write-Warning "Please alert package maintainer the following keys were matched:"
  $key | % {Write-Warning "- $($_.DisplayName)"}
}

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.

Add to Builder Version Downloads Last Updated Status
dbForge Index Manager for SQL Server 1.13.22 20 Tuesday, January 2, 2024 Approved
dbForge Index Manager for SQL Server 1.13.20 35 Wednesday, July 26, 2023 Approved
dbForge Index Manager for SQL Server 1.13.17 35 Tuesday, May 16, 2023 Approved
dbForge Index Manager for SQL Server 1.13.14.20230424 23 Monday, April 24, 2023 Approved
dbForge Index Manager for SQL Server 1.13.14.20230105 44 Thursday, January 5, 2023 Approved
dbForge Index Manager for SQL Server 1.13.11.20220915 43 Thursday, September 15, 2022 Approved
dbForge Index Manager for SQL Server 1.13.11.20220912 35 Wednesday, September 14, 2022 Approved
dbForge Index Manager for SQL Server 1.12.3.20211231 79 Friday, December 31, 2021 Approved
dbForge Index Manager for SQL Server (Trial) 1.11.58.20210913 60 Monday, September 13, 2021 Approved
dbForge Index Manager for SQL Server (Trial) 1.11.46.20210905 61 Saturday, September 4, 2021 Approved

Discussion for the dbForge Index Manager for SQL Server (Trial) Package

Ground Rules:

  • This discussion is only about dbForge Index Manager for SQL Server (Trial) and the dbForge Index Manager for SQL Server (Trial) 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 dbForge Index Manager for SQL Server (Trial), 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