Yes, totally my misreading of the screens. The logging to database screen where it says 'create table' I was reading as 'create database' so definatly my fault!!
Thanks again to everyone for the help. Pete. "Dirk Bulinckx" <[EMAIL PROTECTED]> wrote: > SA uses the db as specified within the ODBC connection. > By default the ODBC layer will use the default db of that user, you can > however > via the ODBC applet of the administrative tools (of the OS) change it towards > a > different DB then the default db. > > > So if SA is using the MASTER db, then this is because the ODBC connection > specifies that. > > > > Dirk Bulinckx. > > -----Original Message----- > From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of > [EMAIL PROTECTED] > Sent: Thursday, March 13, 2008 11:20 AM > To: Servers Alive Discussion List > Subject: Re: [Fwd: Re: [SA-list] Uptime Logging to Database Problem] > > Thanks everyone for the help on this. I have found the problem now by tracking > all transactions going through the SQL box. Basically, I was using the SQL sa > user to connect to the DB and through analysing the transactions you could see > that Servers Alive server was writing to SQL but I still coundn't see the > table I asked Servers Alive to create! > > When we looked at the database id SA was writing to it was always '1'. A quick > look into the Master database and there were new tables with the names of the > databases I was trying to create (sa_debug, sa_uptime etc). > > I am in the process of re-installing SQL2005 Express onto the 'new' Servers > Alive server and am going to try and create a new user just for servers alive. > I'll give it the correct rights to create a DB and see what happens - will > send an Email once this is complete. > > Thanks. > "Chad Stiller" <[EMAIL PROTECTED]> wrote: > > > I had the exact same problems a few weeks back setting up the uptime > logging. It > > was isolated to the credentials the SA server runs under overriding any > > credentials I tried to pass in the ODBC connection, or in the setup in SA. > If > > the database is local to the machine running SA it creates the table and > logs > > fine. If I change SA to run under a Windows account with the necessary > rights I > > can log SA uptime data to the remote database, but I lose my desktop > interaction > > for running SA as a service. > > > > In the interest of time I left the database local as having SA interact with > > the desktop is more important for our environment at the moment. > > > > Hope that helps! > > > > Chad > > > > >>> Peter Shankland <[EMAIL PROTECTED]> 3/12/2008 11:20 AM >>> > > Debug to file is working. No database logging is working. Within the > > file debugging there are entries stating that SA has tried to create the > > databases: > > > > 12 March 2008 17:46:51 CreateTable: () create table sa_uptime( said > > varchar(15),uniqueid numeric, nYear numeric, nmonth numeric, nday > > numeric,upcycles numeric, downcycles numeric, maintenancecycles numeric, > > unavailablecycles numeric, totalcycles numeric,upseconds numeric, > > downseconds numeric, maintenanceseconds numeric, unavailableseconds > > numeric, totalseconds numeric) > > > > > > To unsubscribe send a message with UNSUBSCRIBE as subject to > > [email protected] > > If you use auto-responders (like out-of-the-office messages), then make sure > > that they are not send to the list nor to the individual members of the list > > that send a message. Doing this will get you removed from the list. > > > > To unsubscribe send a message with UNSUBSCRIBE as subject to > [email protected] > If you use auto-responders (like out-of-the-office messages), then make sure > that they are not send to the list nor to the individual members of the list > that send a message. Doing this will get you removed from the list. > > To unsubscribe send a message with UNSUBSCRIBE as subject to > [email protected] > If you use auto-responders (like out-of-the-office messages), then make sure > that they are not send to the list nor to the individual members of the list > that send a message. Doing this will get you removed from the list. > To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected] If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list.
