ok .. so you have a OEM license I think! I was not able to identify you. But I think this misunderstanding about version came because the version string in tag is “4.2” for this version. This means that there are no changes in the XML schema with this version as compared to 4.2 betas/5.0. it does not identify the program version, but the XML schema version.
Quote:
“is there a setting I can add to the config file to not delete records in version 6.15? (notwithstanding the autoincrement/PK issue) …just curious”
A two way sync will never DELETE. For a one-way sync there is an option to 'never delete on target'. But it will UPDATE fromto if PK-values are the same. And a two-way will INSERT to either host what does not exist here if exists on the other (and still rows are identified by the Primary key).
Please create a ticket here http://www.webyog.com/support if you want to discuss upgrading. Even if you do not think it is very important, then possiby some of your customers may think so!
There is no setting I can put in the configuration file to tell sja to run a 2way sync without deleting, only inserting and updating?
>>No! For identical values of the PK the tool will UPDATE that row. That results inoverwriting in first half of a two-way sync.
…if that is the case, can I set the minimum autoincrement on one of the servers to, say, 10000 and so it will always be a different PK between each server?
>>That will work too, but not totally safe, unless you monitor how it grows to avoid collisions. I propose then you make it start with 10,000,000 then on one server …
BTW: what did you pay for that 4.2? Because there was never released a 4.2 FINAL version (there were 4.2 beta and RC's but final was versioned 5.0)?
… and you must have been using it for 3 years or so now, so I will not think that investment was total waste :huh:
September 24, 2008 at 12:48 pm
in reply to: #27397
reference to phpMyAdmin is not relevant at all. PHP scripts (also phpMyAdmin) (practically always) connect to MySQL from 'localhost', because it is the webserver (like the Apache webserver wiht PHP system/module loaded) that connects to MySQL when connection is from a PHP script. With SQLyog (direct connection) you on the opposite connect from your local machine.
The users 'karthik'@'localhost', 'karthik'@'%' and 'karthik'@'some_ip_address' are 3 *different* users in MySQL and I bet that only 'karthik'@'localhost' (or 'karthik'@'127.0.0.1') exist at the moment. And that is the problem!
You will need to create a user that is allowed to connect from remote host(s). If your hosting does not allow for that you will need to use (HTTP or SSH) tunnelling. Those options are included with the ENTERPRISE version. But since you can connect (but not authenticate) that is likely not the problem.
Use your control panel application or commandline client on the server to create such user. Commandline syntax example
Code:
grant all on *.* to 'root'@'%' with grant option;
.. will create a 'root' user that can connect from everywhere and has same privileges as 'root'”localhost' (but I do not necessarily recommend such 'strong' user
privileges for remote users!).
Please read from the FAQ linked to above again:
Quote:
* User is not allowed to connect from the actual host. Note that MySQL by default only allows connection from 'localhost'. To specify from where a user may connect SQL wildcards (% and _) can be used. Simply 'someuser@%' means that user 'someuser' may connect from everywhere.
Please search a little. This has been asked 5 times lately, I think!
It is *per design* thatoverwrites where rows have the same value for the Primary Key! The meaning of a PK is that it is a *unique identification* of rows.
So to avoid this you have 2 options (that both will prevent an identical PK-value to be created on both servers)!
1) define auto_increment_increment and auto_increment_offset server variables and use an auto_increment INTEGER as the PK. Define the server variables so that it will be 1,3,5,7 etc. on one server and 2,4,6,8 on another server. This solution will require a recent MySQL server. I do not recall exactly from what version those server variables were introduced – check MySQL documentation for details.
2) add a column to the PK that is constant on the server and diffferent between servers (like DEFAULT 'server1' on one server and DEFAULT 'server2' on the other) .
One detail to observe with both solutions is that should you want to delete data/rows you will need to do on both servers before syncing – because if you only delete one it will be recreated where it was deleted with next sync.
“I am on version 4.2” .. btw: this was long ago a non-supported version! In principle we support latest stable version (now it is 7.1) only!
As per policy we do not post links to old versions (with the exception of 5.32 – that is last version supporting Win9.x/ME – only) publicly – we only distribute old versions to registered customers (after a ticket request) when there is a specific reason for it as described in the FAQ. This is because we want to be able to notify those users when an issue is fixed as well as well as we like to get feedback that it was fixed!
Before 2.6 there was a bug that could cause downloads to last forever-
There are tow settings in log analyser filter: 1) log file chunk size (default setting is 1 M) and 2) timeframe. It is the smallest of those that have effect. Does this explain? Try selecting ALL for both. Also in filter settings disable the option to 'substitute literals'.
to save from the SQLyog GRIDs (of the data or result tabs) you will have to click the 'save' icon (looking like a diskette), or you will need to move the cursor to another row with one of the arrow-keys.
1) There is no way to migrate Stored Procedures. The *code* defining a SP on either system is different (and with non-trivial examples mostly very different). MySQL only supports coding SP's in SQL – not in VB and C# (like SQL Server does) and not in Perl (like PostgreSQL does). But even with SP's using SQL only the code will most often be very different. And besides the code is not exposed by the ODBC driver either.
2) A SQL Server VIEW can be migrated to a MySQL table, but not a VIEW. Again a VIEW definition is *code*, so this is same problem. But the Migration tool should expose theVIEWs (to make it possible to migrate data here to a table in MySQL) and you tell it don't? Please check 'advanced' settings/properties for the driver. If no success tell SQL server version and ODBC driver version (but again we cannot help with migrating a VIEW to a VIEW – only to a table)
SP definition syntax is not standardized across different RDMS.
September 22, 2008 at 11:52 pm
in reply to: #27358
The quotes are correct for 'normal MySQL mode'. However if server is running ANSI mode we cannot support this before MySQL 5.03. Also any server version before 3.53.x is not supported (versions before and after 3.23 use different client libraries).
“MySQL's WinMySQLAdmin” .. hmm, this is an old boy but not relevant! SQLyog does not care what other clients connects to the server. ODBC driver is also irrelevant. SQLyog does not use ODBC for connection . It uses the MySQL C-API (libmysql) that is compiled into SQLyog.
Why do you use that old version on your local? Active stable version is 5.0.67 (community server). 5.1 is close to stable release (5.1.28 was just released) and 6.0 is in progress.
As regards 3.23.x support I can tell that we support it only for as long as we need not compromise on performance etc. with recent versions. As long as 4.0.x is used widely it does not matter much to support 3.23 too (for a client of the type of SQLyog they are almost identically). But both 3.x and 4.0 are not supported any more by mySQL/Sun and even 4.1 is in 'limited support' (or whatever they call it). And support for 3.23 is restricted to 3.23.58. If anybody reports an issue with any version before 3.23.58 (the latest 3.23.x where MySQL released binaries) the reply is that “we really do not care about this”. Just like we also do not support Win95!
But probably what happens here is that server is running ANSI mode. Can you check the my.cnf/my.ini for such global setting?
September 22, 2008 at 11:35 am
in reply to: #27295
Just uncomment that (remove “/*” and “*/”) and restart MONyog and Dashboard will have a indication if slave is running.
It is also posssible to to add a graph for for instance 'seconds behind master' (use an existing graph definiton as template and refer to “customisation MONyog object model” in docs). A developer promised me that he would post here with more details when he is free.
Author
Posts
Viewing 15 posts - 2,656 through 2,670 (of 7,398 total)