Index Reorganise failure: minionware
-
hi
I have been using the great indexing tool from minionware as per advice from a previous post here
http://minionware.net/reindex/
but randomly the reorganise/reindex fails, always with the same error
Executed as user: NT SERVICE\SQLSERVERAGENT. Parameter 3 is incorrect for this statement. [SQLSTATE 42000] (Error 2561) The statement has been terminated. [SQLSTATE 01000] (Error 3621) Parameter 3 is incorrect for this statement. [SQLSTATE 42000] (Error 2561) The statement has been terminated. [SQLSTATE 01000] (Error 3621) Parameter 3 is incorrect for this statement. [SQLSTATE 42000] (Error 2561) The statement has been terminated. [SQLSTATE 01000] (Error 3621) Parameter 3 is incorrect for this statement. [SQLSTATE 42000] (Error 2561) The statement has been terminated. [SQLSTATE 01000] (Error 3621). The step failed.
as far as I can make out, par 3 is simply
@RunPrepped = 0, -- Valid options: 1, 0. If you've collected index frag stats ahead of time by running with @ Prep Only = 1, then you can use this option.
has anyone else had this issue? (I am on the latest version of minionware reindex)
-
I love this software. I haven't hit this issue, but I've alerted Jenn & Sean. I suspect one or both will swing by shortly to help you out.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore RooseveltAuthor of:
SQL Server Execution Plans
SQL Server Query Performance Tuning -
thanks Grant, I agree great software which removes so much hassle for me!
-
Thanks for the heads up Grant.
Yeah, I've seen this issue before and I think you're on an older version.
Ping me in email and we'll do the needful.
Watch my free SQL Server Tutorials at:
http://MidnightDBA.com
Blog Author of:
DBA Rant – http://www.MidnightDBA.com/DBARantMinion Maintenance is FREE:
-
Just wanted to let you guys know how this turned out.
I already had the issue fixed in the upcoming release. The issue is that when some table or index names have certain special chars in them, the brackets we were using weren't encapsulating the name properly so it gave an error when we called the physical_stats dmv. So in this upcoming release we've switched to double quotes around the object names and that fixes the issue.
If anyone else has this immediate issue then email me and i'll send you the pre-release version and you'll be golden.
Also, while I certainly don't mind (mostly because Grant pings me), but this isn't really the forum for bug reports. Instead, go through our support at http://www.MinionWare.net.
We usually respond within just a few mins.
Watch my free SQL Server Tutorials at:
http://MidnightDBA.com
Blog Author of:
DBA Rant – http://www.MidnightDBA.com/DBARantMinion Maintenance is FREE:
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply