Re: How to allow mutiple application to use the sysmessages table without conflicting?
From: Peter Rilling (peter_at_nospam.rilling.net)
Date: 09/22/04
- Next message: Randy Birch: "Re: Poor VB Programming"
- Previous message: Kalen Delaney: "Re: Force 0?"
- In reply to: David G.: "Re: How to allow mutiple application to use the sysmessages table without conflicting?"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 22 Sep 2004 16:10:07 -0700
Unfortunately our applications will be hosted on a client computer that may
also host application/databases developed by other vendors that we have no
knowledge of.
"David G." <david_nospam@nospam.com> wrote in message
news:OBOnCr2nEHA.2684@TK2MSFTNGP11.phx.gbl...
> Peter Rilling wrote:
> > I think the idea of a sysmessages table is good since it allows the
> > error messages to be centralized, much like using a resource file.
> > The problem I have is that sysmessages are part of the Master
> > database, which means global scope. What if I am working on a server
> > that has more than one database (some of which I may be working on),
> > each being used by a different application. Because there is only
> > one sysmessages tables, if both application A and application B
> > define an the same error code to have different meanings, then there
> > will be a problem because one will get overridden by the other. Is
> > there any way to work around this issue?
> >
> > If not, can someone enlighten me as to why the sysmessages is in the
> > Master and not in the user databases. It seams that error codes are
> > application specific and therefore SQLServer should not be assuming
> > that only a single application will connect to the server.
>
> Yes, assign each application a defined range for error messages. Since
> user-defined messages start at 50001 and the ID is an integer, you can
> have more than a billion error messages in the table, which should be
> enough for any number of applications.
>
> I would think that you may want to have a document shared by all
> applications so they can share a given number of error messages and then
> have a range for errors specific to the application.
>
> As to why it's in the master db: It wouldn't really help the cause to
> put in each user database because, once again, any number of
> applications can hit a given user-database. While you might have a
> better chance of a single app hitting a single db, there's no guarantee
> that would be the case. Plus, the table contains system errors as well.
>
>
> --
> David Gugick
> Imceda Software
> www.imceda.com
>
- Next message: Randy Birch: "Re: Poor VB Programming"
- Previous message: Kalen Delaney: "Re: Force 0?"
- In reply to: David G.: "Re: How to allow mutiple application to use the sysmessages table without conflicting?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
