2 added 238 characters in body
source | link

Seems like a trivial question, but I couldn't find other questions that address the following.

So I'm simply asking, how strong would my (super user) database credentials ideally be? I simply figured out, that since all of my connections are done through my app server script files, why shouldn't I just generate a random 40 letters string and use it hard-coded in my script files as a password? The only backside is that if it gets lost somehow then I'll be left with no access to my db. However, it is an option and since I've never seen anyone else mentions it, what is your opinions about it? And if it's not a wise decision, how strong should my db password be?

And if I use 3 database servers, where 2 of them are simply backups, would I, as best practice, remember the credentials of them all? Using the same password seems dangerous if my concern is hackers. How do big companies deal with it?

Seems like a trivial question, but I couldn't find other questions that address the following.

So I'm simply asking, how strong would my (super user) database credentials ideally be? I simply figured out, that since all of my connections are done through my app server script files, why shouldn't I just generate a random 40 letters string and use it hard-coded in my script files as a password? The only backside is that if it gets lost somehow then I'll be left with no access to my db. However, it is an option and since I've never seen anyone else mentions it, what is your opinions about it? And if it's not a wise decision, how strong should my db password be?

Seems like a trivial question, but I couldn't find other questions that address the following.

So I'm simply asking, how strong would my (super user) database credentials ideally be? I simply figured out, that since all of my connections are done through my app server script files, why shouldn't I just generate a random 40 letters string and use it hard-coded in my script files as a password? The only backside is that if it gets lost somehow then I'll be left with no access to my db. However, it is an option and since I've never seen anyone else mentions it, what is your opinions about it? And if it's not a wise decision, how strong should my db password be?

And if I use 3 database servers, where 2 of them are simply backups, would I, as best practice, remember the credentials of them all? Using the same password seems dangerous if my concern is hackers. How do big companies deal with it?

1
source | link

How strong should a database password be?

Seems like a trivial question, but I couldn't find other questions that address the following.

So I'm simply asking, how strong would my (super user) database credentials ideally be? I simply figured out, that since all of my connections are done through my app server script files, why shouldn't I just generate a random 40 letters string and use it hard-coded in my script files as a password? The only backside is that if it gets lost somehow then I'll be left with no access to my db. However, it is an option and since I've never seen anyone else mentions it, what is your opinions about it? And if it's not a wise decision, how strong should my db password be?