We have an application that is currently
running in MS Access. It is a bug tracker.
We have a description and resolution field.
The max length of data in description
is 10k long and in resolution is 34k long.
We are porting the application to MSSQL
and PHP.
In MSSQL my solution for the above columns
would be to define them as 'ntext' but then
I found the following problem when I ran
my PHP script:
"MS SQL message: ntext data cannot be sent
to clients using DB-Library (such as ISQL)
or ODBC version 3.7 or earlier."
From what I can tell there will be a lot
more coding envolved if I use ntext or text.
Does anybody have any thoughts on this?
Does anybody have another solution for
storing large amounts of text in MSSQL?
thanks,
lp
running in MS Access. It is a bug tracker.
We have a description and resolution field.
The max length of data in description
is 10k long and in resolution is 34k long.
We are porting the application to MSSQL
and PHP.
In MSSQL my solution for the above columns
would be to define them as 'ntext' but then
I found the following problem when I ran
my PHP script:
"MS SQL message: ntext data cannot be sent
to clients using DB-Library (such as ISQL)
or ODBC version 3.7 or earlier."
From what I can tell there will be a lot
more coding envolved if I use ntext or text.
Does anybody have any thoughts on this?
Does anybody have another solution for
storing large amounts of text in MSSQL?
thanks,
lp