sql server - text vs nvarchar

Hi Experts,

I am having a table in sql server 2005.

I will be reading a text file and insert the file details as string in to the table column.

Columun Name: InputXML

Initially, The data type of this column is "Text".

Since, I got the requirement saying that the input file may have 150k length data,

I changed the InptXML column data type to "nvarchar(max)"

Now, while running the batch, I am getting an error which says "FileGroup is Full and could not allocate space"

I was not sure if the error was comming even if the datatype was text.

I thought using nvarchar is better than text data type.

Please suggest,

1. Why is filegroup full error is comming? and how to solve this? (Currently, I am just clearing the table each and every time, i get the error) Is there is any solution for this?
2. Is it because of nvarchar type?
3. Which data type i should use Text/ nvarchar(max).

Please help.
RameshLathuAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

AshokSr. Software EngineerCommented:
Try using
VARCHAR(MAX)

Ashok
0
AshokSr. Software EngineerCommented:
execute this for your table (change MyTable with your real table name).

sp_tableoption N'MyTable', 'large value types out of row', 'ON'

HTH
Ashok
0
AshokSr. Software EngineerCommented:
sp_tableoption N'MyTable', 'large value types out of row', 'OFF'

Not sure which one is default if you do not set it manually so
if 'ON' does not work, try setting it to 'OFF'.

HTH
Ashok
0
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

hafeezmcaCommented:
HI,

Regarding your first & second query:

Unplanned growth of the Data or Transaction log can take up space in the disk. Check if the autogrow option for both Data and log are not set * By percent * .
 
You can see this by selecting Database->properties->Data files tab and Transaction log tab.
 
Please refer the following links for more information:
 

http://support.microsoft.com/default.aspx/kb/315512/EN-US/

If some of your tables are growing faster than you thought then if possible archive and purge them if not you may need to add more space to the disk...
 
To resolve this issue withou a down time you can create new to a different drive by adding new file to PRIMARY FILGROUP


For more information about how to grow and shrink your database and log files, click the following article numbers to view the articles in the Microsoft Knowledge Base:
 
256650  (http://support.microsoft.com/kb/256650/ ) How to shrink the SQL Server 7.0 transaction log
 
272318  (http://support.microsoft.com/kb/272318/ ) Shrinking the transaction log in SQL Server 2000 with DBCC SHRINKFILE
 
317375  (http://support.microsoft.com/kb/317375/ ) A transaction log grows unexpectedly or becomes full on a computer that is running SQL Server
 
247751  (http://support.microsoft.com/kb/247751/ ) BUG: Database maintenance plan does not shrink the database
 
305635  (http://support.microsoft.com/kb/305635/ ) A timeout occurs when a database is automatically expanding

Regarding your third query:

SQL 2005 has deprecated the TEXT in favor of VARCHAR(MAX)  .
Use varchar unless you deal with a lot of internationalized data, then use nvarchar.

The default setting for VARCHAR(MAX) is to store its text value in the table structure, unless the text is over 8,000 bytes at which point it behaves like an TEXT and stores the text value in the LOB.

Since you have altered the table, SQL Server did the alter table, it didn't use the default NVARCHAR(MAX) setting of text in row, but kept the text in the LOB and still uses pointers lookups to get the text out of the LOB.

So, execute this command,  UPDATE <<TableName>> SET Inputxml = Inputxml;

Here are good articles:

http://geekswithblogs.net/johnsPerfBlog/archive/2008/04/16/ntext-vs-nvarcharmax-in-sql-2005.aspx

http://stackoverflow.com/questions/35366/varchar-vs-nvarchar-performance
0
Anuradha GoliSystems Development / Support SpecialistCommented:
using the SQL Server Management Studio. Connect to the server running the Database, open the server/databases, right-click on the database (default name) and click properties. Click on the files tab, change the initial size to the new size(increase size) and click Ok. You can validate that the change in size occurred by going back to the properties of the database.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
RameshLathuAuthor Commented:
Thankyou
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.