Solution : https://service.sap.com/sap/support/notes/327494 (SAP Service marketplace login required)
Key words :
exec sp_autostats vbhdr exec sp_autostats vbdata exec sp_autostats vbmodeach, havingcomputer asmemory memsize sql server parameters windows params {, } minmb maxmb setws awe network priority /3gb /pae, implies dynamic memory consumption} <setws> = 0 <awe> = 0 {disabled}, implies dynamic memory consumption} <setws> = 0 <awe> = 0 {disabled}, managing 32-bit sql server memory involves consideration, sql server service configuration sql server service configuration, empirical contraindicative data suggests alternative configuration, physical main memory <setws> = 0 <awe> = 0 {disabled} sap, physical main memory <setws> = 0 <awe> = 0 {disabled} sap
Related Notes :
| 986907 | SQL Server settings for R3load based system copy |
| 879941 | Configuration Parameters for SQL Server 2005 |
| 766827 | Composite SAP note: Performance SCM 4.0 |
| 567745 | Composite note BW 3.x performance: DB-specific setting |
| 497446 | Upgrading to SQL 2000 stops when executing Upgrade.sql |
| 401836 | Migration Oracle 8.1.7 => SQL Server 2000 |
| 209596 | Setting up Microsoft SQL Server 2000 |
| 193816 | Restore with SQL Server |
| 126808 | Configuration parameter for SQL Server 7.0 |