question

JoannLiao-4647 avatar image
0 Votes"
JoannLiao-4647 asked Criszhan-msft commented

Upgrade SQL server 2017 from 2014


349748, it was my first ticket posted on msdn. Need your expertise.

I had tried couple times upgrading SQL server to 2017 from 2014.

  1. Stop SQL server reporting server,
    Please confirm whether this step is mandatory while upgrading. Or, It's automatically migrated via setup /SqlSetup_x64_ENU. Correct?

  2. Full-text Upgrade. Which option it keep all the original Full-text catalogs?
    Choose a full-text upgrade option?
    Import
    Rebuild
    Reset

  3. Data Collection and Resource Governor become disable after upgraded. Please advise.

88883-image.png






Thank you.

sql-server-general
image.png (160.8 KiB)
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi,

Is there any update on this case?
If the answer is helpful, please kindly click "Accept Answer" and upvote it.

0 Votes 0 ·

1 Answer

Criszhan-msft avatar image
0 Votes"
Criszhan-msft answered ErlandSommarskog commented

Hi,

Stop SQL server reporting server, Please confirm whether this step is mandatory while upgrading. Or, It's automatically migrated via setup /SqlSetup_x64_ENU. Correct

Quoting from the document-Upgrade and Migrate Reporting Services:

Upgrade to Reporting Services 2017 and later from Reporting Services 2016 and older isn’t the same upgrade scenario as in previous versions. When upgrading to Reporting Services 2016 and older versions, you could following an in-place upgrade process using SQL Server installation media. When upgrading to Reporting Services 2017 and later from Reporting Services 2016 and older, you can’t follow the same steps because the new Reporting Services installation is a standalone product. It's no longer part of the SQL Server installation media.

2.Full-text Upgrade. Which option it keep all the original Full-text catalogs?

Import. An imported full-text catalog does not use the new word breakers installed with the latest version of SQL Server. To ensure consistency in query results, full-text catalogs have to be rebuilt.
https://docs.microsoft.com/en-us/sql/relational-databases/search/upgrade-full-text-search?view=sql-server-ver15#FT_Upgrade_Options

3.Data Collection and Resource Governor become disable after upgraded.

These features are disabled by default.

· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.


A little bit confused.

Criszhan-msft

1.

"When upgrading to Reporting Services 2017 and later from Reporting Services 2016 and older, you can’t follow the same steps because the new Reporting Services installation is a standalone product. It's no longer part of the SQL Server installation media"


Upgrade SQL Server 2017 from 2014, please let me know what steps should be followed, or give me a reference link address.


2.

What should be import? What file was referring to? How? and what's the step to generate the file

Please clarify

Thank you.

0 Votes 0 ·

So did you try the link that Cris dropped in his article? I did, and in that topic, I quickly found a link to https://docs.microsoft.com/en-us/sql/reporting-services/install-windows/migrate-a-reporting-services-installation-native-mode?view=sql-server-ver15 and it starts off This topic provides step-by-step instructions for migrating one of the following supported versions of a Reporting Services native mode deployment to a new SQL Server Reporting Services instance:. I don't use Reporting Services myself, but I like to imagine that topic answers you questions.

As for full-text, I normally go for "rebuild". I looked at the topic that Cris referred to, and it seems that this is mainly a matter if you come from SQL 2005, which you don't. Do you have any full-text indexed databases in the first place?


1 Vote 1 ·