Infobright and Analytics
-
As a software engineer myself, I have a strong background working with DBMS systems like SQL Server and MySQL. Not just from building web applications, but also from a n-Tier application architecture approach. I tend to use standard approaches to architecture and modeling, so like any engineer, I have come to test the limits and drawbacks of SQL Server and other OLTP databases. Building out the common business, data and presentation layers of any application tends to meet the many challenges of keeping those layers separate and autonomous. I have worked in many different industries ranging from healthcare and education to wholesale and retail, and one of the biggest problems that I always seem to encounter in my projects is ad-hoc querying in the reporting modules. How do you keep the database tuned for queries when you do not know what the query will be? SQL Server certainly has caching and even the ability to cache the actual query and the data separately, but when the CFO wants to look at common trends against the corporate database for spending with daily, weekly and monthly increments for sales engineers in the northeast regions...... You get the picture. Why a different approach? Because like any other DBMS, the drawbacks of traditional OLTP systems are that they are not built around an analytical approach. They do not focus on the statistical data that is necessary for reporting. I am a strong supporter of data analytics and feel that if your organization is not using them, then you are not competing at the level you can be. Infobright solves this problem with an approach that is based on performance, scalability and lowering overall costs. Take a look into why an analytic database is becoming a vital concept into the business intelligence communities at http://www.infobright.org
-
As a software engineer myself, I have a strong background working with DBMS systems like SQL Server and MySQL. Not just from building web applications, but also from a n-Tier application architecture approach. I tend to use standard approaches to architecture and modeling, so like any engineer, I have come to test the limits and drawbacks of SQL Server and other OLTP databases. Building out the common business, data and presentation layers of any application tends to meet the many challenges of keeping those layers separate and autonomous. I have worked in many different industries ranging from healthcare and education to wholesale and retail, and one of the biggest problems that I always seem to encounter in my projects is ad-hoc querying in the reporting modules. How do you keep the database tuned for queries when you do not know what the query will be? SQL Server certainly has caching and even the ability to cache the actual query and the data separately, but when the CFO wants to look at common trends against the corporate database for spending with daily, weekly and monthly increments for sales engineers in the northeast regions...... You get the picture. Why a different approach? Because like any other DBMS, the drawbacks of traditional OLTP systems are that they are not built around an analytical approach. They do not focus on the statistical data that is necessary for reporting. I am a strong supporter of data analytics and feel that if your organization is not using them, then you are not competing at the level you can be. Infobright solves this problem with an approach that is based on performance, scalability and lowering overall costs. Take a look into why an analytic database is becoming a vital concept into the business intelligence communities at http://www.infobright.org
craig trombly @ infobright wrote:
How do you keep the database tuned for queries when you do not know what the query will be?
You don't tune for a query; indexes aren't linked to queries, but to fields in a table (or a view). Put indexes on the fields that are used for searching and filtering. You can even ask Sql Server which indexes are used most frequently and which aren't, so it could automagically fine-tune itself based on recent usage (the server keeps statistics, so it "knows").
craig trombly @ infobright wrote:
but when the CFO wants to look at common trends against the corporate database for spending with daily, weekly and monthly increments for sales engineers in the northeast regions......
I don't see a problem there.
craig trombly @ infobright wrote:
Take a look into why an analytic database is becoming a vital concept into the business intelligence communities at http://www.infobright.org
Ah, so this is an ad? ;P If you want to introduce something new to the community, then please submit an article; the forum is more fore live discussions, and lots of new posts will move this one to the back, and people will forget about it.
Bastard Programmer from Hell :suss:
-
craig trombly @ infobright wrote:
How do you keep the database tuned for queries when you do not know what the query will be?
You don't tune for a query; indexes aren't linked to queries, but to fields in a table (or a view). Put indexes on the fields that are used for searching and filtering. You can even ask Sql Server which indexes are used most frequently and which aren't, so it could automagically fine-tune itself based on recent usage (the server keeps statistics, so it "knows").
craig trombly @ infobright wrote:
but when the CFO wants to look at common trends against the corporate database for spending with daily, weekly and monthly increments for sales engineers in the northeast regions......
I don't see a problem there.
craig trombly @ infobright wrote:
Take a look into why an analytic database is becoming a vital concept into the business intelligence communities at http://www.infobright.org
Ah, so this is an ad? ;P If you want to introduce something new to the community, then please submit an article; the forum is more fore live discussions, and lots of new posts will move this one to the back, and people will forget about it.
Bastard Programmer from Hell :suss:
Eddy, Thank you for letting me know. This is not an ad though. What I am trying to do is to get people talking about analytic databases and to encourage the use and understanding of them. I do appreciate the feedback from you.
-
As a software engineer myself, I have a strong background working with DBMS systems like SQL Server and MySQL. Not just from building web applications, but also from a n-Tier application architecture approach. I tend to use standard approaches to architecture and modeling, so like any engineer, I have come to test the limits and drawbacks of SQL Server and other OLTP databases. Building out the common business, data and presentation layers of any application tends to meet the many challenges of keeping those layers separate and autonomous. I have worked in many different industries ranging from healthcare and education to wholesale and retail, and one of the biggest problems that I always seem to encounter in my projects is ad-hoc querying in the reporting modules. How do you keep the database tuned for queries when you do not know what the query will be? SQL Server certainly has caching and even the ability to cache the actual query and the data separately, but when the CFO wants to look at common trends against the corporate database for spending with daily, weekly and monthly increments for sales engineers in the northeast regions...... You get the picture. Why a different approach? Because like any other DBMS, the drawbacks of traditional OLTP systems are that they are not built around an analytical approach. They do not focus on the statistical data that is necessary for reporting. I am a strong supporter of data analytics and feel that if your organization is not using them, then you are not competing at the level you can be. Infobright solves this problem with an approach that is based on performance, scalability and lowering overall costs. Take a look into why an analytic database is becoming a vital concept into the business intelligence communities at http://www.infobright.org
Reported: sounds like an ad and looks like an ad and if the page could speak it would probably quack.
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair. nils illegitimus carborundum me, me, me
-
Eddy, Thank you for letting me know. This is not an ad though. What I am trying to do is to get people talking about analytic databases and to encourage the use and understanding of them. I do appreciate the feedback from you.
craig trombly @ infobright wrote:
What I am trying to do is to get people talking about analytic databases and to encourage the use and understanding of them
Then why did you post
craig trombly wrote:
Take a look into why an analytic database is becoming a vital concept into the business intelligence communities at http://www.infobright.org
Not cool.
Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
-
craig trombly @ infobright wrote:
What I am trying to do is to get people talking about analytic databases and to encourage the use and understanding of them
Then why did you post
craig trombly wrote:
Take a look into why an analytic database is becoming a vital concept into the business intelligence communities at http://www.infobright.org
Not cool.
Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
-
Reported: sounds like an ad and looks like an ad and if the page could speak it would probably quack.
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair. nils illegitimus carborundum me, me, me