Sidd's SQL Solution

In my last blog post , I talked about an effective and easy to use restore script, which can help DBAs in many scenarios wherein one of scenarios I mentioned was migration. Migration in itself is a vague term as it can be used in many different contexts by individuals for e.g. migrating objects from one server to another of same version or migrating objects between servers of different versions etc. In this blog post I intend to cover one such aspect i.e. migration of SSRS reports and objects from one server to another. I’ll try to cover up various scenarios that may arise and what approaches are available to do the same. Problem There are various scenarios that one can identify while thinking of migration of SSRS objects are like migrating objects from one server to another may be due to better hardware or setting up or refreshing non-PROD report server or migrating to another server of higher version or migrating a part or particular folder from PROD to non-PROD servers

The always progressive IT industry is moving at faster pace today than it ever was and this trend will going to continue in future too. This progressive industry has made everyone very familiar with words like migration, upgrade, DR (Disaster Recovery) or BCP (Business Continuity Plan) etc. as these are the activities which are being performed more often now all thanks to cheaper hardware and new versions of software releasing every year. In database world one activity which is common to all the above stated activities and is done even more often than them is database refresh. Activities like migration and upgrade are big projects and not performed as often as activities like DR drills or pre-production database refreshes or may be setting up Always-on, which are more likely to require to restore all databases from PROD. Implementation Keeping this high requirement of such database refresh activity in mind, I’ve created below script which can read backups from a given loc

New Year comes with a lot of new hopes, resolutions and opportunities and hence I also took this opportunity to write a post, which is also in line to this saying. As we all know very well that in today’s world the amount of data any application is gathering is huge and growing exponentially and so does the size of the database holding that data and ultimately the storage hosting that database. Though per dollar cost of storage comes down every year, we still need to be prepared for future growth expected for our databases at least by a year in advance to avoid any surprises because of disk spaces. Though this sound as basic part of all IT planning but answering how much space would be required can be tricky. It may not be possible to answer in certainty on how much space is required in future but we should at least have close approximates in hand. Implementation Same scenario also came to me recently and hence I developed my version of T-SQL script, which not only gives gr