We are currently running CCM 4.1(2) and IPCC 6.0. Both use SQL Server 2000 SP3.
We have a link to the HDS servers from another SQL Server which pulls things like the Termination Call Detail records every night. We are going to be upgrading that server to SQL Server 2005 x64-bit edition. There is a known problem which has been identified in the Microsoft KB found here:
We are pulling a number of things, particularly from the Termination Call Detail. We are copying the data using a linked server. That is where the problem is when trying to use linked servers that are 64-bit connecting to a SQL 2000 SP3 or 4 server that doesn't have these stored procedures. Should it screw anything up? No. But I'm hoping someone here has already tried it and could share their success or failure.
Just curious if you ran into any problems upgrading the stored procedures via the instcat script. I have to run this on our HDS and RGR databases since our Data Warehouse team is migrating over to SQL 2005. Any, "Gotchas" that you would want to discuss will be greatly appreciated.
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: email@example.com Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...