Actually using SQL Server 2008.

I test selected values using SQLGETPROP( ) and CURSORGETPROP( ) before I use the "SET" counterparts to tweak the settings. For example, I get the BatchUpdateCount, then change it to a much higher value, then get it again to confirm its changed. All works well, except for packetSize, as shown by one of the logs I use to record this info.

2/23/2010 9:44:33 PM: [SQL Transaction Mode (Old): 1]
2/23/2010 9:44:33 PM: [SQL Batch Mode (Old): On]
2/23/2010 9:44:33 PM: [Cursor BatchUpdateCount (Old): 1]
2/23/2010 9:44:33 PM: [SQL PacketSize (Old): 4096]

2/23/2010 9:44:33 PM: [SQL Transaction Mode (New): 2]
2/23/2010 9:44:33 PM: [SQL Batch Mode (New): On]
2/23/2010 9:44:33 PM: [Cursor BatchUpdateCount (New): 5000]
2/23/2010 9:44:33 PM: [SQL PacketSize (New): 4096]

I'm testing connection 1 (the main SQL connection) above for packetsize. Not shown is the test against connection "0" which DOES accept the change in packet size from 4096 to 11592 (or whatever I was setting it to).

Any ideas?