Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2005 Forums
 SQL Server Administration (2005)
 Establishing Database Direction

Author  Topic 

jbates99
Constraint Violating Yak Guru

396 Posts

Posted - 2011-07-28 : 08:36:57
Hi fellow DBAs,

I'm conducting a meeting with developers and some IT managers to discuss our direction for *future* databases. We have too many MySQL databases and I want to emphasize the importance of choosing SQL Server for new databases.

Some of you may have been involved in discussions relating to database strategy in your organizations. What other topics could be discussed in such a meeting?

Thanks for any ideas.
John

Michael Valentine Jones
Yak DBA Kernel (pronounced Colonel)

7020 Posts

Posted - 2011-07-28 : 09:27:00
You should be prepared to discuss all factors of the relative cost of different solutions.



CODO ERGO SUM
Go to Top of Page

robvolk
Most Valuable Yak

15732 Posts

Posted - 2011-07-28 : 09:40:10
1. Is data integrity important? If so, SQL Server has stronger support than MySQL ever did (InnoDB engine notwithstanding)
2. Is vendor support important? Do you have any support contract with MySQL? If you've had a deep problem with the MySQL software (possible bug, low-level interaction, etc.) how did you resolve it?
3. What application platforms are you writing in? If it's .Net, SQL Server is the logical choice. If it's Java/Ruby/Python/something else and they want to continue with them, then it's tougher to recommend SQL Server. Same applies to Windows vs. Linux operating systems.
4. What does "too many MySQL databases" mean? Why is it a problem (besides the obvious "it's MySQL")
5. If by "too many" you mean you'd want to consolidate systems onto fewer servers, what is your plan for that? Virtualization? Buy bigger hardware?
6. Do you have a need for high availability, disaster recovery, or geographic distribution of data and/or systems? SQL Server has numerous built-in features to support this (replication, log shipping, DB mirroring, failover clustering). MySQL has support for replication but I don't think it's a core part of the engine, and I'm not sure it's free (please check though)
7. Are SQL Server licensing costs an issue? If there are many small DBs (< 10 GB) that are not performance critical, SQL Express 2008 R2 is free and can support that. There are also Web and Workgroup editions that are less expensive than Standard and Enterprise.
8. Do you need tools for data import/ETL (Integration Services), reports (Reporting Services), or data warehousing or analysis (Analysis Services)? These are free components in SQL Server, and have Microsoft's full support.
Go to Top of Page
   

- Advertisement -