I am curious to see if other people are experiencing a problem that I have uncovered.
Here is the scenerio: Windowz 2003 + SQL 2005 clean installation of AR6.3 + ITSM6 + CMDB 1.1 Everything is running just fine. The majority of tables / views for the CMDB are not reflected properly in the sysdepends table. You can run the following SQL: select * from sysobjects where xtype = 'V' and id not in (select distinct id from sysdepends) order by name asc How I uncovered this is trying to move the database between 2 SQL 2005 systems and it was failing due to missing dependancies. We had to move the database using backup / restore :( Other oddities: IF you go into admin tool, open a view that is listed, the 'save' button is automagically set, although you have made no changes to the view yet. Closing the window prompts for save. IF you do save the view, it will then create the sysdepends information as expected because the view(s) get dropped and recreated (why they DROP instead of ALTER VIEW I still do not understand either :( ) So, any feedback would be nice, as Remedy is giving me the run-around as expected and asked I create a incident with Micro$oft. Robert Molenda _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
