If you need to alter existing datatypes in the event of a SQL Server Datatype issue for capacity planning or conversion process this simple schema script may come in handy
2007-10-02 (first published: 2002-06-20)
15,404 reads
Jbabington,
2004-03-15
If you need to alter existing datatypes in the event of a SQL Server Datatype issue for capacity planning or conversion process this simple schema script may come in handy
-- Alteration of existing data types -- Allows the existing data type to be changed as runnable -- Script -- Cr Date; 03-14-2003 -- Jbabington@hotmail.com -- Data types are defined in the where clause -- Only use the CHARACTER_MAXIMUM_LENGTH values with caution -- Data type usage issues should be used only by highly -- Exp.dba as there are negative implications if not -- followed correctly SELECT 'ALTER TABLE ' + Table_name + ' ALTER COLUMN ' + Column_name + ' ' + data_type + '' --+ '(' +CAST(CHARACTER_MAXIMUM_LENGTH AS Varchar)+ ')' FROM INFORMATION_SCHEMA.COLUMNS --WHERE data_type = 'numeric'
2007-10-02 (first published: 2002-06-20)
15,404 reads
I have always read that 8060 bytes is the maximum size. This is stated over and over again in Books Online, the MS site and numerous other sites, including this one. However a post in our forum recently questioned this. I decided to verify the problem and do a little research.
2007-10-02 (first published: 2002-02-07)
37,052 reads
The User_Defined_Functions.exe file contains the User-Defined Functions white paper. The User-Defined functions white paper outlines the characteristics of the new user-defined function (UDF) feature that is introduced in Microsoft SQL Server 2000. The white paper also summarizes how you can create your own Transact-SQL functions to extend the programmability of Transact-SQL.
The following stored procedure will demonstrate the use of cursor metadata. Using cursor metadata we can get information about an SQL statement and use that information to dynamically generate other code such as HTML or other stored procedures.
2001-07-27
5,064 reads
ne of the issues you face when building Web applications is handling the errors you encounter when interacting with a back-end database. I was recently working with someone to create a new Web site with SQL Server™, ActiveX® Data Objects (ADO), and ASP. Lots of little things came up that I thought were worth sharing with MIND readers, so I'll focus this column on what I learned from this experience and the solutions to many of the problems I faced.
2001-07-13
1,579 reads