Is there a problem mapping variables to resultsets with a bigint as datatype
I've tried using int64, and others, but all fail except for object datatype.
I cant use object datatype because i wont be able to use it as a derived column.
Any ideas here
Mapping Variables to Resultsets
Hot Topic
- Problem with profiling date time
- job failing
- Calling external webservice using certificate
- Raw files - create once
- Temporary table vs. Table Valued function
- SA account Locked out
- Bold within a textbox
- SQL Server configuration similar to (Oracle Configuration) SQLNET.EXPIRE_TIME
- Security while embedding SQL Server
- set parameters in sub-selects
SQL Server
- Call to Report Mqanager through Internet
- Passing Command line arguments from Visual Studio
- Get Authentication Error in upgrade SQL 2005 named instance to SP1 TCP
- Problem restoring database with encrypted columns to different database or server with encrypted columns.
- ReportExecutionServer namespace?
- Select with group
- SSIS Optimization
- Anybody played with SmoBrowser example within smo?
- Query Designer in SQL 2005 is total %#%!@
- 64 bit(part II)
Mapping Variables to Resultsets
Nessiee
Bill YU
Thanks.
Chad Boles MSFT
Big integers are returned now as strings. So if you choose your variable as a string variable you should be able to get the result correctly. This will probably change. soon.
razva
If i modified the table structure to int and the variable to int32, it works fine.
SBoyd