I've done both. I tend to like MariaDB / MySQL better because that is what I'm more comfy with.

So, easy fix, the ca_stag2 was a staging DB that was not needed and was not current. The whole thing appears to have corrupted. So I simply "moved" that entire directory to /tmp (just in case I had to put it back) and then MySQL could fire up.

@matteo-nunziati said in Performance Advantages to Splitting Applications from Databases: @gtech yeah the only reason is saturation of resources and scaling out. rdbs do not scale out easily while front ends do. And RDBMSs tend to scale better vertically (throwing more RAM and CPU in a box) while app servers tend to scale better horizontally (throwing more, smaller boxes at it.)

@WrCombs said in Database Server vs File Server: What's Different: @scottalanmiller said in Database Server vs File Server: What's Different: @WrCombs said in Database Server vs File Server: What's Different: Is it possible for a File server to run a database server ? how would that be classified at that point ? No, conceptually that would not mean anything. A file server and a database server are discrete concepts. A single operating system can run neither, either, or both. But as servers themselves, they are discrete. I gotcha. It was one of those hypothetical questions What's messy is that technical file servers are a very, very specific form of database server. Because a file server presents a file system over a network. And a file system is a special case database. No one really thinks about this and absolutely no one will talk about file servers this way, but for understanding what is actually happening... file servers are special purpose database servers. And that is very easy to prove. So a file server is a database server, but a database server is not a file server. But file servers are so common, unique, and discrete, we treat them as totally different animals and no one considers the two to even be similar.

@black3dynamite said in Setting Up a Standard MySQL or MariaDB Database for an Application: @JaredBusch said in Setting Up a Standard MySQL or MariaDB Database for an Application: I like my approach to setting this up. Obviously, install MySQL/MariaDB first as noted above. Then do the following. This all needs done in the same SSH session, but otherwise things are simple. Choose once of these exports for your DB root password. The first one is for you to specify, the second generates a random one and echo's it back to you. # Specify your own password for MariaDB root user export DB_ROOT_PASS="somebigpasswordgoeshere" # Generate a random password for MariaDB root user export DB_ROOT_PASS="$(head /dev/urandom | tr -dc A-Za-z0-9 | head -c 30)" echo "This is your MariaDB root password: $DB_ROOT_PASS" Specify the application database name and application user name # Database user to use for application export DB_USER='yourusername' # Database name to use for application export DB_NAME='yourdatabasename' Generate or specify a random password for the database user # Specify your own password for the application's database user export DB_PASS="somebigpasswordgoeshere" # Generate a random password for the application's database user export DB_PASS="$(head /dev/urandom | tr -dc A-Za-z0-9 | head -c 30)" echo "This is your password for the application user: $DB_PASS" Then create the application database, use, and grant access. mysql -e "CREATE DATABASE $DB_NAME;" mysql -e "CREATE USER '$DB_USER'@'localhost' IDENTIFIED BY '$DB_PASS';" mysql -e "GRANT ALL ON $DB_NAME.* TO '$DB_USER'@'localhost';" mysql -e "FLUSH PRIVILEGES;" Finally, lock down the system without the interactive requirement of mysql_secure_installation # Secure MariaDB (this does what mysql_secure_installation performs without interaction) mysql -e "UPDATE mysql.user SET Password=PASSWORD('$DB_ROOT_PASS') WHERE User='root';" mysql -e "DELETE FROM mysql.user WHERE User='root' AND Host NOT IN ('localhost', '127.0.0.1', '::1');" mysql -e "DELETE FROM mysql.user WHERE User='';" # Beginning on some version of MariaDB after Fedora 29 was released, the test DB is no longer there by defualt. mysql -e "DROP DATABASE test;" mysql -e "FLUSH PRIVILEGES;" Your approach makes it easier to use as part of a script. It also generates random passwords, which I prefer.

