Disasters are always bad. Recovering from disaster is a skill and needs a lot of planning and practice. One of my clients had a disaster and built a new machine to restore the backups. They tried a few attempts to install SQL Server but were having issues. Finally, they contacted me for consultation to fix rule reporting services catalog database file existence.
Question: How Many Foreign Key Can You Have on A Single Table?
I was asked above question in my recent SQLPASS presentations. I quickly answered that it is 253. However, after I returned home when I searched a bit more, I realized that my answer is not complete, hence this blog post.
Does Dropping Primary Key Drop Non-Clustered Index on the Column? – Interview Question of the Week #085
Question: When we drop primary key on the column, does it automatically drop a non-clustered index on the same column (if created)?
Before we see answer of this question, I suggest you read following three blog posts, they discuss various similar aspects related to the primary key and clustered index.
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.
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