ssce Discussions Rss Feed

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

New Post: Divide by zero error encountered

aaditya2000 — Thu, 15 Dec 2011 18:38:55 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

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

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

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

New Post: Columns with imbedded ampersand (&)

ShaunLombard — Thu, 02 Jun 2011 03:19:24 GMT

boB,

This is shaping up to be a great tool - Thanks.

I am receiving an unhandled exception error when I run against a database that contains & characters in the column name.

Error as follows:

Invalid column name 'OrgESA_13WkFull&Path_Outcomes'.

Regards,

Shaun

New Post: Error applying the automatic scripting

masteroz — Thu, 26 May 2011 13:20:00 GMT

Thank you very much. The problem was solved. Congratulations for your program

New Post: Error applying the automatic scripting

majikbybob — Mon, 23 May 2011 17:47:39 GMT

Thank you - the script generation code was incorrectly identifying whether or not an indexe was partitioned and was emitting the wrong script fragment.

This has been corrected in V1.0.3.0

New Post: Error applying the automatic scripting

masteroz — Mon, 23 May 2011 10:23:19 GMT

Hello.

I will be alert during the week

Thank you

From: [email removed]
To: [email removed]
Date: Mon, 23 May 2011 02:29:09 -0700
Subject: Re: Error applying the automatic scripting [ssce:257929]

From: majikbybob

I am working on this now. I hope to have an update available by the end of the week.

Read the full discussion online.
To add a post to this discussion, reply to this email (ssce@discussions.codeplex.com)
To start a new discussion for this project, email ssce@discussions.codeplex.com
You are receiving this email because you subscribed to this discussion on CodePlex. You can unsubscribe on CodePlex.com.
Please note: Images and attachments will be removed from emails. Any posts to this discussion will also be available online at CodePlex.com

New Post: Error applying the automatic scripting

majikbybob — Mon, 23 May 2011 09:29:08 GMT

I am working on this now. I hope to have an update available by the end of the week.

New Post: Error applying the automatic scripting

masteroz — Fri, 20 May 2011 08:25:03 GMT

Thank you, with the new vesion I get the following error:

Msg 7735, Level 16, State 1, Line 5

Cannot specify partition number in alter table statement to rebuild or reorganize a partition of table 'colectivos' as table is not partitioned.

New Post: Error applying the automatic scripting

masteroz — Wed, 18 May 2011 13:02:59 GMT

Thank you very much.

From: [email removed]
To: [email removed]
Date: Tue, 17 May 2011 15:31:49 -0700
Subject: Re: Error applying the automatic scripting [ssce:257929]

From: majikbybob

I will take a look at this and see what is going on. Every object always has at least one partition... I may have to tweak the script - but I shouldn't have to.
Thanks for the continuing feedback.
boB

New Post: Error applying the automatic scripting

majikbybob — Tue, 17 May 2011 22:31:48 GMT

I will take a look at this and see what is going on. Every object always has at least one partition... I may have to tweak the script - but I shouldn't have to.

Thanks for the continuing feedback.

boB

New Post: Error applying the automatic scripting

masteroz — Tue, 17 May 2011 14:03:11 GMT

Hello again. This version solves many issues (resize form, typing Server name...) but I cannot apply the script created with SQL Server Compression Estimator because in all cases I get the following error:

-- This compression script was created by Compression Estimator

-- By applying PAGE compression setting, you should obtain
-- approximately 20,00% compression
ALTER TABLE [Sales].[SpecialOfferProduct]
REBUILD PARTITION = 1
WITH (DATA_COMPRESSION = PAGE);

-- By applying PAGE compression setting, you should obtain
-- approximately 44,66% compression
ALTER TABLE [Sales].[Store]
REBUILD PARTITION = 1
WITH (DATA_COMPRESSION = PAGE);

The database is AdventureWorks2008R2

The error in all cases is

Msg 7729, Level 16, State 1, Line 5

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

Thank you very much

New Post: Thank you

majikbybob — Fri, 13 May 2011 14:26:39 GMT

Thanks for the feedback. I have incorporated the requested enhancements and they are now available in Version 1.0.1.0

boB

New Post: Thank you

majikbybob — Fri, 13 May 2011 14:26:39 GMT

Thanks for the feedback. I have incorporated the requested enhancements and they are now available in Version 1.0.1.0

boB