Subject: RE: Database Migration
From: [email-masked]
To: [email-masked], [email-masked], [email-masked], [email-masked], [email-masked], [email-masked], [email-masked], [email-masked]
Cc: [email-masked], [email-masked], [email-masked]
Date: Thu, 18 Oct 2001 09:26:12 -0700 (PDT)

Hi All, 

All reports have been generated and the Analysts PC's that participate in the production run verified able 
to run reports and access the Report Settings database on the new server. 

Although, at this moment an exact cause is not known.  We'll be looking into the report log and a number of 
other places to determine the cause of the problem and will communicate this to you with a plan to ensure 
Reporting is safe and sound tomorrow morning. 

If you need me please call or stop by.

Thanks
Kim

>  -----Original Message-----
> From: 	Alexander, Kim D  
> Sent:	Wednesday, October 17, 2001 6:26 PM
> To:	O'Malley, Justin; Gaskill, Chris; Reitmeyer, Jay; 
> Chang, Sheila; Bayer, Adam; Berutti, Aaron; Kurdov, Milen
> Cc:	Dronet, David; Wang, Yan
> Subject:	Database Migration
> 
> Hi All,
> 
> Reporting has been migrated to a new (it's own)  database server and 
> access to the old server has been disabled to ensure the 
> currency of data.
> 
> HOW THIS MIGHT AFFECT YOU:
> If you use tools that link to the Report Settings database, 
> the 'pipeline' DSN on your 
> PC will need to be updated to point to the new server.  
> Specifically this applies to 
> anyone utilizing a Access database to link to the database tables.
> 
> 
> RESOLUTION:
> We will be targeting known users (Justin's Group and Jay) tomorrow.  
> However if you experience problems as a result of this change 
> please contact me.
> 
> Thanks,
> Kim