Consultant at a tech consulting company with 51-200 employees
Consultant
2014-04-14T15:38:43Z
Apr 14, 2014
Would be happy to discuss and help. I am only aware of
InfoBright from what has been written publicly, however, MS SQL (and
associated tools) I've used rather extensively.
I evaluated Infobright for a project several years ago (Hadoop ended up being a better fit for this project). Infobright has a MySQL interface - so if your existing software can talk to MySQL then this will make integration easier (but it sounds like you have MS SQL, so this may not apply).
Infobright was very fast for analytical-type queries, scanning many rows, with a high level of aggregation. Another bonus was that there is very little tuning required (or available - general-purpose DBs need to be tuned to their application and use, but columnar DBs really only have one use). If you use the Infobright loader, getting data into the system is really fast.
Now the downsides - the open source version doesn't support INSERT, DELETE or UPDATE - the only way to get data into the system is via the loader, and once a table was present, all you could do is SELECT or DROP. The Open-source version is only useful for testing the speed of the DB against an existing DB (and the commercial version has a better workload manager, and gets better performance than the open-source version).
If you wish to have a mixed workload database MS SQL Server 2012 might be the way to go (but there will likely be performance compromises in both the OLTP and analytical workloads), On the purely columnar front, Vertica seems to have momentum at the moment, and has a full-featured community edition, which allows 1TB of data, with no time limits.
Business Manager (Exco level) & Executive Director at a retailer with 51-200 employees
Vendor
2014-04-10T17:30:25Z
Apr 10, 2014
The question is somewhat confusing/surprising because these 2 db's are not really in the same league
1) Are you really looking at sql 2005 or is it is mistype, because 2005 is so old that the question does not make sense.
2) Only sql 2012 is columnar, not 2005 or 2008. Inforbright is columnar, so the comparison of an old technology rdbms vs a columnar is not really comparable
3) Infobright is sort of opensource so it is low cost compared to Microsoft. Do you have an existing SQL2005 license and want to convert/upgrade to something more "current" than this old technology ?? The logic of the question is not immediately clear so one does not know what points of similarity/difference you are really looking for (again because sql2005 vs infobright is like comparing apples and pears.
I do not know InfoBright and never used it but I think you should first describe what you want to achieve using a relational database system. Pros and cons will make sense in conjunction with the role you want the relational database system to play. I also assume you want to asses the replacement of SQL Server 2005 with InfoBright, since SQL server 2005 is an old version of Microsoft SQL engine. If this is the case, it will be important to describe the interaction of your database system with other components and you have to think at compatibility aspect.
Find out in this report how the two Relational Databases Tools solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI.
Would be happy to discuss and help. I am only aware of
InfoBright from what has been written publicly, however, MS SQL (and
associated tools) I've used rather extensively.
I evaluated Infobright for a project several years ago (Hadoop ended up being a better fit for this project). Infobright has a MySQL interface - so if your existing software can talk to MySQL then this will make integration easier (but it sounds like you have MS SQL, so this may not apply).
Infobright was very fast for analytical-type queries, scanning many rows, with a high level of aggregation. Another bonus was that there is very little tuning required (or available - general-purpose DBs need to be tuned to their application and use, but columnar DBs really only have one use). If you use the Infobright loader, getting data into the system is really fast.
Now the downsides - the open source version doesn't support INSERT, DELETE or UPDATE - the only way to get data into the system is via the loader, and once a table was present, all you could do is SELECT or DROP. The Open-source version is only useful for testing the speed of the DB against an existing DB (and the commercial version has a better workload manager, and gets better performance than the open-source version).
If you wish to have a mixed workload database MS SQL Server 2012 might be the way to go (but there will likely be performance compromises in both the OLTP and analytical workloads), On the purely columnar front, Vertica seems to have momentum at the moment, and has a full-featured community edition, which allows 1TB of data, with no time limits.
Jamie
Hi,
I am looking a comparison between SQL 2012 and Infobright.
Since Infobright is an open source columnar DB and it is low cost, I am interested in hearing more about it.
At the same time, I am not sure about the pros and cons of SQL 2012 vs. Infobright.
So please suggest which columnar DB is better in all aspects.
Regards,
Pankaj
The question is somewhat confusing/surprising because these 2 db's are not really in the same league
1) Are you really looking at sql 2005 or is it is mistype, because 2005 is so old that the question does not make sense.
2) Only sql 2012 is columnar, not 2005 or 2008. Inforbright is columnar, so the comparison of an old technology rdbms vs a columnar is not really comparable
3) Infobright is sort of opensource so it is low cost compared to Microsoft. Do you have an existing SQL2005 license and want to convert/upgrade to something more "current" than this old technology ?? The logic of the question is not immediately clear so one does not know what points of similarity/difference you are really looking for (again because sql2005 vs infobright is like comparing apples and pears.
I do not know InfoBright and never used it but I think you should first describe what you want to achieve using a relational database system. Pros and cons will make sense in conjunction with the role you want the relational database system to play. I also assume you want to asses the replacement of SQL Server 2005 with InfoBright, since SQL server 2005 is an old version of Microsoft SQL engine. If this is the case, it will be important to describe the interaction of your database system with other components and you have to think at compatibility aspect.