[x]
Posted via EE Mobile

Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again.

Question
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

8.4

Long column for a record in SQL 2000 (change to text data type?)

Asked by mrichmon in MS SQL Server

Tags: MS SQL Server 2000, text, long varchar

I have to port a project to SQL 2000.  I have not written in SQL 2000 for a long time so would appreciate any help.  It currently has a table with several medium and one long varchar columns - the long one is CaseDescription.  I converted the CaseDescription to varchar(8000), however I still get the warning:
-- Warning: The table 'CaseDetails' has been created but its maximum row size (14025) exceeds the maximum number of bytes per row (8060). INSERT or UPDATE of a row in this table will fail if the resulting row length exceeds 8060 bytes.

So I realize I have two options:
1) store this column in a separate table that I link to
2) Use the text type

I am thinking of using the text type, but am so rusty I can't remember all the details of doing so.  Even when changing the type to text there is a length that defaults to 16.  Is that bytes - do I need to set it?

Also for my stored procedures that insert into this table how do I need to change them? (there is no updates to the CaseDetails - the just an original insert - the case is then "edited/modified" with subsequent followups stored elsewhere - so this specific column never changes)

Here is an example stored procedure (shorted to focus on just this question) ("..." indicates more columns/code not shown/relevant)

Finally are there any considerations in my stored procedures or ASP.NET application when reading back out the text data type?  I seem to recall that in the query analyzer you only see the first part of the text, but that it is fine for other applications.  Is that correct?

Thanks for any help.
1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
CREATE PROCEDURE [dbo].[CaseCreate]
	@CaseId int,
	@CaseDate DateTime,
	@ReporterLastName varchar(75),
	@ReporterFirstName varchar(75),
	@Comment varchar(8000),
	...
AS
 
INSERT INTO dbo.CaseDetails(CaseId, CaseDate, ReporterLastName, ReporterFirstName, Comment, ...)
VALUES (@CaseId, @CaseDate, @ReporterLastName, @ReporterFirstName, @Comment, ...)
 
...
[+][-]09/10/09 02:43 PM, ID: 25304815Accepted Solution

View this solution now by starting your 30-day free trial. Setting up your free trial is quick, easy, and secure. We will return you to this solution, unlocked, when you're done.

About this solution

Zone: MS SQL Server
Tags: MS SQL Server 2000, text, long varchar
Sign Up Now!
Solution Provided By: pcelba
Participating Experts: 2
Solution Grade: B
 
[+][-]09/11/09 04:14 PM, ID: 25314235Expert Comment

At Experts Exchange, members can ask their questions to thousands of technology professionals, also known as Experts. Experts compete and collaborate to answer those questions by leaving comments like this one.

Start your 30-day free trial to view this Expert Comment or ask the Experts your question.

 
 
Loading Advertisement...
20091111-EE-VQP-92 - Hierarchy / EE_QW_3_20080625