I have written a number of posts in the past working on shared databases and the concepts around these can be read at Sharding or No Sharding of Database – Working on my Weekend Project for the starters point of view. In a recent discussion at a user group, I had someone ask me what is the rationale around building a sharding key and what should be used for sharding their database. The concept, though common, it is not in black-and-white to what should be used as an sharding key. There are guiding principles which can be applied. Let us learn about Database Sharding.
In one of my recent consultation visits to a customer, there was deep performance related problems. They were unclear to what was happening and what was the actual problem. But these are some of the challenges that I love to take head-on too. In this quest to learn what the problem would be, I used a number of tools and during that time I figured out it was a memory pressure that was creating the problem. Let us learn about SQL Server Paging of Memory Identification.
Question: How to drop clustered index, which is created on primary key?
Answer: If you thought the answer as simple as following script, you are wrong.
DROP INDEX PK_Table1_Col1
PostgreSQL is considered to be one of the most advanced open source database. PostgreSQL is very easy to learn as well as it is very implemented and easy to implement. Along with SQL Server I have been recently focusing on MySQL and PostgreSQL. While working with three well proven Relational Databases, I have figured out that once you know one relational language, it is really easy to master another relational language, we just have to know the basics and the rest of the advanced concepts we can build over our founding concepts. In this blog post we will discuss about the PostgreSQL Learning Path.