New answers tagged windows
On Win7 you also must be running this as admin, or it will fail to be able to read the path variable, and install halts.
After an upgrade you need to run "mysql_upgrade -u root" and this will handle all the system table updates.
I might be flying blind on this one, but here it goes ... In your question and comments, you stated the following: The MySQL version in both servers is the same, even the config files are the same (the only difference is the path of the data and the fact that the production server doesn't log anything but the errors) Yes, the DB are the same ...
Keith Murphy (co-author of the MySQL Administrator's Bible) quoted here doesn't appear to think that's very good idea - straight copying of binaries. I know that the quotation is quite old, but I, for one, would be very reticent to do something like that. If I were you, I'd try the option at the beginning of the quote - pipe over a dump - I know that you ...
this bug is reported in MySQL Forums (67179) and the solution is mentioned here. please note that you should do clean-up, before creating tables /* temporary fix for problem with windows installer for MySQL 5.6.10 on Windows 7 machines. I did the procedure on a clean installed MySql, and it worked for me, at least it stopped lines of innodb errors in ...
Open up an Command Line Window as Administrator. Then, follow these steps STEP 01 : Shutdown MySQL net stop mysql STEP 02 : Get the MySQL 5.5 Data into the MySQL 5.6 Data Folder cd "C:\ProgramData\MySQL\MySQL Server 5.6" move data data_empty mkdir data cd "C:\ProgramData\MySQL\MySQL Server 5.6\data" xcopy /s "C:\ProgramData\MySQL\MySQL Server ...
Replication setup on a windows server is equivalent to doing it in other systems: The official manual provides you a detailed guide. In short: Configure on both servers a different server-id, and activate the binary log on the master. If it is not already done, the most typical way to do that is modify the my.ini file and restart the service (net restart ...
This: psql -U postgres -d utrechtTest > backupTest2.sql runs psql and writes its stdout to backupTest2.sql, which will be overwritten. You meant: psql -U postgres -d utrechtTest < backupTest2.sql which is better written as: psql -U postgres -d utrechtTest -f backupTest2.sql because if you use -f then psql can show line numbers.
According to SMAA documentation you can connect just fine to any Oracle server. It doesn't matter if server works on Windows or Linux. After connection you just go with the next steps.
Adam has covered most of the points. However, there are a few things to add. Usage of Windows in a production environment For tl;dr candidates: It is a Very Bad Idea™ to run a mongod instance except for a config server on Windows. Here is why. Both ReFS and NTFS are at least 1/3 slower than ext4 or XFS, the recommended filesystems for Linux production ...
Top 50 recent answers are included