Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

Schema Cleanup Best Practice???

2 posts in General Discussion Last posting was on 2010-09-16 15:50:14.0Z
Scott Kellish Posted on 2010-09-16 14:43:14.0Z
Reply-To: "Scott Kellish" <skellish@siemens.com>
From: "Scott Kellish" <skellish@siemens.com>
Newsgroups: sybase.public.ase.general
Subject: Schema Cleanup Best Practice???
Lines: 25
Organization: Siemens Hearing
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5931
X-RFC2646: Format=Flowed; Original
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4c922d02$1@forums-1-dub>
Date: 16 Sep 2010 07:43:14 -0700
X-Trace: forums-1-dub 1284648194 10.22.241.152 (16 Sep 2010 07:43:14 -0700)
X-Original-Trace: 16 Sep 2010 07:43:14 -0700, vip152.sybase.com
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:29568
Article PK: 78800

Hello,
We're undergoing a cleanup of our large and old database and have identified
a hundred or so tables and 2000 or so SP's that are no longer being used.
The system is 15+ years old and has undergone many revolutions in apps that
bang against it.

We obviously don't have a good process for managing what schema is used by
whats (actually we control tightly add/changes, but don't keep track of when
a app stops using a procedure or table).

I don't want to just drop these tables/procs for fear that some app is still
using it. What would the best practice be for phasing out tables/procs. I
thought initially about renaming them. This will obviously result in an
error caught during testing of an application but ASE behaves differently
depending on whether your accessing a renamed table or proc. I also thought
about just removing execute permissions but this could get messy as well.

Any thoughts?

Scott

Gravitation can not be held responsible for people falling in love. Albert
Einstein


Carl Kayser Posted on 2010-09-16 15:50:14.0Z
From: "Carl Kayser" <kayser_c@bls.gov>
Newsgroups: sybase.public.ase.general
References: <4c922d02$1@forums-1-dub>
Subject: Re: Schema Cleanup Best Practice???
Lines: 45
Organization: BLS
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5931
X-RFC2646: Format=Flowed; Original
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4c923cb6$1@forums-1-dub>
Date: 16 Sep 2010 08:50:14 -0700
X-Trace: forums-1-dub 1284652214 10.22.241.152 (16 Sep 2010 08:50:14 -0700)
X-Original-Trace: 16 Sep 2010 08:50:14 -0700, vip152.sybase.com
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:29569
Article PK: 78799


"Scott Kellish" <skellish@siemens.com> wrote in message
news:4c922d02$1@forums-1-dub...
> Hello,
> We're undergoing a cleanup of our large and old database and have
> identified a hundred or so tables and 2000 or so SP's that are no longer
> being used. The system is 15+ years old and has undergone many revolutions
> in apps that bang against it.
>
> We obviously don't have a good process for managing what schema is used by
> whats (actually we control tightly add/changes, but don't keep track of
> when a app stops using a procedure or table).
>
> I don't want to just drop these tables/procs for fear that some app is
> still using it. What would the best practice be for phasing out
> tables/procs. I thought initially about renaming them. This will obviously
> result in an error caught during testing of an application but ASE behaves
> differently depending on whether your accessing a renamed table or proc. I
> also thought about just removing execute permissions but this could get
> messy as well.
>
> Any thoughts?
>
> Scott
>
> Gravitation can not be held responsible for people falling in love. Albert
> Einstein
>

"We're undergoing a cleanup of our large and old database and have
identified a hundred or so tables and 2000 or so SP's that are no longer
being used."

"I don't want to just drop these tables/procs for fear that some app is
still using it."

How did you do the former and yet now worry about the latter?

Thoughts? (1) You might consider auditing of the
procs/views/triggers/tables. (2) Is your sorce code going to be cleaned up
in sync with your object removals?