Our SQL Server database is being utilized by many Applix/iHelpdesk
forms. On a cloumn with a 'text char(16)' datatype, we recently found
2 <Long Text> errors on a table. The Applix developers said their
application was locked up. My DBArtisan can disply only two records.
The third row showed a <Long Text> error in the Enterprise Manager.
Was my DBArtisan also locked up?
What kinds of Applix data format caused the the <Long Test> error?
How to solve this problem?
TIA.
JeffreyThat's not an error; that's Enterprise Manager not displaying TEXT/NTEXT
properly. Use a better tool (e.g. Query Analyzer) and that problem goes
away.
Adam Machanic
SQL Server MVP
http://www.sqljunkies.com/weblog/amachanic
--
"Jeffrey" <cjeffwang@.yahoo.com> wrote in message
news:c61d4674.0411221528.487ebc2@.posting.google.com...
> Our SQL Server database is being utilized by many Applix/iHelpdesk
> forms. On a cloumn with a 'text char(16)' datatype, we recently found
> 2 <Long Text> errors on a table. The Applix developers said their
> application was locked up. My DBArtisan can disply only two records.
> The third row showed a <Long Text> error in the Enterprise Manager.
> Was my DBArtisan also locked up?
> What kinds of Applix data format caused the the <Long Test> error?
> How to solve this problem?
> TIA.
> Jeffrey
Showing posts with label utilized. Show all posts
Showing posts with label utilized. Show all posts
Sunday, February 19, 2012
<Long Text> errors on a 'text char(16)' column
Our SQL Server database is being utilized by many Applix/iHelpdesk
forms. On a cloumn with a 'text char(16)' datatype, we recently found
2 <Long Text> errors on a table. The Applix developers said their
application was locked up. My DBArtisan can disply only two records.
The third row showed a <Long Text> error in the Enterprise Manager.
Was my DBArtisan also locked up?
What kinds of Applix data format caused the the <Long Test> error?
How to solve this problem?
TIA.
Jeffrey
That's not an error; that's Enterprise Manager not displaying TEXT/NTEXT
properly. Use a better tool (e.g. Query Analyzer) and that problem goes
away.
Adam Machanic
SQL Server MVP
http://www.sqljunkies.com/weblog/amachanic
"Jeffrey" <cjeffwang@.yahoo.com> wrote in message
news:c61d4674.0411221528.487ebc2@.posting.google.co m...
> Our SQL Server database is being utilized by many Applix/iHelpdesk
> forms. On a cloumn with a 'text char(16)' datatype, we recently found
> 2 <Long Text> errors on a table. The Applix developers said their
> application was locked up. My DBArtisan can disply only two records.
> The third row showed a <Long Text> error in the Enterprise Manager.
> Was my DBArtisan also locked up?
> What kinds of Applix data format caused the the <Long Test> error?
> How to solve this problem?
> TIA.
> Jeffrey
forms. On a cloumn with a 'text char(16)' datatype, we recently found
2 <Long Text> errors on a table. The Applix developers said their
application was locked up. My DBArtisan can disply only two records.
The third row showed a <Long Text> error in the Enterprise Manager.
Was my DBArtisan also locked up?
What kinds of Applix data format caused the the <Long Test> error?
How to solve this problem?
TIA.
Jeffrey
That's not an error; that's Enterprise Manager not displaying TEXT/NTEXT
properly. Use a better tool (e.g. Query Analyzer) and that problem goes
away.
Adam Machanic
SQL Server MVP
http://www.sqljunkies.com/weblog/amachanic
"Jeffrey" <cjeffwang@.yahoo.com> wrote in message
news:c61d4674.0411221528.487ebc2@.posting.google.co m...
> Our SQL Server database is being utilized by many Applix/iHelpdesk
> forms. On a cloumn with a 'text char(16)' datatype, we recently found
> 2 <Long Text> errors on a table. The Applix developers said their
> application was locked up. My DBArtisan can disply only two records.
> The third row showed a <Long Text> error in the Enterprise Manager.
> Was my DBArtisan also locked up?
> What kinds of Applix data format caused the the <Long Test> error?
> How to solve this problem?
> TIA.
> Jeffrey
<Long Text> errors on a 'text char(16)' column
Our SQL Server database is being utilized by many Applix/iHelpdesk
forms. On a cloumn with a 'text char(16)' datatype, we recently found
2 <Long Text> errors on a table. The Applix developers said their
application was locked up. My DBArtisan can disply only two records.
The third row showed a <Long Text> error in the Enterprise Manager.
Was my DBArtisan also locked up?
What kinds of Applix data format caused the the <Long Test> error?
How to solve this problem?
TIA.
Jeffrey
Can you script out this table?
There is no text char(16) data type. There is a text data type and a char
datatype, but no text char(16) data type.
"Jeffrey" <cjeffwang@.yahoo.com> wrote in message
news:c61d4674.0411221515.474c4231@.posting.google.c om...
> Our SQL Server database is being utilized by many Applix/iHelpdesk
> forms. On a cloumn with a 'text char(16)' datatype, we recently found
> 2 <Long Text> errors on a table. The Applix developers said their
> application was locked up. My DBArtisan can disply only two records.
> The third row showed a <Long Text> error in the Enterprise Manager.
> Was my DBArtisan also locked up?
> What kinds of Applix data format caused the the <Long Test> error?
> How to solve this problem?
> TIA.
> Jeffrey
forms. On a cloumn with a 'text char(16)' datatype, we recently found
2 <Long Text> errors on a table. The Applix developers said their
application was locked up. My DBArtisan can disply only two records.
The third row showed a <Long Text> error in the Enterprise Manager.
Was my DBArtisan also locked up?
What kinds of Applix data format caused the the <Long Test> error?
How to solve this problem?
TIA.
Jeffrey
Can you script out this table?
There is no text char(16) data type. There is a text data type and a char
datatype, but no text char(16) data type.
"Jeffrey" <cjeffwang@.yahoo.com> wrote in message
news:c61d4674.0411221515.474c4231@.posting.google.c om...
> Our SQL Server database is being utilized by many Applix/iHelpdesk
> forms. On a cloumn with a 'text char(16)' datatype, we recently found
> 2 <Long Text> errors on a table. The Applix developers said their
> application was locked up. My DBArtisan can disply only two records.
> The third row showed a <Long Text> error in the Enterprise Manager.
> Was my DBArtisan also locked up?
> What kinds of Applix data format caused the the <Long Test> error?
> How to solve this problem?
> TIA.
> Jeffrey
Thursday, February 16, 2012
<Long Text> display on 'text' datatype (16-byte pointer) column
Our SQL Server database is being utilized by many Applix/iHelpdesk
devlopers and users.
On a cloumn with a 'text'datatype (16-byte pointer), we recently were
informed by the developers that their application was locked up. In
Enterprise Manager, I found 2 <Long Text> displays on a table. My
DBArtisan can disply only two records. The third row showed a <Long
Text> in the Enterprise Manager.
Was my DBArtisan also locked up?
How to solve this problem from Applix side?
TIA.
Jeffrey
Jeffrey,
Yes, what you have in your table is a column defined with the TEXT datatype
that shows up as a 16-byte textpointer. Most likely the cause is a implied
UPDATE statement is being held on the TEXT data by you application Applix
while your application is open and this is causing blocking or "locking up"
the data from access by other applications. You can use SQL Profiler to
confirm exactly what your application is doing and then alter the code.
Regards,
John
"Jeffrey" <cjeffwang@.gmail.com> wrote in message
news:bb2899d2.0411222006.571cfacb@.posting.google.c om...
> Our SQL Server database is being utilized by many Applix/iHelpdesk
> devlopers and users.
> On a cloumn with a 'text'datatype (16-byte pointer), we recently were
> informed by the developers that their application was locked up. In
> Enterprise Manager, I found 2 <Long Text> displays on a table. My
> DBArtisan can disply only two records. The third row showed a <Long
> Text> in the Enterprise Manager.
> Was my DBArtisan also locked up?
> How to solve this problem from Applix side?
> TIA.
> Jeffrey
devlopers and users.
On a cloumn with a 'text'datatype (16-byte pointer), we recently were
informed by the developers that their application was locked up. In
Enterprise Manager, I found 2 <Long Text> displays on a table. My
DBArtisan can disply only two records. The third row showed a <Long
Text> in the Enterprise Manager.
Was my DBArtisan also locked up?
How to solve this problem from Applix side?
TIA.
Jeffrey
Jeffrey,
Yes, what you have in your table is a column defined with the TEXT datatype
that shows up as a 16-byte textpointer. Most likely the cause is a implied
UPDATE statement is being held on the TEXT data by you application Applix
while your application is open and this is causing blocking or "locking up"
the data from access by other applications. You can use SQL Profiler to
confirm exactly what your application is doing and then alter the code.
Regards,
John
"Jeffrey" <cjeffwang@.gmail.com> wrote in message
news:bb2899d2.0411222006.571cfacb@.posting.google.c om...
> Our SQL Server database is being utilized by many Applix/iHelpdesk
> devlopers and users.
> On a cloumn with a 'text'datatype (16-byte pointer), we recently were
> informed by the developers that their application was locked up. In
> Enterprise Manager, I found 2 <Long Text> displays on a table. My
> DBArtisan can disply only two records. The third row showed a <Long
> Text> in the Enterprise Manager.
> Was my DBArtisan also locked up?
> How to solve this problem from Applix side?
> TIA.
> Jeffrey
Subscribe to:
Posts (Atom)