you can create a UDF for generating a incremented number for a table and attach it to the column in the CREATE TABLE statement

Andy's right

Go to Tools > Options > Results > Maximum characters per column to change this setting

in QA

This is what books online says about sp_executesql

----------

sp_executesql can be used instead of stored procedures to execute a Transact-SQL statement a number of times when the change in parameter...

i agree with you simon ...the if contruct would be more optimized

but the solution i choose depends on how complex the query is ...i often find myself writing complex...

this look like it would need two tables rather than one -if u want a cursor less solution

if u can post the table structures and some sample data we might...

use a alias i suppose !!

check this article

http://www.sqlservercentral.com/columnists/bknight/encryptfunction.asp

i think i see what the problem is ...

try declaring the table explicitly

CREATE TABLE #tmpReportClient

...

instead of SELECT INTO

better still you can put the whole code in a procedure and use...

Try dropping the temp table right after the select rather than at the top

SELECT * FROM #tmpReportClient

DROP Table #tmpReportClient

there's no equivalent to the split function in Sql

this is what i use

IF LEN(RTRIM(LTRIM(@StrList))) > 0

BEGIN

WHILE PATINDEX('%,%',@StrList) > 0

BEGIN

SET @StrPos = PATINDEX('%,%',@StrList)

SET @TempId = CONVERT(INT,LEFT(@StrList,(@StrPos - 1)))

SET...

Oops

CREATE PROC usp_SelectClientAccountManager @ClientID Int , @AccountManager Int AS

SET NOCOUNT ON

SELECT *

FROM Tbl_ClientAccountManager

WHERE ( ClientID = ISNULL(@ClientID,ClientID))

AND ( AccountManagerID = ISNULL(@AccountManagerID,AccountManagerID))

Would'nt this work

CREATE PROC usp_SelectClientAccountManager @ClientID Int , @AccountManager Int AS

SET NOCOUNT ON

SELECT *

FROM Tbl_ClientAccountManager

WHERE ( ClientID = ISNULL(@ClientID,ClientID))

AND ( AccountManagerID = ISNULL(@AccountManagerID,ClientID))

GO

thanks chris..

just found out it was the firewall..it seems that the sa "forgot" to open it

aarrrrrrrrrgggghhhhhh

Why not output variables???

nope u cannot change the max size of the row...

for the blob/image/text fields the storage is different . i think in sql 7 it was implemented as a linked list...