change data source from mysql to sql server
Answered
We are changing a yellowfin source database from mysql to sql server. The schema will remain the same. Can I change the yellowfin source database settings to the new database and expect my existing reports to work?
The same question
Hi Steve,
I don't think I can give a definitive answer to this, Yellowfin generates different SQL according to which database is being used, and then that SQL mightn't compatible with the database you change to, and Yellowfin won't regenerate the SQL. For example, MySQL and SQL Server treat the concept of a database schema differently. And then there can be other differences such as database functions that you may have used within calculated fields, and also there can be different SQL syntax rules such as aggregations and grouping.
So at a guess, I would say that the reports won't work, however you may as well give it a try in your TEST environment anyway.
regards,
David
Hi Steve,
I don't think I can give a definitive answer to this, Yellowfin generates different SQL according to which database is being used, and then that SQL mightn't compatible with the database you change to, and Yellowfin won't regenerate the SQL. For example, MySQL and SQL Server treat the concept of a database schema differently. And then there can be other differences such as database functions that you may have used within calculated fields, and also there can be different SQL syntax rules such as aggregations and grouping.
So at a guess, I would say that the reports won't work, however you may as well give it a try in your TEST environment anyway.
regards,
David
Hi Steve,
I don't think I can give a definitive answer to this, Yellowfin generates different SQL according to which database is being used, and then that SQL mightn't compatible with the database you change to, and Yellowfin won't regenerate the SQL. For example, MySQL and SQL Server treat the concept of a database schema differently. And then there can be other differences such as database functions that you may have used within calculated fields, and also there can be different SQL syntax rules such as aggregations and grouping.
So at a guess, I would say that the reports won't work, however you may as well give it a try in your TEST environment anyway.
regards,
David
Hi Steve,
I don't think I can give a definitive answer to this, Yellowfin generates different SQL according to which database is being used, and then that SQL mightn't compatible with the database you change to, and Yellowfin won't regenerate the SQL. For example, MySQL and SQL Server treat the concept of a database schema differently. And then there can be other differences such as database functions that you may have used within calculated fields, and also there can be different SQL syntax rules such as aggregations and grouping.
So at a guess, I would say that the reports won't work, however you may as well give it a try in your TEST environment anyway.
regards,
David
Hi Steve,
I'm just cleaning up my work list and I noticed this Question is still open, do you approve of its status being changed to "Answered" or is there a further question on the topic that you would like to ask?
regards,
David
Hi Steve,
I'm just cleaning up my work list and I noticed this Question is still open, do you approve of its status being changed to "Answered" or is there a further question on the topic that you would like to ask?
regards,
David
Please mark as "answered" - thanks!
Please mark as "answered" - thanks!
thanks Steve!
thanks Steve!
Replies have been locked on this page!