Primavera P6 Hosting with Microsoft SQL Server
When Primavera P6 uses Microsoft SQL Server, the application and database should be planned together. Performance, maintenance and recovery depend on how those components interact. For access from several locations in Europe, include the database connection in performance tests.
Check compatibility before sizing
Identify the installed P6 release and verify the suitable SQL Server version against the product documentation for that installation. Record database size, growth, concurrent users and common queries. Those facts provide a useful starting point for a test environment. Generic processor or memory figures cannot replace measurements using the team’s actual projects and reporting workload.
Measure the application to database connection
P6 may issue many short database requests. Server capacity therefore matters alongside the connection between the application and database tiers. Test opening large projects, applying filters, posting updates and running reports from normal user locations. A distant database or congested connection can make the interface feel slow even when each server appears to have spare resources.
Assign operating responsibilities
Specify who monitors database health, storage, maintenance jobs and failed backups. Changes to SQL Server, the operating system and P6 should be assessed together and rehearsed in a test environment. Where a service provider is involved, write down the boundary between database administration, application operations and planning support. Otherwise an incident can sit between teams without a clear owner.
Test a usable restore
A database backup alone does not prove that a usable P6 environment can be recovered. Restore the required application components, configuration and integrations in a test. Record the recovered data point and the time taken. If several databases or connected systems are involved, determine which backup points belong together so that project information remains consistent.
Frequently asked questions
Is a fast SQL Server enough for good P6 performance?
Not necessarily. Application servers, network latency, data design and the actual workload also affect response times. Test representative tasks with realistic data.
What should a SQL Server recovery test cover?
Restore a usable P6 environment, then check login, selected projects and relevant integrations. Record the recovered data point and elapsed time.
Need help with your project schedule? Explore our project planning services.