Are ADT's compatible with the current release of Visual Studio .NET?
A couple years ago I had done some C# programming with .NET 2003 and a SS2000 db that used UDT's but .NET did not recognize the UDT's. That actually made programming harder, since you had to go look up the definition for the UDT and use a native .NET data type.
Does Visual Studio .NET 2005 allow you to use ADT's, and how is that done?
If the ADT is also used in stored procedures, is there a way to drop the ADT without changing the stored procedure first?
Hi pcwc66,
you have a very intresting question.
Could you please provide a sample of you stored procedure,
what do you want to accomplish and I will be glad to answer.
Regards
Hi Yakov,
The idea to replace the old ADT with a new ADT is good. However, for maintenance purpose, I'm thinking whether I can replace the old ADT with a new ADT and then replace the new ADT with another ADT which has the same name as the old ADT but has the definition of the new ADT.
Replacing ADT for columns can follow the article and write a not too complicated script to go thru all tables in a database. Writing a script to replace ADT in stored procedures may be complicated. If there is a way to suppress SQL Server to check ADT existence in other SQL Server objects, then othe SQL Server objects may not need to be replaced.
you can replace the old ADT with a new ADT and then replace the new ADT with another ADT which has the same name as the old ADT but has the definition of the new ADT. The procedure provided in the article allows you to do it.
There is no way to suppress SQL Server from checking ADT existence in other SQL Server objects.
Please read more on ADT in coming parts of this article.
