How to Prevent Selection of the nvarchar Data Type When Creating Table 1

[JohnBates]

hello again,

This post is sort of related to another thread javascriptpenindex(450,350,'

http://www.tipmaster.com/includes/refinfo.cfm?w=450&h=350')

but not directly.

I would love to be able to remove the nvarchar data type from the drop-down list of available data types to choose from when creating/changing a table. There must be a way to edit the system tables to accomplish this.

Someone please help me before I go postal/machine-gun!

Thanks John, frustrated DBA

 

[JohnBates]

well... obviiously I dont know how to copy and paste a Thread number

 

[JohnBates]

hmmm..
The spt_provider_types table in .master looks promising. The data types are there. I wonder what column 'Best_Match' is for?

(This is 2000 SP3)

John

 

[SQLSister]

And then what happens when you run across a situation where you need nvarchar? If your developers can't be trusted to follow your rules, then take away their priviledges.

Questions about posting. See faq183-874

 

[Corran007]

agreed.i would be very carful about trying to remove them. what happens if a microsoft patch has need of the datatype?

fixing it on the user side is the best course of action. if the users wont follow the rules, you take away their privilages. but make sure you have a written policy on it and sign that they have read it. that way they cannot say they did not know.

 

[SQLSister]

Corran007, you make an excellent point. As it stands Microsoft does use nvarchar for many of its system procedures. It could be quite dangerous to try to remove nvarchar as a datatype.

Questions about posting. See faq183-874

 

[JohnBates]

OK... OK I won't disable nvarchar

now, where did I put that gun?

John

(Thanks for prodding me to reconsider my rather exterme solution.)

 

[SQLSister]

Ok how about another solution. I presume your developers are not developing on production and therefore the only people who will be hurt with this solution will be developers. Tell them that anytime from now on that you see a table with an nvarchar field defined on a development database you are going to drop the table. Probably only take one or two dropped tables before they come around to your way of thinking. It's cheaaper than bullets and less likely to lead to prison time. But don't do this on production. And make a backup first, so you can recreate the table after they whine a bit.

Questions about posting. See faq183-874