Skip to main content

Materialized view In RDBMS

For a moment if you look 15 years back to see the development of Database, Datawarehouse, and Business Intelligence. Then you will see a lot of features came and depreciated from database engines. Today I will talk about one of best feature, that grows the data warehouse "Materialized view" or "Indexed view". This is the heart of traditional data warehouse system which gives the optimized reporting and analytics.

Oracle first introduced with 8i, later, Microsoft SQL Server brings in 2000 version. SQL Server's Index view is better than other RDBMS. Indexed view of SQL server is Fully optimized for Datawarehouse queries and autorefresh of data and with schema bindings. This was also the reason, so Microsoft SQL Server gets popularity in Datawarehouse Market. Postgres requires Refresh Materialized View for updated data in reports. And if you ask with MySQL developer, they will say materialized view is nothing but a logically insert into the base table and then index it. So, MySQL is still missing this feature till 2018.


Popular posts from this blog

mongoDB error : aborting after fassert() failure

What to do when facing errors on mongoDB “aborting after fassert() failure” I like errors, in mongoDB this is the first error I faced and luckily many times. This error i faced during restoring name-space on local and restarting db system. I am still searching the exact root cause of this issue but i am able to resolve the current problem through below steps. Remove all relevant namespace files from data-file route path.. Now repair mongo instance using mongod process. mongod --repair ////////// execute command from bin folder path  Then start server using mongd process, if started server successfully then .. mongod  ////////// execute command from bin folder path Restore last backups as normal process. Now check database by connecting mongo shell. Thanks for reading,  Please comment your experience if you faced and also share knowledge if you have better steps to resolve...  

SQL71562: external references are not supported when creating a package from this platform

Last week I got this error from one of developer who was trying to deploy his project from Testing server to SQL Azure QA server. He was using “Deploy Database to SQL Azure” option from SSMS Tool-Task option. After connecting to SQL Azure portal when operation started to deployment below errors occurs. Validation of the schema model for data package failed. Error SQL71562: Error validating element has an unresolved refrence to object xx.dbo.xxxx external refrences are not supported when creating a package from this platform . Reason: The reason of the this error was; some functions of project was dependent on master database and only single database was being deploy to SQL Azure. DACFx must block Export when object definitions (views, procedures, etc.) contain external references, as Azure SQL Database does not allow cross-database external references So, this error was coming. Solution : I suggested him to create those function to locally

How to add an article in Transactional Replication

If we have a set-up of Transactional Replication for Data Distribution running and wanting to add new object to replication on other server we can follow below process. To add an article In Transaction replication with PUSH Subscription