Separate PCS 7 SQL Data and Log Storage Without Assuming Installer Support

SQL Server supports relocating user-database files, but that does not establish that PCS 7 setup can reuse an arbitrary instance, accept altered unattended-installation parameters, or tolerate relocated application databases. Identify the exact PCS 7 and SQL components before choosing a storage change. No installation-specific support for those three proposed approaches has been established. The documented SQL relocation sequence below explains the closest database operation and its limits, rather than authorizing a PCS 7 modification.

Identify the Installation and Storage Scope

The installation is described as PCS 7 installing a SQL Server Express instance, without a PCS 7 version, SQL edition/build, station role or database inventory. Treat Express as a reported description, not a confirmed component identity.

For example, the opened PCS 7 Readme V8.2, section 3.4, documents system setup installing SQL Server 2014 SP1. That release-specific statement illustrates why the exact installation must be identified; it does not determine what another PCS 7 release installs. See the V8.2 readme.

Separate the SQL program/instance installation path, system-database files, user-database data files, transaction logs and application-managed archives. Changing one location does not establish that the others moved.

Compare the Three Proposed Approaches

Proposed changeWhat is establishedWhat remains unresolvedReuse a preinstalled SQL instanceSQL instances are distinct deployment contextsPCS 7 detection, required instance settings and release supportAlter setup parameters or make SQL setup interactiveNo applicable PCS 7 procedure was establishedSupported installer interface and consequences for system setupMove files after installationMicrosoft documents user-file relocation within an instancePCS 7 dependencies, supported database scope and recovery behavior

Do not edit copied setup files or replace the required instance to satisfy a storage policy without applicable product evidence. Record the compliance requirement and request a supported storage design for the actual station and release.

Documented SQL Relocation Sequence

Microsoft's Move user databases procedure applies to user-database files within the same SQL instance. It is not a PCS 7 authorization or a system-database relocation procedure.

Identify the database's logical file names and existing paths through sys.master_files. Ensure the SQL service account can access the destination.
Use ALTER DATABASE ... MODIFY FILE to record each intended new location.
Take the database offline during the planned outage. Exclusive access is required; handle connected applications through their supported shutdown process.
Move the identified files, then bring the database online.
Verify the paths and database state in sys.master_files.

These are the manufacturer's SQL-level stages. A DBA must prepare the concrete commands for the identified files and approved product configuration. No forced-disconnection command is prescribed for a live control-system database.

Verification

For an approved change, inspect both database state and physical file locations, then verify the PCS 7 functions that use the database. Include the required archive writing, retrieval and project-opening checks for the station's actual role.

A database reporting online does not prove that application services, backup or recovery remain correct. Record the before/after file inventory and the application acceptance results.

Limitations and Operational Precautions

The central PCS 7 compatibility questions remain unanswered. The SQL reference does not prove that an application ignores storage changes; the application's own path handling and lifecycle requirements need evidence.

Preserve recoverable application and database backups, retain the original file mapping, and plan outage and rollback before an approved relocation. Do not move live files in File Explorer while the database remains in use.

No exact SQL edition, data path, installer switch or supported PCS 7 workaround is invented.

Engineer FAQ

Can an arbitrary preinstalled instance be assumed usable? No applicable PCS 7 evidence establishes that.

Does moving user files relocate SQL's installation directory? No; those are different scopes.

Is the Microsoft procedure sufficient for production PCS 7 approval? It needs application-specific support and acceptance evidence.

Technical References

Related Tags

SQL Server

PCS 7

20 respuestas

Separate PCS 7 SQL Data and Log Storage Without Assuming Installer Support