Skip to main content

An elephant moves into new room

Friends after a long time, I am writing a blog. I was away for last 3 months, due to one of the critical projects assigned to me from the client. Recently, we have moved a young elephant into a new and big room. Yes friends, elephant is a single Big-table of around 700+ GB data size and the room is of 5 TB storage with SQL Server 2014 version. Earlier, we had limited resources, older SQL version and huge data, which were altogether making system hell .

I want to share about one of the worst days of my life. The day started with hot summer of April. Delhi's temperature was reaching 500 C and the database issues were making it even worse for me. I was almost about to quit before the system because the SAN drive was full of data as there was no free space and we couldn’t perform the delete/shrink operations in the weekdays because the shrinking activity was taking around 4-5 hours for 20 GB of data and daily data increment was about 15-20 GB. Then one fine morning, it was Wednesday, we had around only 20 GB space left and we had to manage it for 3 more days i.e., about 45GB space more space was required for that week as we could perform the shrink activity on Saturday only. But, on Wednesday, surprisingly the database grew upto a size of 20 GB and drive went full and everything stopped, resulting into slow performance of the application. The quick and easy solution was to move a small database of 45 GB to another server and change the connection string, and, we did same and application got started working for 3 days. Further, we did the maintenance activity on the weekend, deleted 2 million records, and then, got 80 GB of free space after shrinking.

Hence, I have got a breathing space for a month, in which we planned the migration testing and application impacts. I will share my experiences about all this in my next post.

Thanks for reading


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