sql-server-maintenance-solution
litestream
sql-server-maintenance-solution | litestream | |
---|---|---|
47 | 165 | |
2,763 | 10,026 | |
- | - | |
0.0 | 7.5 | |
14 days ago | 17 days ago | |
TSQL | Go | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
sql-server-maintenance-solution
- Rookie dba questions on maintenance
-
What are your SQL server best practices that you live by?
100% this. Separating tempdb has a huge impact, and Ola’s scripts are a must, for anyone who doesn’t know: https://ola.hallengren.com
-
Securing SQL Standard 2019 server
Since you are new to SQL - https://ola.hallengren.com/ and http://whoisactive.com/downloads/ + https://www.sqlshack.com/monitoring-activities-using-sp_whoisactive-in-sql-server/ will make your SQL experience night and day. Learn these SPs/Tooling.
-
Windows environmental variables and maintenance plans
First, don't use maintenance plans. Full Stop. Use Ola Hallengren's Maintenance Solution or Minion Backup. dbatools even has a way to install and schedule Ola's jobs, including backups. Quick and easy.
-
To create a custom text log file using MS SQL server
Instead of trying to reinvent the wheel look at https://ola.hallengren.com/
-
Slow SCCM Server and Console Performance
Great advise. I tend to use this for SQL: https://ola.hallengren.com
-
Sccm, Wsus pros.
Ya I use https://ola.hallengren.com for my DB maintenance. I typically have to fix existing non maintained WSUS / SUSDB Sups. I found one the other day with about 20K updates lol
-
Automatic backup to Azure blob
Install Ola Hallengren's Maintenance Solution and schedule the Agent jobs to run the backups when you need them (and make sure you understand the difference between FULL, LOG and DIFF backups, and when you should use each). Configure it with the URL for your Azure Blob Storage. You will also need to create a Credential for SQL Server to use to authenticate to Azure Blob Storage.
-
Hired in to "fix" SCCM. Their build is running without issue (albeit fairly slow) but is quite messy. Where would you start looking to make improvements?
SQL Server database maintenance. You don't need to be a SQL expert - just set it and forget it with this: https://ola.hallengren.com/
litestream
-
Ask HN: SQLite in Production?
I have not, but I keep meaning to collate everything I've learned into a set of useful defaults just to remind myself what settings I should be enabling and why.
Regarding Litestream, I learned pretty much all I know from their documentation: https://litestream.io/
-
How (and why) to run SQLite in production
This presentation is focused on the use-case of vertically scaling a single server and driving everything through that app server, which is running SQLite embedded within your application process.
This is the sweet-spot for SQLite applications, but there have been explorations and advances to running SQLite across a network of app servers. LiteFS (https://fly.io/docs/litefs/), the sibling to Litestream for backups (https://litestream.io), is aimed at precisely this use-case. Similarly, Turso (https://turso.tech) is a new-ish managed database company for running SQLite in a more traditional client-server distribution.
-
SQLite3 Replication: A Wizard's Guide🧙🏽
This post intends to help you setup replication for SQLite using Litestream.
-
Ask HN: Time travel" into a SQLite database using the WAL files?
I've been messing around with litestream. It is so cool. And, I either found a bug in the -timestamp switch or don't understand it correctly.
What I want to do is time travel into my sqlite database. I'm trying to do some forensics on why my web service returned the wrong data during a production event. Unfortunately, after the event, someone deleted records from the database and I'm unsure what the data looked like and am having trouble recreating the production issue.
Litestream has this great switch: -timestamp. If you use it (AFAICT) you can time travel into your database and go back to the database state at that moment. However, it does not seem to work as I expect it to:
https://github.com/benbjohnson/litestream/issues/564
I have the entirety of the sqlite database from the production event as well. Is there a way I could cycle through the WAL files and restore the database to the point in time before the records I need were deleted?
Will someone take sqlite and compile it into the browser using WASM so I can drag a sqlite database and WAL files into it and then using a timeline slider see all the states of the database over time? :)
-
Ask HN: Are you using SQLite and Litestream in production?
We're using SQLite in production very heavily with millions of databases and fairly high operations throughput.
But we did run into some scariness around trying to use Litestream that put me off it for the time being. Litestream is really cool but it is also very much a cool hack and the risk of database corruption issues feels very real.
The scariness I ran into was related to this issue https://github.com/benbjohnson/litestream/issues/510
-
Pocketbase: Open-source back end in 1 file
Litestream is a library that allows you to easily create backups. You can probably just do analytic queries on the backup data and reduce load on your server.
https://litestream.io/
- Litestream – Disaster recovery and continuous replication for SQLite
- Litestream: Replicated SQLite with no main and little cost
-
Why you should probably be using SQLite
One possible strategy is to have one directory/file per customer which is one SQLite file. But then as the user logs in, you have to look up first what database they should be connected to.
OR somehow derive it from the user ID/username. Keeping all the customer databases in a single directory/disk and then constantly "lite streaming" to S3.
Because each user is isolated, they'll be writing to their own database. But migrations would be a pain. They will have to be rolled out to each database separately.
One upside is, you can give users the ability to take their data with them, any time. It is just a single file.
[0]. https://litestream.io/
-
Monitor your Websites and Apps using Uptime Kuma
Upstream Kuma uses a local SQLite database to store account data, configuration for services to monitor, notification settings, and more. To make sure that our data is available across redeploys, we will bundle Uptime Kuma with Litestream, a project that implements streaming replication for SQLite databases to a remote object storage provider. Effectively, this allows us to treat the local SQLite database as if it were securely stored in a remote database.