@Dashrender said in Make an osTicket Database Backup: Total DB Admin noob here - so bare with me. Does this include the username/password setup for this DB? or does that need to be maintained separately? i.e. you have to rebuild from this backup - do you just create a brand new SQL user and grant them rights to this DB upon import, then use that new account to give access to the app? In typing out my question I kinda assume the answer is the second bit - you just create a new user and assign them rights. Correct. The user and the database are separate things.

@pmoncho said in Slow MS SQL Queries between Windows 10 VMs and MS SQL 2014 on same host: @JasGot said in Slow MS SQL Queries between Windows 10 VMs and MS SQL 2014 on same host: Winner Winner, Chicken Dinner. It was MDTC and Windows Firewall. (Which is frustrating, because the firewall is turned off for the domain!) Good job at troubleshooting. I'm wondering what led you down this path versus something related to Networking, hard drives or software drivers? Remembered it from several years ago with another SQL based application. Don't know what made me think of it at 1:30am. But I'm ok with it!

@Emad-R said in Installing MS SQL Server Express on CentOS: Et me guess it is much faster on Linux than on Windows server No idea, but it is one less Windows Server license needed. Also MS SQL Server Express works well for many tasks.

So, circling back. How is the backup project going?

I will Download this To my laptop later and give it a try with a File from the lab here and let you know.

@magicmarker Why dont they create one giant hazardous label to fit all the products, and make it generic as possible. Like this product contains hazardous chemicals. it is not like someone actual reads that small fine print. Another problem solved...

@StorageNinja said in MongoDB Major Change to Licensing: @scottalanmiller said in MongoDB Major Change to Licensing: if you are a SaaS vendor looking at building software that uses MongoDB somewhere, you'd better get a lawyer looking over this license and how it applies to you. This is becoming a bigger issue as the biggest SaaS vendors hide behind this clause more and more with incredibly proprietary forks. They offer very little to no actual core development or contribution and it goes against the previous method of GPL code getting funding. It annoys me, as the legal headaches of contributing internal only use code back will block some companies from using OSS, but I see it both ways. The startups who are doing a lot of the core housekeeping of NOSQL platforms are learning they can't find a business model. This is getting messier and messier. Partially because there are just too any vendors involved. What's amazing, though, is that a move like this took a customer who was very into MongoDB and using it in projects and was literally working with MongoDB's own hosted product and now looking to avoid it like the plague. So at least in this one case, they are likely losing hosted product from this. And gaining nothing. I imagine a lot of customers going through this same process.

If you want to exit the SQLite command line shell, the command is dot exit... .exit

@jaredbusch said in MongoDB Storage Engine Error Detected MMapV1 and wiredTiger: @scottalanmiller okay, they totally fucked this up. Yeah, this is some weird stuff.

@jaredbusch said in MS SQL Server Best Practice Guide on Scale HC3: You actually get your SMB clients to plan ahead? /gasp! We try!

@oksana Still backups are needed

Just installed on CentOS 7.6 with XFS. Still flawless install.

We have plans to add an in memory database to ML in the future when more performance is needed, as well.

Oh that's funny and interesting! Might I ask what sort of work so I can see a little bit about what is done?

If you were looking for a de facto direct replacement to MS SQL Server and just didn't want to have to "think" much about anything, the obvious choice is PostgreSQL.  It is one of the world's most powerful, mature and respected database platforms.  It is insanely fast, scales insanely big, is supported on the most enterprise style deployments, does relational the same way that MS SQL Server does and so forth.  It is the most direct competitor.  And you have loads of top end support options for it.  So if you want a safe "starting point", start there.  It's hard to go really wrong.  But best to do an evaluation of needs as there are just so many great options

@WLS-ITGuy said in MySQL to PostgreSQL conversion: Well, that was a thread that will fizzle out quickly Thanks for the assist all. LOL, sometimes that's exactly what you want. This would have been a large, horrible project. Now it's a simple "Oh good, we are all set"