First published on MSDN on Aug 22, 2009
First of all apologies for not being more active on our blogs site for the last two months. Reason is that we are in the usual annual review phase and also went through a reorganization. Therefore I was pretty busy.
Nevertheless I was able to spend some time improving the stored procedure one can use for applying SQL Server Database Compression to SAP or non-SAP databases. Attached to this blog you can find the new release of the sp_use_db_compression script where I fixed one bug and added another feature. Working with a customer, it figured out that the procedure didn’t work when it was created in the dbo schema and the SAP schema was in the <sid> schema. Even the option @schema set to the value ‘ALL’ did not work. This is corrected in the new version attached.
There was another request from one of our customers. They wanted to have all the T-SQL commands for executing compression stored in a table. But they didn’t want to have the compression executed. So what I implemented is a new option called @write_verbose_table. Setting this option to a value of 1 and also having the option @verbose_only set to a value of 1 will go through the tables, just create the T-SQL commands and write all the commands into a table sp_use_db_compression_sql_commands. This table is created in the same schema the stored procedure sp_use_db_compression resides in.
There will be another version of the procedure within the next two months. The procedure will deal with a specific case for SQL Server 2008 R2. But more about SQL Server 2008 R2 in the next Blog entry
sp_use_db_compression_22.sql
