Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
jamie
Aged Yak Warrior
542 Posts |
Posted - 2004-11-03 : 08:41:17
|
| hello,one of our 3rd party applications uses the statement :Set No_BrowseTable ONbefore many of its SQL statements to retreive (select) data.I have checked on BOL but can't find any info. regarding this option.what is it all about ? and is it needed ?thanks.Jamie |
|
|
spirit1
Cybernetic Yak Master
11752 Posts |
Posted - 2004-11-03 : 09:01:26
|
According to KB#178366:SET NO_BROWSETABLE ON is an undocumented option performed for Remote DataService (RDS) ActiveX Data Connector (ADC) connections to SQL Server.Enabling this option makes every SELECT statement act as though FOR BROWSEhad been appended to the statement, but bypasses the temporary table thatFOR BROWSE normally pipes the results through. The net effect is to add keysand timestamps to the query as hidden output columns so the client canupdate specific rows (updateable cursors) without separate trips to theserver to pick up the meta-data and munging the query to get the appropriatecolumns.if that gives you any clues.... it doesn't to me...Go with the flow & have fun! Else fight the flow |
 |
|
|
jamie
Aged Yak Warrior
542 Posts |
Posted - 2004-11-03 : 09:49:36
|
| not sure.seems strange why they would run something like :Set No_BrowseTable ONSELECT * FROM LOOKUP WHERE ID=20nothing is updated here.... |
 |
|
|
|
|
|