https://mariadb.com/blog/getting-microsoft-sql-server-data-mariadb-connect-storage-engine
In the above page, can anyone tell me what this sentence means?
"MariaDB works with many clients to migrate Microsoft SQL and Oracle to
MariaDB"
Does that mean: The company MariaDB works with lots of customers to migrate their SQL Server database or Oracle database to MariaDB?
The thing is I got it as the above meaning but my co-worker translated it to something like "MariaDB itself is compatible with lots of other computers(or components)...". The word "clients" was quite confusing in this sentence. If it is "customers", it must be clearer
Sorry for the strange question, i'm translating the article to Japanese.
Yes it works with lots of clients to migrate from Oracle or MS SQL Server. You can call MariaDB's support to know more about their clients.
MariaDB Database Migration Team
This is pretty common in databases even MySQL has Percona which helps in migrating etc.
Sure, MariaDB will sell you its consulting services for the conversion services. But the statement also means that the "Connect Storage Engine" feature of MariaDB (not MySQL) provides a tool to facilitate the conversion.
MySQL Workbench is another tool for conversion.
Related
Can I know please the difference between SQL Server and SQLITE .Is there any major differnces in the syntex? I know SQL but I did not learn SQLITE which I have to know within days ???
SQLite supports pretty much full SQL syntax, in fact it probably has less quirks than MS SQL Server
The huge difference is that one is a server (SQL server). The other is embedded (SQLite), a totally different use case
Write a hello world program using SQLIte, create a table and store a row.
There are some very good free sqlite tools for inspecting a sqlite DB so you can see if your test worked
SQL is the query language to manage databases.
SQL Server is DBMS product of Microsoft.
SQLite is a open-source DBMS often used in PoC (proof of concept, or prototypes) applications or mobile apps. Its "advantage" is that the whole database is stored in a single file in your file system. You don't have to setup a whole database server to work with sqlite. This is obviously not a solution to real life applications or web sites.
I am trying to migrate database from oracle 11g to MySql 5.7, after the migration what are the issues i might find ?. How triggers, sequences, privileges etc are supported ?. Any performance issues ?. I need to report these pros and cons before migrating from oracle to MySql. Please help me to report, i didn't find any solution in google related to this, anyone please help.
Despite the ANSI SQL standard every DBS has its own specialties.
All your Questions are so much depending on your specific DB structure, code and functions you've used, nobody can give you clear answer.
You can run in all the Problems you are asking or into none of them.
If your current Oracle DB application is 100% ANSI SQL it should at least run, but i doubt it will be 100% ANSI SQL.
The only possible answer is try it, see what Problems you are facing and then decide if you want to do it or not.
https://mariadb.com/blog/getting-microsoft-sql-server-data-mariadb-connect-storage-engine
In the above page, can anyone tell me what this sentence means?
"MariaDB works with many clients to migrate Microsoft SQL and Oracle to
MariaDB"
Does that mean: The company MariaDB works with lots of customers to migrate their SQL Server database or Oracle database to MariaDB?
The thing is I got it as the above meaning but my co-worker translated it to something like "MariaDB itself is compatible with lots of other computers(or components)...". The word "clients" was quite confusing in this sentence. If it is "customers", it must be clearer
Sorry for the strange question, i'm translating the article to Japanese.
Yes it works with lots of clients to migrate from Oracle or MS SQL Server. You can call MariaDB's support to know more about their clients.
MariaDB Database Migration Team
This is pretty common in databases even MySQL has Percona which helps in migrating etc.
Sure, MariaDB will sell you its consulting services for the conversion services. But the statement also means that the "Connect Storage Engine" feature of MariaDB (not MySQL) provides a tool to facilitate the conversion.
MySQL Workbench is another tool for conversion.
We're upgrading our systems to support clustering and auto failover features. Our business runs .NET 4 applications, web apps and services on SQL Server Express. We can upgrade to SQL Server Standard, but the cost has motivated us to consider other options. Is it a legitimate option to integrate our .NET data layer with ODP.NET? After searching, I have seen a tendentious statement or two in the negative (viz) and yet it would seem that people are doing it anyway. What development features in the Visual Studio IDE will we lose? Thanks for your help!
Well, I'm now working since 20+ years with Oracle and MS SQL Server, having done a lot of projects. Some projects are running now more than 10 years, with all the updates, maintenance and so on.
My quick answer is: Stay with MS SQL Server. Go to Oracle only, if you have really GOOD TECHNICAL reason, or if you are planning really an ENORMOUS database, and if you have enough staff to handle all thge administration.
The main reason is that SQL Server is much easier to maintain; and it also integrates greatly into the Microsoft environment.
Oracle, in contrast, has a steep learning curve. The handling of Oracle is much more "manual" then MS SQL Server. Well, that's also a good thing, because you are in control of every small detail, but it also means that you need to learn a lot; or you need to pay experts. And it is not so easy to find people who really know what to do.
I really like both Systems, but for a rule of thumb, I normally suggest to use MS SQL Server.
I've been using .net with Oracle for years, and migrate away from it whenever the option is available.
If all your database code is in stored procs and you call it though the codebehind or a library and you use ansi sql your migration from ms sql to oracle will be fairly painless.
If you use TableAdapters, they re-write any sql you put in to the oldschool oracle 8 syntax like table1,table2,table3 then have a big where clause to do the join conditions. There's also some weird bugs where sometimes sql that runs fine over in SQL Developer won't work in the TableAdapters.
If you use Entity Framework migration should be pretty easy, but the MS SQL driver is much better then the Oracle one. There have been several queries I couldn't do though EF in oracle because of some of the various errors with the current driver.
If you need more info let me know.
Also if Cost is the main reason to consider migration, why not go with mysql?
Since you are already working in MS SQL, you must be habitual of the way it work, be it entity framework or any other data execution. Yes offcource, microsoft has very high license rates for it. But if you want to move to any other database, it is perfectly alright. I have personally used MS SQL and MySQL both. Initially you might face some syntax related issues, but do remember that logic remains the same for fetching and saving the data. Further it gives a benefit that you got to learn a new language and that too at the expense of far less money.
I intend to start developing an ASP.NET application and I am wondering which database to use. Performance is very important and the database should be able to handle without issues a database of about 50GB. I am wondering however, if a SQL Server license is worth paying for. I have looked for performance and scalability comparisons between MSSQL Server (2005/2008) and MySQL but I can't seem to find any good tests. Can you point me to some extensive benchmarks related to this subject?
MySQL traditionally is very fast if you are doing a lot of reads. For example in a web site there is probably a 100 to 1 read write ratio so MySQL works well. If you are planning a high transaction database then head straight to MSSQL. If money is no issue head straight to MSSQL anyway because it is a better product.
As mentioned, MySQL can provide high read performance (assuming simple queries with few or no joins) as long as you use the default table type.
However you also stated the database is 50GB in size, which suggests you may be looking for a database that will reliably store the information. Using the default table type MySQL is not a reliable database by any stretch of the imagination.
If you want a fast, free alternative to MS SQL then PostgreSQL may be a good choice - it is fast reliable, and has a more open licence (if you use MySQL for a commercial project you'll want to read its dual licence very carefully). The only downside to PostgreSQL is that it shares some of the same DBA guru requirements as Oracle, where as MS SQL can often be managed by a regular IT person, and MySQL doesn't need much management besides restoring the old backups everytime it decides to become corrupted and lose your data.