On the SQL 2012 server we are hitting:

Developer Edition (64-bit)11.0.2332.0RTM

On the SQL 2008 server we are hitting:

Standard Edition (64-bit)10.0.5770.0SP3

opc.three (10/2/2012)

---

I cannot recreate the issue. Maybe it has been fixed. Here is the SQL I see when I script the 500-column VIEW as an ALTER:

It looks like it is...

opc.three (10/1/2012)

---

If you have the time and inclination to provide proof-of-concept code that could be used on any instance to reproduce the issue it would be helpful to the community...

opc.three (10/1/2012)

---

I would venture a guess that a difference in SMO for 2012 is the source of the trouble. Have you changed any of the standard scripting options in SSMS...

Hey!

Well, I figured it out... I guess you need to have:

exit [/b] [ExitCode]

As the last line of the batch file.

Works like a charm!

Hey!

Also, the method racosta posted, and the method I posted should produce identical query plans... it just depends on how you want to do it!

 

Hey!

SELECT COUNT( DISTINCT [FieldA] ) FROM Table1

Hope this helps!

Hey!

I mean the application administrator uses the app to create the indexes... its not ideal, but thats the way it works.

The people administering the application know nothing of SQL, and...

Hey!

They need to create indexes because it is a requirement of the application. 

There are hundreds of columns of data, but not all of them can...

Hey!

Yeah, I guess we can only do what SQL allows... if we there is no way, then I guess we will have to look at changing what we do for...

Hey!

Unfortunately I cant try the stored procedure way, as the code is already written to do the indexing, and it currently uses an account that has full permissions to everything (sa).

Hey!

BOL is the first place I looked.  From what I read, it doesnt look like you can GRANT index permissions.

Thanks for any additional help!

Hey!

OK... I need a user that isnt the owner to be able to create indexes... I added the user to db_ddladmin, but that gived that user way too much power......

Well that kind of sucks!

Thanks for the info !

Paul

Hey!

We connect from an ASPX web page using SQL Authentication.  Its just a typical looking connection string:

server=SERVER1;uid=user_name;pwd=password;database=DATABASE_NAME

Thanks, Ill check out that link right away and see if it applies!

Paul