phpmyadmin and speed of my mac - mysql

Really new with the whole phpMyAdmin thing.
I was wondering, when I enable my computer for web sharing, then install phpMyAdmin, is this detrimental to my computer in anyway (mainly in speed)? If so, I would opt for just using another (older) computer. But that would be a hassle.
Thank you in advance.

There are potential security issues depending on your set up and a slight impact on speed since youll be running the webserver and mysql in the background but its nothing huge in terms of performance.
With that said theres no need to use phpmyadmin locally. Its kind of pointless since you can use a real mysql client like Sequel Pro, Navicat, or MySQL Workbench. I prefer Sequel Pro myself since its free and pretty lightweight.

Related

MySQL local network query issue

I work with a software developed in Visual Basic 6 which MySQL is the database. Our application works in a local network and always worked fine, but just one costumer is having an issue. The question is when the consultant does something in our application the MySQL database takes too much time to search or stops to work, but when I'm on the machine that is installed MySQL (5.5) it is working.
I already have tried some tips, changing my.ini file lines, grant all command, reinstallation and etc.
Maybe the problem could be the local network? Any advice?
I have to apologize for my english if something don't look right,
Regards.
Well, I solved my problem, It was easier than I thought.
I had to go in Performance Options from Windows and change the Virtual Memory, just this.

Test a MySQL restore on same server

I've got a third-party application that uses MySQL as a backed. The next version will have support for our backup system, but before we upgrade we would like to take a backup. Catch 22! I am not a DBA, and our DBA staff isn't familiar with MySQL, so I'm pretty much on my own. Our server has lots of space and CPU cycles, so I would like to test the restore on that machine, without overwriting the production data. So my question is, should I install another instance of MySQL on the same computer in a different location, or is there a way to restore my data to an alternate database on the existing server?
If you are not familiar with MySQL. The preferable option would be to install MySQL on another machine, ideally with the same OS and test your restore there. It's free to install and any extra time taken to install MySQL (About 15 minutes with the Wizard) far outweighs the effort it would take to restore your live system if you make a mistake and break it.
If that is not an option and you really do want to restore on the same machine. Then your question has already been answered and voted for on stackoverflow. Multiple MySQL instances on a single machine
Your quite right that a backup isn't worth a tinker's curse unless you know you can restore it.
I would like think I know what I'm doing with a MySQL database, and in theory its possible to test the restore of a MySQL database, but not an entire MySQL instance on an existing machine. But personally I would be doing this very carefully and only as a an absolute last resort. There's just too much to go wrong.
MySQL will run on all sorts of operating systems, and with very little overhead (if you so configure it). Setting up a test machine is so easy, you also need a very good reason not to set up a new instance to test the backup on.

Will exporting a database using MySQL Workbench cause downtime on server?

I am using Workbench to export a database stored on my hoting providers server, will the server experience any downtime whilst I am exporting the data?
The only reason I ask is because when I back up my local SQL database my server needs to be switched offline for it to work.
All comments will be much appreciated.
Ben
No it will not cause a downtime, unless your server has really low resources (in which case you should find a better hosting). Seriously though, nothing bad will happen.
Also I can hardly imagine why you need to disable your localhost for backup... Workbench uses mysqldump for exports and this in turn needs MySQL to be online...

Client Connect MySQL

Is there a client-based internet technology that allows me to connect to a remote MYSQL dataabase without using any server side scripting ?
I know that JavaScript does not allow me, but provided that the user knows the database's password, can it be done on the client side?
Do you just need a MySQL administration client? Something like MySQL Workbench should do the trick, no? If the database is open and available then any MySQL client application should be able to connect to it, including the command-line tools that come with MySQL.
Keep in mind that, in general, it's usually not recommended to expose your database directly to the internet. You'll want to really keep an eye on security if you do this.
If you really want to go with a browser, my first thought is to install a tool like phpMyAdmin on the server and then let your users access to that.
Again, I'll give you the same advice the other gave you: don't. Please, don't. And if you really want to do that, have a safe backup and take all the necessary precautions.

mysql: keeping local mysql database and remote server database synced up

I am kind of a amateur at web development. But it seems like most people develop on their local machines and the upload to their remote servers when everything is ready. I want to start doing this. I've installed Xampp (Apache) on my local machine. But in order for this to really work, i need the the mysql databases that already exist on my remote server to be "synched" or "duplicated" on my local machine. But I'm finding this somewhat hard to figure out.
First, Should I be using mysql "reduplication" feature (with my remote server as master) and local machine as slave? Or is there a better way to do this? Should I be synchronizing instead of reduplicating
Second, Is anyone willing to give me a quick description of how I achieve this "reduplication" or "synchronization"
Thanks
It may be tempting, but it's hopeless to try to keep the database in two places. Instead, always keep the database on the server because it's much easier to develop and debug your code if it's in just one place. "Resynch" and "reduplicate" and all that business is just too much trouble, as you are discovering. The DB is going to end up on the server anyway, so you may as well put it there right now.
Also, you will not need a web server on your local machine, which will unburden you.
This next is applicable if you are writing CGI. If you aren't sure whether or not you are writing CGI, then you are not (well, probably not). {
If you mainain just one database and it lives on your server, you'll be able to write one piece of portable code that will run equally well on your local machine and on your server. This is a huge win, take my word for it.
To get this working, you will need the mysql library on your local machine; no other mysql component is needed there. The mysql server will run on your server only.
Read up on mysql "connector" for the language you're using.
}