17
Unable to allocate new text value, dbid %d.
When you create a table with text, image, or unitext columns, the data is stored on its own chain of text, image or unitext pages. Error 7101 is raised when you attempt to insert data into a text, image, or unitext column in a table, but there is not enough space to allocate the new text, image, or unitext pages.
Error 7101 is raised with the following states:
State |
Meaning |
---|---|
1 |
Could not allocate the first page to add a new value in a table’s text, image, or unitext column. |
2 |
Could not allocate additional pages for an in-progress insert to a text, image, or unitext column. |
Error 7101 is similar to error 1105, states 1 and 2, but it is specific to text, image, or unitext allocation.
Check the available space in the database:
1> use <database_name> 2> go 1> sp_spaceused 2> go
Identify the table by examining the query that raised the error. (You can also run sp_helpsegment on the database segments; rows where indid = 255 refer to the tables with text, image, or unitext columns.)
Check the space use in the table:
1> sp_spaceused <table_name>, 1 2> go
To find the space used by text, image, or unitext columns in this report, look for objects named “t” plus the table name.
Use alter database to increase the storage space for the text, image, or unitext data.
By default, a chain of text, image, or unitext pages is placed on the same device as its table. You can specify a separate device for future space allocations to the text, image, or unitext pages by using the sp_placeobject system stored procedure. This is desirable when you expect substantial growth in text, image, or unitext storage.
See “Placing Text Pages on a Separate Device” in the chapter “Creating and Using Segments” in the System Administration Guide: Volume 2 for details.
All versions