Skip to main content

3rd day of Lock down in India

It’s 3rd day of Lock down in India. Today I started morning with some tips that will help to working from home during lockdown. Here I am going to share top 10 Tips while working from home due to corona virus pendamic outbreak .

  • Avoid working while lying in a bed or relaxing in a couch/sofa/reclining chair. These comfortable setups will make it difficult to focus on work. Ideally a study table and chair would be conducive to staying focused and maintaining productivity.
  • Maintain a routine, get up at a reasonable time, shower and have breakfast/lunch at the usual times. Also ensure you log off at reasonable times and get sufficient sleep at night.
  • Try and emphasize to your family that work from home times are not holidays and request them to keep interruptions to a minimum.
  • Take a 2-3-minute break from work every 30-45 minutes to just stretch, walk around or do some simple exercises.
  • Setup and maintain regular meetings with your managers and teams. Keep people updated about your work and request for updates to stay informed.
  • Setup reports, dashboards etc. which help you monitor progress of your work.
  • Be proactive if you need to contact people. Be prompt to respond to others if they are requesting your attention.
  • Ensure your laptops and mobile phones are in good working condition and fully charged.
  • Ensure your internet connection is stable. Ideally, high speed connections are not needed for regular browsing and emails however if you need to connect with teams over a video chat then consider upgrading your connection to a higher speed one.
  • Lastly, with the extra time freed up from commuting, spend time on looking after your health, spending time with your family and pursuing hobbies/passions.

Thanks for reading
Plz dont forget to like Facebook Page..


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