SQL Server 2019: Creating new database fails and ends up with “invalid column name: is accelerated database recovery on” (error 207),

Question

SQL Server 2019: Creating new database fails and ends up with “invalid column name: is accelerated database recovery on” (error 207),

Jamal NUMAN 46

I couldn’t figure out why creating new database fails and ends up with “invalid column name: is accelerated database recovery on” (error 207).

What could be the issue here?

Answer 1

Hi @Jamal NUMAN ,

SSMS 18.7.1 is the latest version of SSMS, we suggest you using it.

SQL server 2019 RTM has been released for a long time, please uninstall the SQL Server 2019 CTP 2.2 (Community Technology Preview 2.2)( 15.0.1200.24), install SQL server 2019 RTM and apply CU8 for SQL 2019 as others mentioned.

Download SQL server 2019 RTM.
Cumulative Update 8 for SQL Server 2019

You can follow the steps from this document to uninstall SQL 2019 CTP2.2.
Uninstall an Existing Instance of SQL Server (Setup)

Best regards,
Cathy

If the response is helpful, please click "Accept Answer" and upvote it.

Answer 2

The problem is that you are running a preview version of SQL 2019, one which apparently predates the introduction of Accelerated Database Recovery.

Uninstall your preview version and install the released version. Also do not forget to apply the most recent Cumulative Update, which is CU8.

If you have database you want to keep, you will need to script them and bulk out the data. As I recall, there were breaking changes around CTP 3.0, you will not be able to restore backups on the released version.

Answer 3

Jamal NUMAN 46

Thanks Erland,

I just uninstalled the mamagment studio 18.7.1 and replaced it with 18.3.1 and it works fine

Sure. I’ll be using the released version instead of the preview later

Ronen Ariely 14,141 Reputation points MVP

2020-12-06T23:30:42.767+00:00

Hi,

It is a bit difficult to know who is in the other side of the screen in the forum, so I am sorry If this is not relevant, but it seems in first glance that you have a confusion between the server and the client tool. No?

JamalNUMAN-7082: I just uninstalled the mamagment studio 18.7.1 and replaced it with 18.3.1 and it works fine

This is not related to the server but to a client application which can be installed in the same machine or in totally different machine.

Note! According to your image you are using version 15.0.1200.24 which is Microsoft SQL Server 2019 Community Technology Preview 2.2 (CTP 2.2). This is a very old version of the server from 2018-12-11. Check this list.

Using old version of the SSMS is not a solution, but in the best case only a way to bypass a behavior.

You should probably use the newest release version of SQL Server and the newest version of the SSMS . It is highly important.
Erland Sommarskog 72,416 Reputation points MVP

2020-12-07T22:38:44.59+00:00

It is a bit difficult to know who is in the other side of the screen in the forum, so I am sorry If this is not relevant, but it seems in first glance that you have a confusion between the server and the client tool. No?

My interpretation is Jamal got the message of my post, but instead following my advice, he applied the "workaround" of downgrading to a version of SSMS that does not use this column. I will have to admit that I shook my head in disbelief when I read this.

I realise that Jamal may be in a hurry to produce something, and therefore decided to defer installing the RTM version of SQL 2019. But I like to point out again: you may not be able to upgrade these databases to SQL 2019 RTM! So you are just digging deeper into the hole.

Answer 4

Jamal NUMAN 46

Thank you guys for the help
best
Jamal

CathyJi-MSFT 20,786 Reputation points Microsoft Vendor

2020-12-08T01:30:27.417+00:00

Hi @Jamal NUMAN ,

Still suggest you using SQL 2019 CU8, the latest version.

By the way, If the responses helped, do "Accept Answer". By doing so, it will benefit all community members who are having this similar issue. Your contribution is highly appreciated.

Best regards,
Cathy

SQL Server 2019: Creating new database fails and ends up with “invalid column name: is accelerated database recovery on” (error 207),

3 additional answers

Activity