I finally found the easy way to get this information directly from Amazon with a couple of clicks.
Log into the RDS management dashboard
Click on "DB Instances"
Click on the instance in which you are interested. That should expand it and show much more info about it.
View the "Monitoring" tab.
There is a "Free Storage Space" graph:
If you do any backups of MySQL Instance it is best to setup MySQL Replicaton so that any impose server load or increase disk I/O does not impact your production database is any way.
Once you setup MySQL Replication, you can script a mysqldump in different ways (Please see my post on the DBA StackExchange for the variety of techniques), as long ...
Note that having this sort of sub-federal jurisdiction above the level of a municipality happens in many countries, not just in the US (e.g Australia, Canada, China, India, Mexico...)
To answer your question, you (modiX) need to understand why one would ask for the state (or province or territory). There are two primary reasons:
If you need to use old-...
It's not necessarily a bad idea, assuming DB server/node/gear/droplet/etc is in the same "cloud" and stays on internal bogon routes. A couple cons that could come into play though, depending on the remote-ness are:
Speed, as in round trip time to contact DB and get a reply back to the app.
Caching, as in how and where will the cache be maintained
There are fringe cases where zip codes can actually cross state lines. Amazingly stupid, but true:
Following trends blindly might be bad UI design but bucking them without a healthy dose of paranoia is a bad idea too.
Morgan Lewis is a law firm with offices in the UK and they have published information (as of 2012 which is the most recent authoritative publication I can find on the subject) on the ICO's guidance on deleting personal data under the DPA 1998.
According to their legal assessment of the guidance the ICO recognized the difficulty in deleting electronic data ...
You do not say what the .sql file is for, however, a .sql file, in of itself, is just plain ol' text and therefore not a threat. Ignore it the notice.
That said, if you do not know what the file is or if ...
According to the Data Protection Act 1998 they do. The exceptions are data used for national security, the detection of crime, and taxation purposes.
The referenced Principle 6 actually doesn't cover the removal of data on the subject's request. However, this contingency is addressed in the Conditions for Processing, as in:
Consent must also be ...
Disclaimer or Terms and Conditions
All sites that obtain personal information should use some kind of disclaimer or terms of conditions on submitting such data to the system, this varies from site to site and you should do a little research on what things you should be mentioning. If its for a big project then I suggest a legal adviser. It's important to ...
You need a Disclaimer - make the users to agree and understand that although you will not misuse their data, but you will not be responsible for anything that may happen to the information that they submitted voluntary.
About "making the data safe", it can't be answered in this question, it's too broad and you need to be more specific.
You have to configure PHPMyAdmin to connect to the MySQL database first. If you go to http://wiki.phpmyadmin.net/pma/Config you'll see that you need to add the following example to your config.inc.php file:
$cfg['Servers'][$i]['host'] = 'localhost'; // MySQL hostname
$cfg['Servers'][$i]['port'] = ''; // MySQL port (leave blank for 3306)
You can export the database information as many text formats like CSV, JSON, TXT, SQL, etc.
But usually databases are more complex than just the information contained there, for instance, there may be dependencies between tables, autoincrement fields, foerign key restrictions, etc. If you just edit the exported text, you may be breaking some of the ...
If MySQL servers we open to the general public like your website it would open them up to brute force attacks, and other remote attacks by bots mostly which they simply don't need to deal with. Most people who know enough that they'll need remote MySQL access should be familiar with setting that up in cPanel etc. It's a matter of security for you, and less ...
whois is a very poorly defined protocol (or more precisely: defined well enough at the moment it went into use, but now clearly outdated and missing key elements needed today, like tiered access and formatted output), with only RFC 3912 covering it (obsoleting RFC 954), which says mostly nothing: you send a query on one line, the server replies with a blob ...
No, it's not good practice to create a database user for every site user. The way you have things setup now is pretty standard. It shouldn't be possible for people to get access to passwords stored in your PHP code unless your server is compromised, and that's pretty much the worst case scenario.
The only caveat is that if you are using some form of source ...
There's no reason that this has to be one way or the other. I would say to optimize both. If you have a large number of images, a CDN makes sense, regardless of what you do on the server. Also, even if that takes care of the problem, better database performance is helpful in general, so I would recommend tackling both options.
I really do love AWS tools. ...
Here is several free relational database service.
"To help new AWS customers get started in the cloud, AWS is introducing a free usage tier. The free tier can be used for anything you want to run in the cloud: launch new applications, test existing applications in the cloud, or simply gain hands-on experience with AWS.
All of PHP's mysql_* functions, including mysql_real_escape_string() have been deprecated, in favour of the mysqli and PDO extensions.
See Deprecated PHP (A blog set up by two StackOverflow members).
Use query binding (SELECT * FROM table WHERE ? with a $condition) and you won't have to use the function you mention.
With a small server, without much power/space for a large database, I think it's a good idea.
Also if you want to keep a clean and active user database you can do this:
warn user about inactivity this XX years/months and tell him that without answer from him in the next weeks, you will remove its account
re-warn him a week before the deletion
without new ...
It will be stored in what ever database you want.
Presumably you have a database that holds the items you are selling, in that case store the customer details in a table in that database.
In fact what you should have is two tables. One to hold the basic customer details (name etc.) and a second for addresses. That way you can have multiple addresses per ...
I would set up a contact form that will send an email each time somebody is interested. Unless you think you will get 10s of these a day, that shouldn't be a horrible solution. My guess is you'll be lucky to get 1 a day.
I wrote a contact form that you can use for such a purpose: http://ostermiller.org/contactform/ I would configure such that preview ...
If you're talking about dedicated servers, then it won't be such a big problem to transfer the database.
You can use SSH in order to transfer it directly from one server to another, without even downloading it. Then you can import it in a new database from the command line pretty fast.
If you don't want to worry about storage and performances, then go for ...
The URLs should be something like www.example.com/?id=XXX. Based on the ID parameter, you can extract the required data from your database and pass it in the response.
I have learned how to retrieve data from a database to a single page
by using a form
I think you are using the POST method in your form, and because of that the parameters will be passed ...
This sounds like you would benefit from a GUI to do this for you... However some one would need to build that for you (assuming you're not a developer).
Exporting to a different format is not advisable in most cases as if your database is relational or has any constrains, then editing without having these rules enforced will likely cause issues and prevent ...
Search engines bots see your final HTML (after the server delivery of your page to the client web browser). Therefore, you can build and customize your pages like you want.
Otherwise, it depends on what you modify compared to the old version of your site. If you modify good SEO spots like <title>, <h1>, <h2>, etc., your SEO can be impacted ...
There is no impact to SEO whether meta information is static HTML or dynamically generated HTML. By the time the search engines see it there is no difference - they look at the meta content itself and not the technology behind it.
If managing the meta information in a database helps you to ensure it is kept relevant, up-to-date and accurate then obviously ...