I've seen that a lot. When I import Drupal databases, I learnt to use its Backup and Migrate module instead, it works flawlessly. Downside is you need to do clean Drupal installation first, but that basically is just creating blank database and putting brick on enter key.

@scottalanmiller

Did you ever solve this problem? Just wondering what you solution was if you did.

@Obsolesce said in UREs Strike InnoDB on MySQL:

@scottalanmiller said in UREs Strike InnoDB on MySQL:

@Pete-S said in UREs Strike InnoDB on MySQL:

Step one is to remove the drives and clone them with dd or recovery tool to a new drive.
You could probably recover 99.9% of the data - if you want.

As you can guess from all of their previous issues, they don't want to pay for any recovery, they just want it magically fixed for free. They don't own any storage onto which to clone it, either.

Then what is the point of any of it? It appears to have zero value to the business.

I said that to them.

@dafyre said in PATH Error with TimeScaleDB-Tune on Fedora 30:

then why are you even using it?

Capacity Planning, for example.

@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!

@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...

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

@tonyshowoff said in MS SQL Server 2017 on Linux Has Released:

Does it allow odd number processors yet or do I still have to disable one if I don't have an even number?

Even only for licensing, I believe. No change there.

@fuznutz04 said in MySQL configuration best practices:

@emad-r

What is your practice for log rotation? For example, the error log. If that grows (obviously indicating other issues) , and needs to be rotated, what procedure do you use to rotate logs?

Currently the third party vendor uses this:

expire_logs_days = 10
max_binlog_size = 100M

In our MySQL instance.

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

You will often hear or see the term RDBMS or Relational Database Management System. This term refers to a subset of DBMS, not an alternative, and is specific to those DBMS that handle relational database formats. The term SQL is often incorrectly applied to these, but SQL is a language and relational databases are a mathematical model. While the two have a relationship (no pun intended) they are different things completely and are not directly tied together. Today, what is and is not an RDBMS is increasingly unclear as nearly all DBMS have some relational element and even the most traditional RDBMS stalwarts have begun to add non-relational engines or options.

@scottalanmiller said in Why Does Everyone Still Focus on Relational Databases?:

I just built out a NoSQL ElasticSearch three node cluster in the lab. Whoo!

The perfect DB setup for storing a hit counter for the number of times I've watched Tombstone!

https://channel9.msdn.com/Shows/Data-Exposed/SQL-Server-on-Linux-Sneak-Peak

They work very differently too. MySQL's features vary significantly based on which engine is in use. They perform differently, have different relational abilities, store differently on disk (MyISAM is one file per table, InnoDB is one file for everything) and use different tools.