As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
My team has a product that was created using MySQL. All of our other systems use SQL Server 2008, and I want to investigate migrating to SQL Server. The person who headed up the MySQL server effort has left the company, so now we don't have anyone familiar with MySQL. We want to migrate, but I want to be able to present a detailed analysis as to why we want to migrate. Are there any documented case studies on the advantages/disadvanteges of MySQL, and any compelling reasons to migrate to SQL Server? FYI, the app is still in Beta mode, it would be easier to migrate now than 6 months from now.
The two conversations that I don't want to have with my boss are:
1) I want to migrate the app to SQL Server, and the reason is "just because I want to ".
2) We should have migrated 6 months ago, but we didn't and wish we had.
You've already made the two most important points for your case:
"All our other systems use SQL Server 2008"
"Now we don't have anyone familiar with MySQL".
Given those conditions, the case has to be made for retaining MySQL, not moving away from it. If the product isn't dependent on specific MySQL features, move. Simplify your stack, reduce your support overhead.
I say this as somebody with a strong antipathy to MS products. But I'm also a responsible senior software engineer and I know what's right.
Related
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
I want to start a web project in ASP.Net and still not decided which database to use. I have had experience with MSSQL and Oracle, but I want one that is free to the end user.
My options are: MySQL, Firebird and PostgreSQL.
What do you recommend and why?
Thanks for the support.
I've used MySql, PostgreSql, and MS Sql extensively. I would recommend MySql. It is easy to set up and configure, has all the features you will need, and is used by countless open source projects across the world, including Wordpress, which a ridiculous number of people use to power their websites.
I would use PostgreSql if you need more powerful and fine-grained support. It has been around a long time along with it's ancestors, and at one point powered the largest database in the world, a 2 petabyte database run by Yahoo.
For a simple web app, though, I would recommend MySql. It is used by more people, and is the de facto open source database.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
I'm going to deploy an IIS 7 Web Server for my ASP.NET MVC 4 Application.
Windows Server 2008
IIS 7
SQL Server 2008
I'm going to do this:
In my application:
*Each customer have to use two database
First DB: Their own database(each customer have one)
Second DB: The Global Database (all customer have the same one)
And the First DB can join to the second DB.
(I'm going to use Server Binding)
And about Web-server:
Each customer have their own Web-site (on the same IIS Web Server) to get the View/UI
All customer have the same API Web Server (this one will do everything: get data from database, add/remove data,...)
Each customer have one Search-Engine(Suggestion tool), to use this tool, I have to load all relative data into Memory(reload this data each 4 hours)
This is the first time I have to deploy a server like this, so I don't know how to do the best...
If there are any advises, suggest, reference, books,...please send it to me.
Any help is appreciated!
IIS and SQL Server already cache things in memory for performance, provided there is enough memory and the programming allows it. You don't need to write a special module to do this.
You don't need Server Binding to join across databases in SQL Server. You just join accross the database in your SQL (provided they are on the same server)
SELECT D1.F1, D2.F2
FROM
ClientDatabase.dbo.Table1 D1
INNER JOIN
GlobalDatabase.dbo.Table2 D2
ON D1.Key = D2.Key
SQL Server already comes with a text search engine http://msdn.microsoft.com/en-us/library/ms142571.aspx
Will you be searching text within database records, or will you be searching text in external documents (i.e. Word, PDF)
It appears you are reinventing the wheel. You are more likely to have success if you use pre-built proven components!
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I am working on .NET environment.
Because of sql server express limitations (4gb max) I want to switch a free solution.
I am checking around and found out postgresql OR mysql would be great solution.
As I only worked on on MsSql, I want to learn which database would be easier for me to migrate all my existing data.
Also which database syntax (postgresql OR mysql) is closer sql MsSql syntax and structure.
So I can learn it faster.
Thanks for your help.
Hmmm... you will find language differences in either of those. I had that same choice a while ago and ended going to MySql due to its immense comunity.
Of course, if your only reason is the 4gb limitation I would not recommend switching (but that's just me). You should upgrade to SQL 2008 / 2012 which they both have 10gb limitation. Also, if you must know, there are other limitations such as using only 1 processor and I believe there's a RAM restriction as well. Anyway it shouldn't make a noticeable difference with small databases (<10g) and not-so-complicated queries.
If you want help in migrating from MSSQL to MySQL you should google for something like "MSSQL to MySQL Migration Toolkit" (I did that). It's fairly easy, you'll make the transition in no-time and most likely without any problems.
Best of luck
MySQL Workbench has a migration wizard. Is has some prerequisites for MS SQL, which are explained very clearly in the wizard help docs.
http://www.mysql.com/products/workbench/
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
As i know about Both Sqlserver and Oracle are Database Systems.
1. In case of Sql server, we can work with multiple databases at once.
Is their any other difference between oracle and sql server.
Check out this comparison of databases, there are quite a few differences.
They both store data, but apart from that they are like chalk and cheese - they are massively different in a lot of ways.
Oracle can be used as a small database system, but is more aimed at the enterprise data storage level, whereas SQL Server is more commonly used at the lower end of the data storage market (although they also have a very good enterprise level product).
I suggest you just start with the Wikipedia entries, then if you have more specific questions come back and ask them.
Oracle
SQL Server
P.S. Even though I tendered an answer, I'm voting to close this as the question is way too broad in scope.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
if you read some MVP's blog for watching out the difference then they always can talk SQL server because why they tell about Mysql whenever they itself not used My SQL server or itself not interested in Mysql. [you are amazed then they write everywhere that when someone talk them for opensource database then they answer MS SQL server express. ha ha [nice joke they make]
if you talk with someone who use MySQL then they difficult to answer because they not used MS SQL so tehy first not give answer or very hard to explain.
so i need to know about what the thing a have and another not. are their anyone can explain the pros and cons of using both type of database.
I would recommend reading
this (point of view SQL) to give you an
idea
2-Here
to view the other side (Mysql)
3- And finally some differences