You may be familiar with the SET TEXTSIZE statement in SQL Server, that enables you to limit the amount of data returned in a SELECT query.
Perhaps you’re finding that its results are exactly the same as LEFT() when running a specific query. Which begs the question: Is there a difference between these two options?
Have you used SET TEXTSIZE to limit the data returned by a query, but found that it just doesn’t seem to work? You’re finding that your SELECT queries continue to return the full amount of text, regardless of the TEXTSIZE value?
Read on. You could be making this one obvious mistake.
When I first encountered the TEXTSIZE option, I decided to run a quick test. But it didn’t work. I tried several times with various TEXTSIZE values, but nothing seemed to work.
“Why isn’t it working?” I wondered.
But then it clicked. I re-read the documentation and realised that I wasn’t using the correct string size for my data types.
In SQL Server, the SET TEXTSIZE statement specifies the size of varchar(max), nvarchar(max), varbinary(max), text, ntext, and image data returned by a SELECT statement.
Microsoft advises that text, ntext, and image will be removed in a future version of SQL Server, so you should avoid using these data types in new development work, and plan to modify applications that currently use them to use varchar(max), nvarchar(max), or varbinary(max) instead.
In SQL Server, the @@TEXTSIZE configuration function returns the current value of the TEXTSIZE option.
No argument is required. You can simply use it in a SELECT statement to return the current TEXTSIZE value.
The TEXTSIZE value specifies the size of varchar(max), nvarchar(max), varbinary(max), text, ntext, and image data returned by a SELECT statement. This value can be set using SET TEXTSIZE.
In SQL Server, you can use the T-SQL IDENT_INCR() function to return the increment value of an identity column. This is the increment value specified when creating the identity column.
In SQL Server, you can use the T-SQL IDENT_SEED() function to return the original seed of an identity column. This is the original seed value specified when creating the identity column.
In SQL Server, if you ever need to return the value created in an identity column, you have several options. Each of these options, although similar, do a slightly different thing.
In SQL Server, you can use the T-SQL SCOPE_IDENTITY() function to return the last identity value inserted into an identity column in the same scope.
A scope is a module (stored procedure, trigger, function, or batch). If two statements are in the same stored procedure, function, or batch, they are in the same scope.
Note that it returns the last identity value generated in any table in the current session. This is in contrast to the IDENT_CURRENT() function, which returns the last-inserted identity value for a given table, regardless of which session it’s in.
SCOPE_IDENTITY() is very similar to @@IDENTITY in that they both return the last-inserted identity value in the current session. The difference is that SCOPE_IDENTITY() is limited to the current scope, whereas @@IDENTITY is not limited to a specific scope.
In SQL Server, you can use the T-SQL @@IDENTITY system function to return the last-inserted identity value in the current session.
Note that it returns the last identity value generated in any table in the current session. This is in contrast to the IDENT_CURRENT() function, which returns the last-inserted identity value for a given table.
The SCOPE_IDENTITY() function is very similar to @@IDENTITY in that it also returns the last-inserted identity value in the current session. The difference is that SCOPE_IDENTITY() is limited to the current scope.
In SQL Server, you can use the T-SQL IDENT_CURRENT() function to return the last identity value generated for a specified table or view on an identity column. The last identity value generated can be for any session and any scope.