May 22, 2003 at 12:01 pm
Recenly we upgrade our SQL Server 2000 to SP3. It's primary role is for Analysis Services. In the past I have worked with Microsoft on issues that required hotfixes being applied to my server and clients, which upgraded some DLLs in C:\Program Files\Common Files\System\OLE DB\. After installing SP3, I compared those DLL's to the ones in used in the hotfix, and SP3 DLL's are newer, which is what I expected.
My issue is with client machines. The hotfixes instruct certain DLL's be updated on clients connecting to SQL server as well. Client machines use PivotTable Services to connect to Analysis Services, and these DLL's are usually installed on the client by running the PTSFull.exe or PTSLite.exe files from the SQL Server CD or in SP3. However, when I run these files from SP3 on the client machines, they still use the older DLL's. It appears Microsoft did not update the PTS files in SP3.
Short of copying over the DLL's from the server piecemeal, can someone verify that I am not doing something wrong, or am not wrong in asserting that Microsoft hasn't upgraded PTS in SP3? Especially when updating many client computers, I would like a simple executable like PTSLite.exe, rather than a batch file that renames, copies and registers a bunch of DLL files.
May 22, 2003 at 5:10 pm
We've been speaking with MSft re:PTS lately on completely different topic (performance), but to take advantage of some connection string parameters etc etc, they've instructed us to upgrade all clients to SP3 PTS - which leads me to believe that they have upgraded the PTS component. Also, if you look at the AS architecture, PTS is integral (ie everything goes through PTS to get data to *any* client) so the SP3 upgrade of the AS server component probably would have forced a requirement to upgrade the PTS component.
Steve
Steve.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply