Downloads:
24,740
Downloads of v 3.47.0:
65
Last Update:
22 Oct 2024
Package Maintainer(s):
Software Author(s):
- D. Richard Hipp
- SQLite contributors
Tags:
sqlite db database analyzer embedded hwaciSQLite Analyzer
This is not the latest version of SQLite Analyzer available.
- 1
- 2
- 3
3.47.0 | Updated: 22 Oct 2024
Downloads:
24,740
Downloads of v 3.47.0:
65
Maintainer(s):
Software Author(s):
- D. Richard Hipp
- SQLite contributors
SQLite Analyzer 3.47.0
This is not the latest version of SQLite Analyzer available.
Legal Disclaimer: Neither this package nor Chocolatey Software, Inc. are affiliated with or endorsed by D. Richard Hipp, SQLite contributors. The inclusion of D. Richard Hipp, SQLite contributors trademark(s), if any, upon this webpage is solely to identify D. Richard Hipp, SQLite contributors goods or services and not for commercial purposes.
- 1
- 2
- 3
All Checks are Passing
3 Passing Tests
Deployment Method: Individual Install, Upgrade, & Uninstall
To install SQLite Analyzer, run the following command from the command line or from PowerShell:
To upgrade SQLite Analyzer, run the following command from the command line or from PowerShell:
To uninstall SQLite Analyzer, run the following command from the command line or from PowerShell:
Deployment Method:
This applies to both open source and commercial editions of Chocolatey.
1. Enter Your Internal Repository Url
(this should look similar to https://community.chocolatey.org/api/v2/)
2. Setup Your Environment
1. Ensure you are set for organizational deployment
Please see the organizational deployment guide
2. Get the package into your environment
Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)-
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
-
Open Source
-
Download the package:
Download - Follow manual internalization instructions
-
-
Package Internalizer (C4B)
-
Run: (additional options)
choco download sqlite.analyzer --internalize --version=3.47.0 --source=https://community.chocolatey.org/api/v2/
-
For package and dependencies run:
choco push --source="'INTERNAL REPO URL'"
- Automate package internalization
-
Run: (additional options)
3. Copy Your Script
choco upgrade sqlite.analyzer -y --source="'INTERNAL REPO URL'" --version="'3.47.0'" [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 sqlite.analyzer -y --source="'INTERNAL REPO URL'" --version="'3.47.0'"
$exitCode = $LASTEXITCODE
Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
Exit 0
}
Exit $exitCode
- name: Install sqlite.analyzer
win_chocolatey:
name: sqlite.analyzer
version: '3.47.0'
source: INTERNAL REPO URL
state: present
See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
chocolatey_package 'sqlite.analyzer' do
action :install
source 'INTERNAL REPO URL'
version '3.47.0'
end
See docs at https://docs.chef.io/resource_chocolatey_package.html.
cChocoPackageInstaller sqlite.analyzer
{
Name = "sqlite.analyzer"
Version = "3.47.0"
Source = "INTERNAL REPO URL"
}
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
package { 'sqlite.analyzer':
ensure => '3.47.0',
provider => 'chocolatey',
source => 'INTERNAL REPO URL',
}
Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.
4. If applicable - Chocolatey configuration/installation
See infrastructure management matrix for Chocolatey configuration elements and examples.
This package was approved as a trusted package on 22 Oct 2024.
SQLite Analyzer is a command-line utility program that measures and displays how much and how efficiently space is used
by individual tables and indexes with an SQLite database file.
The sqlite3_analyzer.exe
binary is a command-line utility program that measures and displays how much and how
efficiently space is used by individual tables and indexes with an SQLite database file. Example usage:
sqlite3_analyzer database.sqlite
The output is a human-readable ASCII text report that provides information on the space utilization of the database
file. The report is intended to be self-explanatory, though there is some additional explanation of the various
parameters reported toward the end of the report.
The output is also valid SQL. Most of the report text is contained within a header comment, with various SQL statements
that create and initialize a database at the end of the report.
The constructed database contains the raw data from which the report was extracted. Hence the original report can be
read into an instance of the command-line shell and then the raw data can be queried to dig deeper into the space
utilization of a particular database file.
Notes
The
sqlite3_analyzer.exe
program is a TCL program that uses the dbstat virtual table
to gather information about the database file and then format that information neatly.Current versions of sqlite analyzer provide 64-bit support only - for a 32-bit version use sqlite.analyzer 3.43.2.
choco install sqlite.analyzer --version 3.43.2 choco pin add -n=sqlite.analyzer --version 3.43.2
This package is automatically updated using the Chocolatey Automatic Package Update Model (AU).
If you find it is out of date by more than a day or two, please contact the maintainer(s) and let them know the package is no longer updating correctly.
SQLite Is Public Domain
All of the code and documentation in SQLite has been dedicated to the public
domain by the authors. All code authors, and representatives of the companies
they work for, have signed affidavits dedicating their contributions to the
public domain and originals of those signed affidavits are stored in a
firesafe at the main offices of Hwaci. Anyone is free to copy, modify,
publish, use, compile, sell, or distribute the original SQLite code, either in
source code form or as a compiled binary, for any purpose, commercial or
non-commercial, and by any means.
The previous paragraph applies to the deliverable code and documentation in
SQLite - those parts of the SQLite library that you actually bundle and ship
with a larger application. Some scripts used as part of the build process (for
example the "configure" scripts generated by autoconf) might fall under other
open-source licenses. Nothing from these build scripts ever reaches the final
deliverable SQLite library, however, and so the licenses associated with those
scripts should not be a factor in assessing your rights to copy and use the
SQLite library.
All of the deliverable code in SQLite has been written from scratch. No code
has been taken from other projects or from the open internet. Every line of
code can be traced back to its original author, and all of those authors have
public domain dedications on file. So the SQLite code base is clean and is
uncontaminated with licensed code from other projects.
Open-Source, not Open-Contribution
SQLite is open-source, meaning that you can make as many copies of it as you
want and do whatever you want with those copies, without limitation. But
SQLite is not open-contribution. In order to keep SQLite in the public domain
and ensure that the code does not become contaminated with proprietary or
licensed content, the project does not accept patches from unknown persons.
All of the code in SQLite is original, having been written specifically for use
by SQLite. No code has been copied from unknown sources on the internet.
Warranty of Title
SQLite is in the public domain and does not require a license. Even so, some
organizations want legal proof of their right to use SQLite. Circumstances
where this occurs include the following:
* Your company desires indemnity against claims of copyright infringement.
* You are using SQLite in a jurisdiction that does not recognize the public
domain.
* You are using SQLite in a jurisdiction that does not recognize the right
of an author to dedicate their work to the public domain.
* You want to hold a tangible legal document as evidence that you have the
legal right to use and distribute SQLite.
* Your legal department tells you that you have to purchase a license.
If any of the above circumstances apply to you, Hwaci, the company that employs
all the developers of SQLite, will sell you a Warranty of Title for SQLite. A
Warranty of Title is a legal document that asserts that the claimed authors of
SQLite are the true authors, and that the authors have the legal right to
dedicate the SQLite to the public domain, and that Hwaci will vigorously defend
against challenges to those claims. All proceeds from the sale of SQLite
Warranties of Title are used to fund continuing improvement and support of
SQLite.
Contributed Code
In order to keep SQLite completely free and unencumbered by copyright, the
project does not accept patches. If you would like to make a suggested change,
and include a patch as a proof-of-concept, that would be great. However please
do not be offended if we rewrite your patch from scratch.
VERIFICATION
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.
The application has been downloaded from the official distribution and can
be verified by:
1. Go to the binary distribution page
https://sqlite.org/download.html
and download the archive sqlite-tools-win-x64-3470000.zip using the link in
the Precompiled Binaries for Windows section.
Alternatively the archives can be downloaded directly from
https://sqlite.org/2021/sqlite-tools-win-x64-3470000.zip
2. Extract the file sqlite3.exe from the archive
3. The executable can be validated by comparing checksums
- Use powershell function 'Get-Filehash' - Get-Filehash -algorithm sha256 sqlite3.exe
- Use chocolatey utility 'checksum.exe' - checksum -t sha256 -f sqlite3_analyzer.exe
File: sqlite3_analyzer.exe
ChecksumType: sha256
Checksum: 5565192EA27443394625895E05F767D0E19B8844CD6BC64CD5954616A57C5413
Contents of file LICENSE.txt is obtained from http://www.sqlite.org/copyright.html
$ErrorActionPreference = 'Stop'
$toolsDir = Split-Path -parent $MyInvocation.MyCommand.Definition
$executable = Get-ChildItem -Path $toolsDir 'sqlite?_analyzer.exe' -Recurse
Uninstall-BinFile -Name $executable.Name -Path $executable
md5: 596912A65B1631ADFB1119688491AB2C | sha1: BB8D0285ED69FDC30438122C911174B275F86FDF | sha256: 5565192EA27443394625895E05F767D0E19B8844CD6BC64CD5954616A57C5413 | sha512: EA9F735123957AF8D6FA3042E43939AA079AA51992A46589B1B3D0A80DAF1595E4DF8710203977E3E7374CA2FA37E438C9BE2CA601FA538C62F833352B15A0C3
Log in or click on link to see number of positives.
- sqlite3_analyzer.exe (5565192ea274) - ## / 73
- sqlite.analyzer.3.47.0.nupkg (80eb6723ec22) - ## / 67
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 |
---|---|---|---|---|
SQLite Analyzer 3.47.2 | 31 | Sunday, December 8, 2024 | Approved | |
SQLite Analyzer 3.47.1 | 51 | Tuesday, November 26, 2024 | Approved | |
SQLite Analyzer 3.47.0 | 65 | Tuesday, October 22, 2024 | Approved | |
SQLite Analyzer 3.46.1 | 108 | Wednesday, August 14, 2024 | Approved | |
SQLite Analyzer 3.46.0 | 142 | Friday, May 24, 2024 | Approved | |
SQLite Analyzer 3.45.3 | 45 | Tuesday, May 21, 2024 | Approved | |
SQLite Analyzer 3.43.2 | 260 | Wednesday, October 11, 2023 | Approved | |
SQLite Analyzer 3.43.1 | 123 | Tuesday, September 12, 2023 | Approved | |
SQLite Analyzer 3.43.0 | 125 | Friday, August 25, 2023 | Approved | |
SQLite Analyzer 3.42.0 | 214 | Wednesday, May 17, 2023 | Approved | |
SQLite Analyzer 3.41.2 | 174 | Thursday, March 23, 2023 | Approved | |
SQLite Analyzer 3.41.1 | 101 | Sunday, March 12, 2023 | Approved | |
SQLite Analyzer 3.41.0 | 123 | Wednesday, February 22, 2023 | Approved | |
SQLite Analyzer 3.40.1 | 157 | Thursday, December 29, 2022 | Approved | |
SQLite Analyzer 3.40.0 | 140 | Thursday, November 17, 2022 | Approved | |
SQLite Analyzer 3.39.4 | 213 | Friday, September 30, 2022 | Approved | |
SQLite Analyzer 3.39.3 | 130 | Monday, September 5, 2022 | Approved | |
SQLite Analyzer 3.39.2 | 141 | Friday, July 22, 2022 | Approved | |
SQLite Analyzer 3.39.1 | 109 | Thursday, July 14, 2022 | Approved | |
SQLite Analyzer 3.39.0 | 126 | Sunday, June 26, 2022 | Approved | |
SQLite Analyzer 3.38.5 | 152 | Saturday, May 7, 2022 | Approved | |
SQLite Analyzer 3.38.4 | 89 | Thursday, May 5, 2022 | Approved | |
SQLite Analyzer 3.38.3 | 109 | Friday, April 29, 2022 | Approved | |
SQLite Analyzer 3.38.2 | 155 | Sunday, March 27, 2022 | Approved | |
SQLite Analyzer 3.38.1 | 135 | Sunday, March 13, 2022 | Approved | |
SQLite Analyzer 3.38.0 | 182 | Wednesday, February 23, 2022 | Approved | |
SQLite Analyzer 3.37.2 | 188 | Friday, January 7, 2022 | Approved | |
SQLite Analyzer 3.37.1 | 70 | Friday, December 31, 2021 | Approved | |
SQLite Analyzer 3.37.0 | 148 | Sunday, November 28, 2021 | Approved | |
SQLite Analyzer 3.36.0 | 254 | Saturday, June 19, 2021 | Approved | |
SQLite Analyzer 3.35.5 | 188 | Tuesday, April 20, 2021 | Approved | |
SQLite Analyzer 3.35.4 | 133 | Wednesday, April 14, 2021 | Approved | |
SQLite Analyzer 3.35.3 | 93 | Wednesday, April 14, 2021 | Approved | |
SQLite Analyzer 3.10.1 | 1691 | Thursday, January 14, 2016 | Approved | |
SQLite Analyzer 3.10.0 | 412 | Wednesday, January 6, 2016 | Approved | |
SQLite Analyzer 3.9.2 | 514 | Monday, November 2, 2015 | Approved | |
SQLite Analyzer 3.9.1 | 517 | Friday, October 16, 2015 | Approved | |
SQLite Analyzer 3.9.0 | 478 | Wednesday, October 14, 2015 | Approved | |
SQLite Analyzer 3.8.11.1 | 537 | Wednesday, July 29, 2015 | Approved | |
SQLite Analyzer 3.8.11 | 470 | Monday, July 27, 2015 | Approved | |
SQLite Analyzer 3.8.10.2 | 508 | Thursday, May 21, 2015 | Approved | |
SQLite Analyzer 3.8.10.1 | 501 | Sunday, May 10, 2015 | Approved | |
SQLite Analyzer 3.8.10 | 473 | Saturday, May 9, 2015 | Approved | |
SQLite Analyzer 3.8.9 | 513 | Thursday, April 9, 2015 | Approved | |
SQLite Analyzer 3.8.8.3 | 495 | Friday, February 27, 2015 | Approved | |
SQLite Analyzer 3.8.8.2 | 555 | Sunday, February 1, 2015 | Approved | |
SQLite Analyzer 3.8.8.1 | 516 | Wednesday, January 21, 2015 | Approved | |
SQLite Analyzer 3.8.8 | 492 | Saturday, January 17, 2015 | Approved | |
SQLite Analyzer 3.8.7.4 | 543 | Thursday, December 11, 2014 | Approved | |
SQLite Analyzer 3.8.7.3 | 505 | Sunday, December 7, 2014 | Approved | |
SQLite Analyzer 3.8.7.2 | 530 | Wednesday, November 19, 2014 | Approved | |
SQLite Analyzer 3.8.7.1 | 561 | Thursday, October 30, 2014 | Approved | |
SQLite Analyzer 3.8.7 | 538 | Saturday, October 18, 2014 | Approved | |
SQLite Analyzer 3.8.6 | 615 | Saturday, August 16, 2014 | Approved | |
SQLite.analyzer 3.8.5 | 525 | Thursday, June 5, 2014 | Approved | |
SQLite.analyzer 3.8.4.3 | 557 | Friday, April 4, 2014 | Approved | |
SQLite.analyzer 3.8.4.2 | 549 | Thursday, March 27, 2014 | Approved | |
SQLite.analyzer 3.8.4.1 | 512 | Wednesday, March 12, 2014 | Approved | |
SQLite.analyzer 3.8.4 | 525 | Tuesday, March 11, 2014 | Approved | |
SQLite.analyzer 3.8.3.1 | 564 | Wednesday, February 12, 2014 | Approved | |
SQLite.analyzer 3.8.3 | 489 | Tuesday, February 4, 2014 | Approved | |
SQLite.analyzer 3.8.2 | 547 | Saturday, December 7, 2013 | Approved | |
SQLite.analyzer 3.8.1 | 553 | Friday, October 18, 2013 | Approved | |
SQLite.analyzer 3.8.0.2 | 590 | Tuesday, September 10, 2013 | Approved | |
SQLite.analyzer 3.7.17.20130622 | 552 | Saturday, June 22, 2013 | Approved | |
SQLite.analyzer 3.7.17 | 548 | Saturday, June 22, 2013 | Approved | |
SQLite.analyzer 3.7.11.0 | 627 | Wednesday, April 11, 2012 | Approved | |
SQLite.analyzer 3.7.10.0 | 558 | Sunday, January 22, 2012 | Approved | |
SQLite.analyzer 3.7.8.0 | 606 | Monday, October 3, 2011 | Approved |
None - SQLite Analyzer is dedicated to the public domain
This package has no dependencies.
Ground Rules:
- This discussion is only about SQLite Analyzer and the SQLite Analyzer 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 SQLite Analyzer, 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.