End of September I changed from IT Support to Database Administration. My company was migrating thousands of databases from Microsoft SQL 2008/ 2012 to 2016 and my instructor invited me to help out. Of course I accepted that offer and ever since then I’ve been in the database admin team. I should have changed teams a while ago but due to corona virus and home office I’m still in there.
Back in school and university I already learned about SQL queries but actually creating/ modifying/ backing up/ deleting databases, adding Windows users, creating SQL users – or should I rather call this creating logins, since there is a difference – and migrating databases is a whole new thing I found very interesting.
My first week was very simple, they taught me how to install SQL Server 2016 and configure everything. I just repeated it for the rest of the week. Starting the second week I migrated the first database by backing it up and restoring it on a new server. I was very happy and impressed it worked since I had no clue before on how to do any of that.
The second db server I had to migrate contained an SSISDB. To migrate an SSISDB you don’t actually restore tha database but create a new Integration Services Catalog. Then you Deploy Projects, select the Integration Services Catalog of the old server and import from it.
To migrate a Report Server we would backup ReportServer and ReportServerTempDB, drop the new default databases and restore the old databases on the new server . . .
One of the things I got confused about is the physical backup location. If you reconfigure the SQL Server to store new backups at a . . .