![]() It's impossible to not upgrade because the current version of server needs that new structure for db files.Īll speculations around compatibility level / read_only property will not help at all, current server will never run with files that are not of the structure it needs. And if you restore or attach database from lower version db files are one-way updated to have a structure that the current version of SQL Server needs. ![]() Every version of SQL Server has its data and log files structure that differs between server versions. Upgrade step from version 868 to version 869. When the above runs I get: Database 'Polly' running the upgrade stepįrom version 782 to version 801. Would like to see no upgrade steps, but only if database still usable. If anyone has general improvements to above I am happy for suggestions.ĭatabase 'Polly' running the upgrade step from version 782 to version 801.ĭatabase 'Polly' running the upgrade step from version 868 to version 869. RESTORE DATABASE Polly FROM DISK = 'C:\data\Polly.bak' ![]() Have been looking through T-SQL documentation and not found this referred to. Is it possible to run the RESTORE without the database getting upgraded? This is a problem as I wish to modify the database and then do a backup which then gets transferred and restored to another system which is using the same earlier version of MS SQL. ![]() However during the restore the database gets upgraded to the current version. I am successfully doing a daily restore of a backup from an earlier version onto MS SQL 2017 using T-SQL. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |