Forum Replies Created
-
AuthorPosts
-
katlaMemberRitesh wrote on Oct 6 2005, 02:12 PM:I am not sure if I understood the problem. Can you explain it a little more?
The problem was that I did something which I should not do… I actually messed around with connections so that when I thought I worked on the replica – I actually worked on the original and it effectively did what it was told to do – and destroyed my original database. But since I were unsure about how sqlYog worked – I did take an mysql backup before I started messing about.. and that was when i found the bug in mysql backup…
(there are lots of other annoying things in mysql – text colums can for instance not be used in recordsets when I am updating (like I am used to from ms sql server) – the ODBC driver is not as good as it should be.. But I guess that is what is the price one have to pay for a software that does not drive one into bankrupcy..)
katlaMemberRitesh wrote on Oct 6 2005, 01:29 PM:You can indeed do it using the ODBC Import Tool (Migration Toolkit in v4.2 BETAs).[post=”7460″]<{POST_SNAPBACK}>[/post]Yes! I understand that I can do an Import. But I would like to do an automatic sync every 15 minutes or so so i can do this for a kind of insurance if the primary server goes down.
Ideally I would have liked to have replication which is very good with MS SQL servers – but the cost of 2 complete servers are prohibitive. But MS is making a sql server 2005 Express which is free – but it only takes replication TO it – not FROM it. And it does not support what was great with ms sql 2000 – DTS (its not called that now).
I know I can do quite a lot with MySQL and I am now doing all my development work for inhouse solutions for this DB – but since I have heard rumours about “instability” from friends when databases grow (on Windows that is) – I would have preferred to use MS SQL server since it is fantastic when it comes to stability (and a lot ofther things as well). But MySQL is so far quite nice too – but there are too many bugs leading to lots of work. And up to now the lack of Stored procedures, trigger and views have been a limitation.
A bug example for Mysql (4.1.12 at least): a ' in a varchar field lead to that the backup in 4.1.12 is impossible to use since the mysql outputs ,', for it (while it would output ,'A', if the field had contained an A. I spent several hours last mondays with this simple error which lead to that the restore did not work.
(and the need for the backup was that I tested sqlYog and accidentally destroyed my production database… thats how newbies with sqlyog can “misuse it”..)
katlaMemberQuote:I think this belongs in the Forums! I'll delete the entry from the FAQ – just for your information!No problem – I first posted it in the faq – but there were some error messages on the top of the screen – so I was not sure whether is was stored or not..
—
Here is how it looks like in sql compare
First how structure compare looks:
This is how source looks like in SQLyog
And this is how Target looks like.
a) The 4.1.12 is intalled on a windows 2003 server and the 5.0.rc is on a w2K server
😎 i run the sqlYog enterprise on my windows XP. logon is root for both servers and i use normal server connection (no tunnelling)
weird..
-
AuthorPosts