I'm checking some new technologies available in SQL Server 2005/2008. Most of my applications have been written in C # And usually a database component is what I am getting on Google is basically, 'How did you set up CLR UDT?' I have some common questions on application and usage of their real world.
- Is CLR hosted UDT which are usually used in applications? On large or small scale
- Are there performance concerns related to using them?
- Does DBA generally use only the underlying types?
They find a way to revisit an object in a table. Do I believe that the actual range of problems in which solutions have been simplified due to their use? > UDT has only one advantage when they represent some basic elements of your application. Almost always they can be divided into manufactured types, but the advantage is that you do not have to return the returned object. So you probably should not use the UDT which represent the complex objects like the employee, but something like the basics or the shape may be a good option because it is light but its definition is very rigid.
Comments
Post a Comment