[cisco-voip] Making phone changes through SQL ?

[Tim Reimers]

All--
 
I have the same problem as TechGuy -- but I want to discover the scope
of the issue first, to see if just hand editing phones will work.
 
Is there a way for me to query <something> to find out how many
lines/phones have a SoftKey template setting -other- than 'none' or
'default' ??
 
Tim

________________________________

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Wes Sisk
Sent: Wednesday, October 04, 2006 10:00 AM
To: Tech Guy
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Making phone changes through SQL ?


1. not supported by Cisco.  You're on your own.  there are *MANY*
dependencies in the SQL database and data validation rules are
implemented in DBL not directly in SQL.  This is why updates should go
through BAT, AXL, or CCMAdmin to pass through DBL and data validation.
This means you are allowed to insert garbage directly into SQL.  CM does
not validate data so the effects of your changes could be interesting.
2. depending on CM version you *MAY* not get change notification.  In
4.x CN is generated by Insert/Update/Delete triggers on the tables in
SQL.  This means any update directly to SQL will generate a change
notification.  Same is true of 5.x.  Same is not true of 3.x.  For 3.x
you would have to make the changes and then reboot the server.  Also
changes must be made on the publisher to replicate down to subscribers.
Updating a subscriber will only update the local subscriber DB and that
will not replicate to any other server in the cluster.  Also, when the
system is working properly the subscriber DB will never be read anyway.

I know admins of several large systems who depend on direct mods to SQL
due to lack of features in BAT.  Those admins follow 3 rules to be
successful:
1. be very good at SQL's tri-valued logic i.e. True, False, and NULL
2. verify changes on a lab box first
3. backup the CCM database before making changes. If anything goes awry
restore the backup and go back to the lab.

/Wes

Tech Guy wrote: 

	I am no SQL guru, hell not even a CallManager guru.  Though I
knew alot about it, but the more I talk to others and see the way others
do things the more you come to realize just how little you know.
	 
	This leads me to want to confirm some thing.  I am almost 99.9%
positive that you can change just about anything you want through SQL,
if it is in the database you can change it and as long as you do it
right there shouldn't be a problem. 
	 
	Earlier this week I asked about changing the phone softkey field
through BAT.  Can't seem to find an option to do this within BAT, people
informed me that you could kinda do this through the device pool.
Helpful yes, but not exactly. 
	 
	See the problem with the device pool is that only works if the
phones are set to "none" for the softkey field so then they inherit the
setting from the device pool.  Well apparently when they had CallManager
setup over here someone set all the softkey fields on each phone to the
same.  So, changes to the device pool are not taking affect for me. 
	 
	So this is all part of why I am wanting to confirm things in
regards to making edits directly through SQL instead of through
CallManager.  It should be a simple task through SQL to make this sort
of mass change.  After all isn't that alot of what CallManager and BAT
are, just front ends to SQL database?  I am referring to the web pages
like ccmadmin of course, I know they do more but the essence of the web
pages for ccmadmin and BAT are just easy ways to manipulate the SQL
database right? 
	 
	Thanks for the help so far, its a pleasure to be a part of such
an active and informative mailing list.  By far the best one I have been
a part of in the past 15 or so years.
	
________________________________


	_______________________________________________
	cisco-voip mailing list
	cisco-voip at puck.nether.net
	https://puck.nether.net/mailman/listinfo/cisco-voip
	  

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20061005/232759f5/attachment.html