On Tuesday, April 06, 2004 7:10 PM
Tyler Hepworth
everything has worked very well for me. I can create and respond to tickets, manage users/customers, and send and receive email. I have not gotten any error messages from the SQL server complaining about invalid syntax or any of the other problems that I have seen other's write about on the mailing list.
Great!
However, I am concerned about one datatype in SQL compared to MySQL. There are several places in MySQL that you use the datatype MEDIUMTEXT. From my understanding, this datatype allows for up to 16,777,215 characters to be entered into the field. This datatype is not available in SQL so I had to substitute an approximate equivalent. The closest thing (capacity wise) I could find was the NTEXT type. I setup the database with this type, but got horrible error messages about "SQL cannot do sort or compare operations on NTEXT, TEXT, or IMAGE datatypes". So, NTEXT did not work because it cannot be used in sort or compare operations. To work around this error, I was forced to convert all MEDIUMTEXT types to VARCHAR in MSSQL. Varchar can be sorted and compared, but it only allows a maximun of 8000 characters (non-unicode). There is a huge difference in capacity between MEDIUMTEXT and VARCHAR. I am wondering if this is going to cause problems with some of the fields you have constructed and their intended use.
Yes, I suppose so. You will have to solve that or you'll run into serious problems. Additionally, the absence of Unicode will concern us on the long run. I had a look at the supported data types in MS SQL Server, and it doesn't look good. NTEXT were the one to choose ime, but we need to sort and compare on it. Robert Kehl -- ((otrs.de)) :: OTRS GmbH :: Norsk-Data-Str. 1 :: 61352 Bad Homburg http://www.otrs.de/ :: Tel. +49 (0)6172 4832388