We performed a comparison between Infobright DB and SQL Server based on real PeerSpot user reviews.
Find out what your peers are saying about Microsoft, Oracle, SAP and others in Relational Databases Tools."It has very amazing smart grid query feature for very fast aggregate queries across millions of rows"
"We have found the solution to be scalable."
"The support from Microsoft has been good."
"It's easy to use and fairly intuitive. I do development and data analysis, so we do a lot of work with SSIS and SQL Job Scheduler. Deploying new databases is very simple with things like BACPAC."
"The performance is good."
"The performance is great."
"SQL Server's performance is fine."
"A valuable feature of the solution is that it is comparatively simpler to manage than Oracle."
"The pricing of the solution is okay. It's less expensive than Oracle, for example."
"Only the data from the columns that reached 2GB will actually decrease. Other columns below 2GB in size do not leave the disk."
"Due to the fact that I'm dealing with the product more as a data analyst, the SQL Server management studio is really relatively primitive compared to other more advanced tools."
"More things in SQL Server need to be automated."
"I do not think SQL Server is suited for a typical database warehouse environment. However, people do use SQL Server for data warehouse environments but the best use case is for very small databases. If somebody wants to store more than 10 TB of data querying then the performance really degrades. The performance should be improved in the future to allow more scalability."
"The solution is lacking a compound index for comparing values."
"The performance needs some improvement and it needs more features integrated into it."
"Sometimes the system hangs. Its databases should be able to deal with more data in a faster way. Its speed of processing larger amounts of information should be improved."
"The price could be better. In the next release, it would be better if the database was more easily extendable."
"As a software developer, it can be hard to do something in Oracle that is SQL Server specific, and vice-versa, sometimes."
Earn 20 points
Infobright DB is ranked 31st in Relational Databases Tools while SQL Server is ranked 1st in Relational Databases Tools with 260 reviews. Infobright DB is rated 7.6, while SQL Server is rated 8.4. The top reviewer of Infobright DB writes "If you need a real big data solution, look for a distributed solution that actually has a proven track record". On the other hand, the top reviewer of SQL Server writes "Easy to use and provides good speed and data recovery". Infobright DB is most compared with MySQL and LocalDB, whereas SQL Server is most compared with MariaDB, SAP HANA, Oracle Database, LocalDB and IBM Db2 Database.
See our list of best Relational Databases Tools vendors.
We monitor all Relational Databases Tools reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
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.