SQL Server Compression Estimator

Source code checked in, #19253

Project Collection Service Accounts — Mon, 01 Oct 2012 20:30:36 GMT

Upgrade: New Version of LabDefaultTemplate.xaml. To upgrade your build definitions, please visit the following link: http://go.microsoft.com/fwlink/?LinkId=254563

Source code checked in, #19252

Project Collection Service Accounts — Mon, 01 Oct 2012 20:28:45 GMT

Checked in by server upgrade

Patch Uploaded: #12241

ahribernik — Fri, 18 May 2012 05:16:45 GMT

ahribernik has uploaded a patch.

Description:
- changed table name filter to be case insensitive
- included Patch 11883 by philcart

New Post: "Cannot specify partition number in the alter index statement as the index is not partitioned."

sanathkura — Tue, 08 May 2012 12:41:49 GMT

"Cannot specify partition number in the alter index statement as the index is not partitioned."

When i queried Sys.partitions table for the table name i could get multiple rows so i had rebuilt below syantax

alter index <Indexname1> on <tablename>
rebuild partition = 1

But recieve the error "Cannot specify partition number in the alter index statement as the index is not partitioned."

I had removed partition =1 from alter index and rebuild the index but when i check the fragmentaation level on physical _io_stats, i could find the fragmentation level >50.

Need help to defragment the table.

Details: SQL Server 2005
Indexes : two indexes
Query on sys.partitions for table : 2 rows

New Post: Error applying the automatic scripting

sanathkura — Tue, 08 May 2012 12:38:06 GMT

I am also getting the same error as above

"Cannot specify partition number in the alter index statement as the index is not partitioned."

When i queried Sys.partitions table for the table name i could get multiple rows so i had rebuilt below syantax

alter index <Indexname1> on <tablename>
rebuild partition = 1

But recieve the error "Cannot specify partition number in the alter index statement as the index is not partitioned."

I had removed partition =1 from alter index and rebuild the index but when i check the fragmentaation level on physical _io_stats, i could find the fragmentation level >50.

Need help to defragment the table.

Details: SQL Server 2005
Indexes : two indexes
Query on sys.partitions for table : 2 rows

Patch Uploaded: #11883

philcart — Mon, 02 Apr 2012 07:25:15 GMT

philcart has uploaded a patch.

Description:
Set Anchor properties so DataGrid resizes with form.
Added filter for table name.
Fixed some errors with SQL scripts.
Add 'Raiserror' notification messages to generated script.
Added statusbar with progress indicators.

Created Issue: Divide by zero error encountered [536]

aaditya2000 — Thu, 15 Dec 2011 18:43:29 GMT

Hello:

This is an excellent tool & thank you for provding this tool to SQL Community.

When i run this tool, intermitently i am getting popup window saying "Divide by zero error encountered".

Any resolution to this error or latest version is greatly appreciated.

Thanks
Regards
Jay

New Post: Divide by zero error encountered

aaditya2000 — Thu, 15 Dec 2011 18:38:55 GMT

New Comment on "Documentation"

aaditya2000 — Thu, 15 Dec 2011 18:36:33 GMT

Hello: This is an excellent tool & thank you for provding this tool to SQL Community. When i run this tool intermitently i am getting popup window saying "Divide by zero error encountered". Any resolution to this error or latest version is greatly appreciated. Thanks Regards Jay

New Post: Divide By Zero Error

YvesA — Tue, 22 Nov 2011 16:43:15 GMT

Same here ... also not every tables were evaluated and only in the schema dbo.

New Post: Divide By Zero Error

SwePeso — Tue, 20 Sep 2011 13:23:16 GMT

I get a lot of these when processing my tables.

New Post: Row compression?

majikbybob — Mon, 18 Jul 2011 16:38:39 GMT

It tries both ROW and PAGE. Depending upon which row in the grid you click you can choose to implement ROW or PAGE. IF all you are getting is PAGE as a possibility, then I need to investigate :)

boB

Reviewed: Error 207 Invalid column name (Jul 07, 2011)

kkline84 — Thu, 07 Jul 2011 22:21:32 GMT

Rated 5 Stars (out of 5) - A very useful and direct utility that helps you quickly analyze whether data compression will be useful on your SQL Server database, and then creates the scripts to implement data compression.

New Post: Row compression?

kkline84 — Thu, 07 Jul 2011 22:19:16 GMT

Hi Bob,

Very nice utility! I'm even doing a write-up for SQL Server Magazine about it.

I noticed that all of the scripts produce PAGE compression. Any plans to support ROW compression in the future? Since this is a simple switch in sp_estimate_data_compression_savings, I wondered if you might support that level of analysis as well?

In the category of "cool & nice, but not necessary", it'd be useful to be able to do blanket specification of certain types of objects, such as only tables, only clustered indexes, only indexed views, etc. Again, not necessary, but could be very useful in a big schema.

Also, a couple behavioral oddities. First, the column sorts seemed a little weird. For example, if I clicked to sort on the Current Size (KB) column, it didn't always come out in correct sorted order. Lastly, although the tool is resizable, it doesn't appear that the column window itself is. So I could drag the tool out to fit all of the columns into view, but the column window remained the same size hiding a couple columns.

All in all, a great tool!

Thanks,

-Kevin Kline

Twitter at @kekline

kevin.kline@quest.com

Created Issue: Numerical column data sorts as character within the GUI [342]

JohnSansom — Sun, 05 Jun 2011 10:01:19 GMT

When the results of the analysis are presented within the Compression Calculator GUI, the numerical columns such as current size and % savings etc. are sorted as text values when the column header is clicked.

This is a very minor and aesthetic point that of course becomes irrelevant once data is exported to another application/tool for review.

I would also like to say that I think this is a fantastic tool by the way and I certainly appreciate the development efforts. Keep up the great work!

New Post: Columns with imbedded ampersand (&)

majikbybob — Thu, 02 Jun 2011 12:29:42 GMT

There appears to be a defect in the system stored procedure that provides the estimate of savings for compression. It does not correctly handle the case you have identified. I am filing a bug with the Product Team. Until then I can't fix this one. I did provide a minor release that at least gives a more meaningful message to the user. Thank you for your feedback.

boB

Created Release: Error 207 Invalid column name (Jun 02, 2011)

majikbybob — Thu, 02 Jun 2011 12:27:51 GMT

There appears to be a defect in the sp_estimate_data_compression_savings system stored procedure if you have a table with a column that does not conform to the rules for regular identifiers. According to Books Online, for identifiers that do not conform to the rules, those identifers must be enclosed in double quotes or square brackets. This action is not being performed by the system stored procedure. As such, if you process a table with a non-regular identifier as a column name youi will receive an Error 207 Invalid column name. Calls to COL_NAME resolve correctly, so it appears to be a problem only in this stored procedure.

I am filing a bug with the Product Team.

This release just provides a bit more meaningful feedback to the user when this condition occurs.

Released: Error 207 Invalid column name (Jun 02, 2011)

Thu, 02 Jun 2011 12:27:51 GMT

Source code checked in, #8167

MajikbyboB — Thu, 02 Jun 2011 12:10:36 GMT

If a column name has embedded special characters, sp_estimate_data_compression_savings will throw a 207 error. Notify the user

New Post: Columns with imbedded ampersand (&)

majikbybob — Thu, 02 Jun 2011 11:34:43 GMT

I'll take a look at it. Do you use QUOTED IDENTIFIERs in this database? Also, is it during the processing, or the script creation, or the execution of the script that this error occurs?

boB