Skip to main content
added 85 characters in body
Source Link

This is default behaviour for temporal tables, the history tables are PAGE compressed by default. thisThis is done out of space & performance considerations, compression will reduce the amount of data that has to be processed, both on disk & memory. This will have a tradeofftrade-off in extra cpuCPU cycles as SQL Server has to decompress the data. So unless you are under CPU pressure, compression is usually a good thing as your DISKdisk IO & Memorymemory usage improve.

More information on temporal tables: (https://learn.microsoft.com/en-us/sql/relational-databases/tables/temporal-table-considerations-and-limitations?view=sql-server-2017Temporal Table Considerations and Limitations)

For what SP_BlitzIndexsp_BlitzIndex page says about it:

https://www.brentozar.com/blitzindex/sp_blitzindex-abnormal-psychology/

Abnormal psychology findings aren’t necessarily problems– just look at this as a big FYI. Some implementations of indexes may mean that the database can only be restored in a certain edition of SQL Server, or they may change performance of some operations. Which apply to you? Check out details on your finding below.

Abnormal psychology findings aren’t necessarily problems– just look at this as a big FYI. Some implementations of indexes may mean that the database can only be restored in a certain edition of SQL Server, or they may change performance of some operations. Which apply to you? Check out details on your finding below.

So as stated above, this does not mean it is a problem. For the reasons described above.

This is default behaviour for temporal tables, the history tables are PAGE compressed by default. this is done out of space & performance considerations, compression will reduce the amount of data that has to be processed, both on disk & memory. This will have a tradeoff in extra cpu cycles as SQL Server has to decompress the data. So unless you are under CPU pressure, compression is usually a good thing as your DISK IO & Memory usage improve.

More information on temporal tables: (https://learn.microsoft.com/en-us/sql/relational-databases/tables/temporal-table-considerations-and-limitations?view=sql-server-2017)

For what SP_BlitzIndex page says about it:

https://www.brentozar.com/blitzindex/sp_blitzindex-abnormal-psychology/

Abnormal psychology findings aren’t necessarily problems– just look at this as a big FYI. Some implementations of indexes may mean that the database can only be restored in a certain edition of SQL Server, or they may change performance of some operations. Which apply to you? Check out details on your finding below.

So as stated above, this does not mean it is a problem. For the reasons described above.

This is default behaviour for temporal tables, the history tables are PAGE compressed by default. This is done out of space & performance considerations, compression will reduce the amount of data that has to be processed, both on disk & memory. This will have a trade-off in extra CPU cycles as SQL Server has to decompress the data. So unless you are under CPU pressure, compression is usually a good thing as your disk IO & memory usage improve.

More information on temporal tables: Temporal Table Considerations and Limitations

For what sp_BlitzIndex page says about it:

Abnormal psychology findings aren’t necessarily problems– just look at this as a big FYI. Some implementations of indexes may mean that the database can only be restored in a certain edition of SQL Server, or they may change performance of some operations. Which apply to you? Check out details on your finding below.

So as stated above, this does not mean it is a problem. For the reasons described above.

added 17 characters in body
Source Link
Stijn Wynants
  • 1.8k
  • 12
  • 18

This is default behaviour for temporal tables, the history tables are PAGE compressed by default. this is done out of space & performance considerations, compression will reduce the amount of data that has to be processed, both on disk & memory. This will have a tradeoff in extra cpu cycles as SQL Server has to decompress the data. So unless you are under CPU pressure, compression is usually a good thing as your DISK IO & Memory usage improve.

More information on temporal tables: (https://learn.microsoft.com/en-us/sql/relational-databases/tables/temporal-table-considerations-and-limitations?view=sql-server-2017)

For what SP_BlitzIndex page says about it:

https://www.brentozar.com/blitzindex/sp_blitzindex-abnormal-psychology/

Abnormal psychology findings aren’t necessarily problems– just look at this as a big FYI. Some implementations of indexes may mean that the database can only be restored in a certain edition of SQL Server, or they may change performance of some operations. Which apply to you? Check out details on your finding below.

So as stated above, this does not mean it is a problem. For the reasons described above.

This is default behaviour for temporal tables, the history tables are PAGE compressed by default. this is done out of space & performance considerations, compression will reduce the amount of data that has to be processed, both on disk & memory. This will have a tradeoff in extra cpu cycles as SQL Server has to decompress the data. So unless you are under CPU pressure compression is usually a good thing as your DISK IO & Memory usage improve.

More information on: (https://learn.microsoft.com/en-us/sql/relational-databases/tables/temporal-table-considerations-and-limitations?view=sql-server-2017)

For what SP_BlitzIndex page says about it:

https://www.brentozar.com/blitzindex/sp_blitzindex-abnormal-psychology/

Abnormal psychology findings aren’t necessarily problems– just look at this as a big FYI. Some implementations of indexes may mean that the database can only be restored in a certain edition of SQL Server, or they may change performance of some operations. Which apply to you? Check out details on your finding below.

So as stated above, this does not mean it is a problem. For the reasons described above.

This is default behaviour for temporal tables, the history tables are PAGE compressed by default. this is done out of space & performance considerations, compression will reduce the amount of data that has to be processed, both on disk & memory. This will have a tradeoff in extra cpu cycles as SQL Server has to decompress the data. So unless you are under CPU pressure, compression is usually a good thing as your DISK IO & Memory usage improve.

More information on temporal tables: (https://learn.microsoft.com/en-us/sql/relational-databases/tables/temporal-table-considerations-and-limitations?view=sql-server-2017)

For what SP_BlitzIndex page says about it:

https://www.brentozar.com/blitzindex/sp_blitzindex-abnormal-psychology/

Abnormal psychology findings aren’t necessarily problems– just look at this as a big FYI. Some implementations of indexes may mean that the database can only be restored in a certain edition of SQL Server, or they may change performance of some operations. Which apply to you? Check out details on your finding below.

So as stated above, this does not mean it is a problem. For the reasons described above.

Source Link
Stijn Wynants
  • 1.8k
  • 12
  • 18

This is default behaviour for temporal tables, the history tables are PAGE compressed by default. this is done out of space & performance considerations, compression will reduce the amount of data that has to be processed, both on disk & memory. This will have a tradeoff in extra cpu cycles as SQL Server has to decompress the data. So unless you are under CPU pressure compression is usually a good thing as your DISK IO & Memory usage improve.

More information on: (https://learn.microsoft.com/en-us/sql/relational-databases/tables/temporal-table-considerations-and-limitations?view=sql-server-2017)

For what SP_BlitzIndex page says about it:

https://www.brentozar.com/blitzindex/sp_blitzindex-abnormal-psychology/

Abnormal psychology findings aren’t necessarily problems– just look at this as a big FYI. Some implementations of indexes may mean that the database can only be restored in a certain edition of SQL Server, or they may change performance of some operations. Which apply to you? Check out details on your finding below.

So as stated above, this does not mean it is a problem. For the reasons described above.