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.
| Author |
Topic |
|
jay83091
Starting Member
14 Posts |
 Posted - 2010-05-05 : 21:37:44
|
| Hi Everyone,I am a SQL Server newbie and was wondering if anyone could help me with choosing the correct SQL Version and licensing options.- Looking to purchase SQL for a small ~ medium size company environment (max 100 people in the company) - Mainly to replace existing access database (40 of them 50MB each) and to integrate data from different systems (Simple & common systems) and design simple data warehouse to bring all the data in one spot and use with Other BI Tool to produce reports- Just purchased medium size server (8 Core, 12 GB Memory)Question1. Which version of SQL Server will suit the environment mentioned above? (SQL Server 2005 standard?)2. What will be the best licensing option?3. How do I get the license? Does it take ages?4. I am assuming either DBA or DWA need to be involved in installing, configuring the SQL Server and designing the simple data warehouse. Roughly how much DBA effort will be required for this sort of task? I absolutely have no IDEA.Any help will be much appreciated.Regards,James |
|
|
dportas
Yak Posting Veteran
53 Posts |
Posted - 2010-05-06 : 04:42:06
|
| Assuming you've already settled on SQL Server the choice of version is easy. Use SQL Server 2008 R2 unless you have a special reason to choose an older version. Choose the licensing model that is most cost effective for you. If you have 100 users then that's most likely going to be processor licensing. A processor licence is costed per socket, not per core. The choice of Edition should be based on the features you need.http://www.microsoft.com/sqlserver/2008/en/us/pricing.aspxYou can purchase through a Microsoft reseller or partner and you could either Google for one or call your local Microsoft office which you can find via Microsoft.comHowever, it seems like you have some work to do first. Even though your existing data is very small, given the investment you are planning to make I suggest you first hire the person you need to do the work and let them help you choose the tools to do it. BI tool selection is important to the success of any BI project and is probably a more critical decision than the DBMS to be used. It can also work out to be more expensive. You don't need a DBA at this stage, you need a BI developer / consultant (BI / DW development projects are very often outsourced). Here I must declare an interest because I'm a consultant and my company provides BI consulting services. |
 |
|
|
jay83091
Starting Member
14 Posts |
Posted - 2010-05-06 : 19:19:26
|
Thank you for your reply,I am thinking of hiring someone but if you could help me understand little bit more,- What is the major difference between DBA and BI/DW Consultant? I thought DBA would know how to design dataware houses, config etc?Thhanks again  |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
dportas
Yak Posting Veteran
53 Posts |
Posted - 2010-05-07 : 07:19:02
|
quote:
Originally posted by jay83091
- What is the major difference between DBA and BI/DW Consultant? I thought DBA would know how to design dataware houses, config etc?
The definition of a DBA role varies a lot and so does the experience of DBAs themselves. Of course there are DBAs who know BI and there are certainly DBAs who know how to build a data warehouse.However, it seems like you may need someone who can specify and deliver a complete solution: someone who will do the business analysis, knows and can recommend BI tools and then do the development and implementation. That's not what I would usually call a DBA ... but it depends on your definition of DBA. |
|
|
|
|
|
|
|
|
SQL Server Version? Licensing?!?