01-14-2010 05:58 AM - edited 03-14-2019 05:06 AM
hi, i am trying to access to the sql data base, but i dont see the sql query analyzer installed, but i clearlly see SQL server running, how can i check the DB? and normally which login and password does cisco use to connect to it?
thanks
01-14-2010 09:36 AM
My first post, I hope it's helpfull.
The way we did it was to create a new user in Windows on the UCCX server and then log into a PC with the same user and password and run the SQL management tools from there.
You can add a sql server login once you're in there. We were told that this would break historical reporting somehow, but we don't use that feature anyways.
01-14-2010 10:13 AM
Giovanni,
By default UCCX installs SQL Server Express/MSDE hence why you see no query analyzer. You'll need to install SQL Server 2000 to get the tools to manage it.
01-15-2010 01:06 PM
A few comments on this thread:
01-15-2010 01:39 PM
In reply to Jonathan,
Do you think all the data an organization needs to report on about a phone call is covered in Historical Reporting?
Some organization, like ours, also use internal applications to track data about specific phone calls. We like to have reports that integrate both systems. In order to facilitate this, we do a nightly extract from the CCX database to our own reporting database. This accomplishes a couple of things.
1. All report data is in one database making it easier to create reports and ad-hoc queries.
2. It's typically not wise to allow users to run ad-hoc queries and such against production databases. Because we extract the data, we keep the CCX database "on task".
Turning on mixed-mode authentication is documented and does work. Interestingly enough our Historical Reporting still works as well even though we don't use it and were told they wouldn't.
01-15-2010 01:50 PM
I am definitely not stating that the canned HR reports provide every useful data point or representation of what happened in CCX. What I was saying is that mixed mode was known to break CCX until 7.0(1)SR4 and that there is a documented process (DTS export) for doing this.
I was also cautioning against deviating beyond anything that Cisco documents because it will eventually break. When Cisco tells you that you are on your own because of what you did, that's a bad day and I have seen customers in that position. Band aid workarounds to product limitations are not worth doing IMO.
01-15-2010 01:55 PM
I fully agree with Jonathan. It is a suck position to be in when you get kicked in the face by TAC because you didn't do it exactly as they describe. (On the flip side, TAC hasn't been overly useful, for me anyway, with regards to UCCX).
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: