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 50⁰ 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

Comments

How to encrypt and decrypt Table data in postgres

For encrypting and decrypting , we must use the bytea data type on the column which we implement. Bcoz bytea will use the pgcrypto method by default. However, you will need to create the pgcrypto extension to enable these functions as they are not pre-defined in PostgreSQL/PPAS. Example CREATE EXTENSION pgcrypto; CREATE TABLE userinfo (username varchar(20), password bytea); >> Inserting the data in an encrypted format INSERT INTO userinfo VALUES(' suman ',encrypt('111222','password','aes')); select * from userinfo ; >> Retrieving the data as decrypted format SELECT decrypt(password,decode('password','escape'::text),'aes'::text) FROM userinfo; Thanks for reading Plz dont forget to like Facebook Page.. https://www.facebook.com/pages/Sql-DBAcoin/523110684456757

How to recover msdb database from suspect mode

It was Monday 9 th Jun 47 degr. temperature of Delhi-NCR. Temperature was like boiling me and database. When I reached my office( @ 8.45 am) got an alert from one of Server. “MSDB is in suspected mode” At the same time comes in my mind, this issue will boil me today.. I just tried to cool my self through cold drink then connected server from my local system using windows authentication mode..

History of MySQL from AB Corp to Cloud Database

MySQL was created by a Swedish company, MySQL AB, founded by David Axmark, Allan Larsson and Michael "Monty" Widenius. Original development of MySQL by Widenius and Axmark began in 1994. The first version of MySQL appeared on 23 May 1995. Its name is a combination of "My", the name of co-founder Michael Widenius's daughter,and "SQL", the abbreviation for Structured Query Language. · 23 May 1995 - First internal release · Year 1996 - Version 3 o Simple CRUD operations o January 1997 Windows version was released on 8 January 1998 for Windows 95 and NT o production release 1998, from www.mysql.com · Year 2002 - Version 4 o MyISAM o unions o Tracking o B-trees o s...

The Young DBA

Search This Blog