Re: Complicated database problem

Paul wrote:

Bill Karwin <bill@xxxxxxxxxx> wrote:
Though it is a reasonable recommendation to avoid using reserved words in a schema, because then you don't have to remember to use quoted identifiers. 

Touché, or should I say touched? Prescisely my point. Why make life
difficult, when with a teeeeny tiiiny bit of effort, it can be made
easier?


Yeah, I'm in total agreement that it is easier to avoid reserved words.

But it's still a good thing that a mechanism exists to escape them. For instance, if it's important enough to use a specific word, it may be worth the inconvenience of using delimited identifiers. When maintaining legacy systems, sometimes we don't have the freedom to go changing the schema.

Regards,
Bill K.
.

Relevant Pages

  • Re: 2003 R2 version question
    ... Thanks for the tip Paul, as soon I am in i will check what you said. ... You know what just to be clear use adsi edit and verify both domains via the ... Verify the schema extension ... In the child domains there are some R2 DC but the schema version is 30 ...
    (microsoft.public.windows.server.active_directory)
  • Re: XmlValidatingReader memory behaviour
    ... Paul ... > schema collection with multiple XmlValidatingReaders that are created over ... >> I need to validate a number of different XML documents against the same ... >> has to be passed in via the constructor so you can't re-use the internal ...
    (microsoft.public.dotnet.xml)
  • Re: Moving publisher db to another server. (any steps on how to do this without reinitializing?)
    ... >> Comb, ... >> has the schema and data" that you'll need (nosync initialization). ... >> Paul Ibison ...
    (microsoft.public.sqlserver.replication)