Exporting a non functional XAMPP database? - mysql

I've been using XAMPP for several local projects.
A few days ago I installed Desktop Server for Wordpress local development.
Little did I realize, I wouldn't be able to open the regular xampp back up...
Now I need to export the databases I've created on xampp without being able to access the old phpmyadmin.
How can I do that?
Thanks!

It sounds like you have two MySQL instances on your machine. If one is using the MySQL networking port (3306), the other won't be able to start, which is consistent with what you're describing.
If you stop the one (from Desktop Server) then manually start the other one (in XAMPP, which you should be able to do from the XAMPP control panel), you can then connect to it and export your database.
You can't safely merge the two database data directories, but in theory if you completely stop both MySQL instances — and back everything up — you should be able to completely replace one datadir with the other. I don't generally advise this, because the possibility also exists to lose your data.

Related

How do I migrate a SQLAnywhere 9 db running in a remote server into a mysql server on my machine?

I am working at a company that has some CRM software running in a remote Windows XP server that uses a SQLAnywhere 9 db to store its data; I have access to this remote server with an administrator account.
I would like to extract the db into a .sql file so that I can run the db locally on my machine without affecting the running db in the server (since it is key for the company's day to day operation).
The reason I need this is that we are going to test some BI Software and we need data from this database to test it, but we don't know the structure of the database since the developers of the CRM software didn't give us any documentation on it. So we need to have the database locally so that, without affecting the running CRM, we can:
understand the structure by looking at the DDL
make queries to it to get sample data
I researched a bit, and the most common solution to my problem was to use dbunload on the remote server to unload the db into a reload.sql file that contained what I needed. But most tutorials on the subject mention that I have to stop the db first (which would be catastrophic). If this is the only option, then I guess I am willing to do it on the weekend when the CRM is not used, but I wanted to know if there was another solution first.
If there is no other solution, can you point me to where I can find the proper and safer way to do this?
I have researched a lot, but prior to this day I have never even heard of SQLAnywhere, so I really need all the help I can get. My main concern is doing something that impacts negatively the CRM software.
Thank you.
You can run dbunload across the network, you just have to tell it to do an "external" unload. The default is to do an internal unload which would only work from the machine where the database server is running.
I don't have SQL Anywhere 9 documentation right now to look up the exact switch, but dbunload -? should show you all the possible switches.
Edit:
-an will create a new database and load the data and schema from another data
-xi switch will do external unload and internal reload.
-c parameters to connect to your remote database

Is There A Difference Between WAMP and MYSQL

This is my first post on Stack overlow
I'm a computer Engineer, but i'm relatively New to MYSQL
also i love using CLI
Backround info :
I Initially Installed MYSQL on my computer on IIS7 Virtual Server
Then Seperately installed PHP My Admin
when i did that it installed components such as MYSQL Workbench and Connectors and so on
i like the installed components but didn't use them frequently,
i only found myself using the Console and the Workbench
Now. the workbench has been replaced by PHP MyAdmin
at that time my database had only a few entries
after more research i learnt about WAMP, LAMP etc..
I'm now using the WAMP Stack
MY QUESTION IS THIS..
Other than the obvious fact that WAMP Uses Apache and i was using IIS7
is there any real difference between installing WAMP as a package
or installing all the components seperately
i would think not, but, what i did notice before i installed WAMP, was that i was always having to alter directory locations to enable new features
i find in WAMP that i'm doing that so much
In Giving me an answer
i would like it to be considered that ..
- I'm pretty much doing standard Data entry
- Running Queries
- i would like to have the ability to Backup the data file locations without any issues
- i would like to have the ability to Import and Export a table to another table if i see fit
eg.
if i created a table in a database called (for example) stock_my
and then i populated that with about 100 entries for example
and then i decided to rename the table my_stock
i would like to be able to export the data from stock_my to a .sql file
and then to be able to Import the data to the new table
Lastly , i would like Upgrading to newer versions of MySql or PHP My Admin to be relatively painless
THAT'S IT
SORRY ABOUT THE LONG POST
Any Comments are appreciated ahead of time
and i'd like to say , it's a pleasure to NOW be part of the community
sincerely
Martin Kuliza
The only difference is that Wamp installs those products already configured to work together and tuned up for a development environment, which means putting minimal footprint on your computer resources so you can work normally in the same machine you have the servers installed.
Installing them separately would only mean you would have to configure all that yourself, but essentually you would be installing the same things.

Move native phpmyadmin databases to xampp

After a computer crash (Mac OSX Update), I was able to recover my files from a back up. In order to make things easier on me in the future, I decided to move to XAMPP instead of using the native PHPMyAdmin and MySQL. I know where PHPMyAdmin was pointing before - how do I move the files so XAMPP can see them?
It's not a recommended means of backing up and restoring, but as long as there's nothing in the XAMPP databases you might just be able to replace the XAMPP data directory with the backup from your old MySQL one. Note that XAMPP may have "important stuff" in the database by default; I don't use it so I have no idea. You can also just drop in specific databases (which are represented on disk by files or folders of similar name), but will have to recreate permissions and users for those.
It's better to do SQL exports and imports for backing up your data.

Can I run my own instance of MySQL?

I'm trying to migrate a web site to friend's server. The site uses MySQL, but he didn't previously have it set up. He's installed the package now and suggested that I could run my own instance of it. I'm at a loss for how to do so. Is it even possible? If so, how?
Some relevant information:
The OS in use is CentOS 5.9
Using MySQL 5.0.95
I only need the DB to be read locally via PHP when serving my site.
I have no root privileges on this system (although a full shell), but am close friends with the owner/administrator if that's necessary.
To clarify:
It's the daemon that I want to run my own instance of. So I guess what I want to know is if it's possible to have multiple users on the system running their own instances of mysqld containing different databases.
All I need this for is serving a web page. If I have to break down and switch to a pseudo-database using CSV files I will, but I'd much rather stick to MySQL if I can.
If MYSQL is setup on that machine yes you can run your own instance of it.
You can have it set up and your site given its on Database within that MYSQL instance and that specific MYSQL account can be used to access the tables etc. involved with your website.
Now if he is only putting MYSQL on the machine then having you set everything up you will just need an account for MYSQL and from ther eyou can get in and just create all the needed items that will allow your site to fully function.
EDIT
In response to your comment. You can you just can't clog the same port or have configurations that conflict each other. As long as it won't be to much of a performance hit and you configure a different user to start each instance you should be able to do Something like this.

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