-1

I'm working on taking a on-premise server that works with SQL Server 2019 and migrating this to the cloud. The data right now is not the important thing, but rather the schema since this is a proof of concept. The main issue is that the on-premise server uses filestream to sometimes handle files. This will have to change in the future as refactoring and application updates take place.

The easiest way I thought would be to generate a schema .sql script from the old db and run that in the new environment, but this generated a TON of errors (25k).

Most of the errors include:

  1. Failed permissions in database 'master'
  2. Not finding certain objects in the new clean DB
  3. Extended properties are not permitted on an object or it doesn't exist
  4. Invalid data types
  5. Database doesn't exist or permission not allowed
  6. Filestream feature is disabled

So this probably won't work as a drop in solution to get the schema migrated to the new db. I've heard about AWS DMS (data migration service), but I don't know a lot about this. I'm asking, what tools could I look into to migrate over to RDS when RDS doesn't support features native to SQL Server?

marc_s
  • 732,580
  • 175
  • 1,330
  • 1,459
Lacrosse343
  • 491
  • 1
  • 3
  • 18

1 Answers1

0

One way to import schema is through the generated scripts wizard. You will have to manually tweak some things to make filestream and the local configuration of the sql server work nicely with aws RDS.

Generate and Publish Scripts Guide

  1. Go to the source database

  2. Right click the database in the menu on the left (Object Explorer) Tasks>Generate Scripts

  3. Select All tables, procedures, etc.. except for filestream tables.

  4. In the Scripts wizard pop up under Set Scripting Options, choose to make a .sql file, under advanced options, choose Schema Only. This will generate a script with only meta data for the tables and not the data in them

  5. Generate the file.

  6. Copy the .sql file over to the EC2 instance (probably the Bastion Host) that is connected to the RDS instance.

  7. Open MS SQL Management Studio and right click on the top most object in the Object Explorer and open a new query.

  8. Copy and paste the code inside the .sql file into the query window.

  9. Change the file path location of the data and log file to be D:\rdsdbdata\DATA\TEST_AWS.mdf and D:\rdsdbdata\DATA\TEST_AWS_Log.ldf  respectively. Any other file location will not be recognized by RDS and will fail to create the table.

  10. Comment or remove the lines of code that include:

    a. ALTER DATABASE [TEST_AWS] SET TRUSTWORTHY OFF  

    b. ALTER DATABASE [TEST_AWS] SET HONOR_BROKER_PRIORITY 

    c. ALTER DATABASE [TEST_AWS] SET DB_CHAINING OFF Creating global users

    d. FileStream

  11. Execute the Script

  12. Consider adding towards the top of the script DROP DATABASE [TEST_AWS] before the creation of the new database just in case you need to run the script multiple times to find the errors. This will save you from overwriting errors or having a unfinished table in memory.

Lacrosse343
  • 491
  • 1
  • 3
  • 18