Steelhead Appliance

[cgeary]

You are correct, that feature has no effect with the MS-SQL optimization disabled. 

You must not enable RiOS MSSQL optimization without the assistance of Riverbed Professional Services. If you would like me to put you in touch with PS, please PM me.

[adieball]

Dear, Version 3.0.4 is somewhat "old" :-)

I don't knwo exactly what have been done since then for SQL optimization, but in general one can optimize SQL quite good, only drawback: you need to have specific rules which need to match your sql traffic pattern. The build in rules are good for MS Project Server 2003 only and might break other SQL traffic if enabled.

If your data reduction is good, you might want to take some tcp dumps (full size) and ask Riverbed or your partner to analyze, they can tell from the dumps whether a latency for your specific SQL traffic is possible or not.

Andre

[Ascendo]

Hi Everyone

I have a question regarding SQL Server - SQL Server communications. Since deploying SQL 2005, our remote sites seem to be a lot slower - the compression ratio is the same, but when we move large amounts of data, our line does not get filled completely, whereas it used to. All other protocols are fine.

We did some testing, and when we connect to our linked servers via ODBC with an older SQL Server ODBC driver, things run very quickly again, but this isn't available for 64bit, and there is some functionality missing.

Due to the complexity of our environment, SQL Optimizations have always been disabled, and we want it to stay that way. I see that the option "Enable MS-SQL Prefetch Fetch-Next" is enabled, but I'm not sure this has an effect with the first option off.

To summarise: SQL Native client = slow; SQL Server ODBC driver = fast, but missing functionality.

Has anyone got any experience with this? We are on version 3.0.4.

Thanks