The Young DBA

 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..

Cleanup History and Maintenance Clean-up History related to Maintenance Plan. It is a bit confusing but they are totally different . If we are designing maintenance plan then we should also create cleanup history and maintenance clean-up history.   

Dear God,                 1st of all thank you so much, You have made me the part of your creature. You have stolen few things early from my life but no issue I Born B+. You are a great architect and designer, you have designed a beautiful world, human beings and planet. You have given me opportunity to look everything in database point of view. I am sharing with you what I observed. Our  fingerprint   is working as Unique Identifier Primary Ky . Atmosphere and sessions are working interdependent like referential Integrity . All the things you have been relate to each other and effecting to each other just like done proper Normalization . You have given two Authentication mode of life Good/Bad and Truth/False. Configuration and Resources of our planet is with Fixed mode, it’s not dynamic. Sometimes earthquake and disaster turning life into RTO. But god there is no any planning for Backup and DR of our limited Resourced Earth. We are using our resources quickly and

Now I am habituated to use CTRL+R to see the code in full screen because it allows me to hide the result or message pane from windows.  Working on SSMS for Development or testing any TSQL procedures I like too much and I am using this tool since 4 years.

After New Installation of SQL Server database will be in Full Recovery Mode by default. When our Application Goes Live and Transaction started processing we should have a proper Backup-DR plan otherwise We can face below error in SQL server in future. Because it is necessary to Truncate the TLOG in Full Recovery Mode.

Error - provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe "A mountain in labour and a mouse be result" .Sometimes it happens in finding Root Couse. I faced the same when I was new in organization. Web application was throwing error something like below …

Every organization have different work environment, culture and network infrastructure. After getting place in new organization I am learning new things and comparing all those about past windows, db , application & processes .