Skip to main content
Post Closed as "Needs more focus" by Philᵀᴹ, RDFozz, Colin 't Hart, Marco, mustaccio
edited tags; edited tags
Source Link
user1822
user1822

In the company I worked:

MSSQL database has previuslypreviously been archivearchived on another database. Approximately 70m rows. (Includesincludes sales information.)

Now, I am asked to move these archivethis archived data to live database. Because, we customer can't see order history older the 3 years.

Is it reasonable to do this? I think it will be slow. Are there other solutions?

Live DB size : 250GB

Archive DB size : 50GB

CPU : 8 Core

Memory : 64GB

Version : Microsoft SQL Server 2016 (SP1)

  • Live DB size : 250GB
  • Archive DB size : 50GB
  • CPU : 8 Core
  • Memory : 64GB
  • Version : Microsoft SQL Server 2016 (SP1)

In the company I worked:

MSSQL database has previusly been archive on another database. Approximately 70m rows. (Includes sales information.)

Now, asked to move these archive data to live database. Because, we customer can't see order history older the 3 years.

Is it reasonable to do this? I think it will be slow. Are there other solutions?

Live DB size : 250GB

Archive DB size : 50GB

CPU : 8 Core

Memory : 64GB

Version : Microsoft SQL Server 2016 (SP1)

MSSQL database has previously been archived on another database. Approximately 70m rows (includes sales information.)

Now, I am asked to move this archived data to live database. Because, customer can't see order history older the 3 years.

Is it reasonable to do this? I think it will be slow. Are there other solutions?

  • Live DB size : 250GB
  • Archive DB size : 50GB
  • CPU : 8 Core
  • Memory : 64GB
  • Version : Microsoft SQL Server 2016 (SP1)
Source Link
Yunus UYANIK
  • 1.1k
  • 1
  • 10
  • 27

Retrieve archived data

In the company I worked:

MSSQL database has previusly been archive on another database. Approximately 70m rows. (Includes sales information.)

Now, asked to move these archive data to live database. Because, we customer can't see order history older the 3 years.

Is it reasonable to do this? I think it will be slow. Are there other solutions?

Live DB size : 250GB

Archive DB size : 50GB

CPU : 8 Core

Memory : 64GB

Version : Microsoft SQL Server 2016 (SP1)