Alias for a database name?

Hi there,
I'm using SQL Server 2000.
I've created a database that has the name "SworderNet.ProductAnalysis."
Various applications connect to this database using this name. Well, it
turns out that certain programs like Excel have a problem accessing SQL
databases that have a "." in the name. The simplest solution is obviously to
just rename the database but it would be a major hassle to try to track down
all of the various clients that use this database and change the
appropriate config files to reflect the new name. Is there a way to create
an "alias" name for this database (similar to a CNAME record in dns)? For
example, I'd like to create an alias called "ProductAnalysis"... The
original name would still work, but clients that have problems with "."
embedded in the database name can just use the alias name instead.
Is it possible?
Sincerely,
David SworderI'm afraid not. The closest would be to create a new database and for each
table create a view inside that database. Not a nice solution...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"David Sworder" <GilGrissom@.CSILasVegas.com> wrote in message
news:unJfw9IDEHA.1600@.tk2msftngp13.phx.gbl...
> Hi there,
> I'm using SQL Server 2000.
> I've created a database that has the name
"SworderNet.ProductAnalysis."
> Various applications connect to this database using this name. Well, it
> turns out that certain programs like Excel have a problem accessing SQL
> databases that have a "." in the name. The simplest solution is obviously
to
> just rename the database but it would be a major hassle to try to track
down
> all of the various clients that use this database and change the
> appropriate config files to reflect the new name. Is there a way to create
> an "alias" name for this database (similar to a CNAME record in dns)? For
> example, I'd like to create an alias called "ProductAnalysis"... The
> original name would still work, but clients that have problems with "."
> embedded in the database name can just use the alias name instead.
> Is it possible?
> --
> Sincerely,
> David Sworder
>|||Hi,
I have a workaround.
The overhead of this workaround might be large depending upon the database
size and the number of users accessing it.
I tried to replicate the database to the same server with a different name.
If the application, that is facing problem, accessing the database with "."
in its name, does not update the data, then the replication can be
transactional and a frequency can be set for updating the new database.
But again as I said, the overhead may be big. But this workaround would
eliminate the requirement of renaming the database and changing it in the
various clients.
Ashish
This posting is provided "AS IS" with no warranties, and confers no rights.

Agent stops and won't restart

Various sites/servers this is happening.
Start Server AGent
Schedule a DTS to run nightly.
Come back a few days later
SQL SA is stopped
the job never ran
When this first happened I checked the props of SQLSA
and found the "Auto - Restart SQL Server on failure" and "A-R SQL SA..." check boxes.
Checked them.
Come back a few days later. Same results
When I view the jobs in SQL SA- Jobs area those jobs failed for the inimitable
sqlstate 42000 error 8198 "... if the owner
(server\administrator) of job Nightly Update has server access (reason: Could
not obtain information about ... 'server\administrator'.
Yes, the adminitrator. Now I've changed the owner of the jobs to
sa. I'm afraid to presume that sa is powerful enough to stand up to SQL authentication if the admin can't (smirk)
Does anyone have any insights? would the 8198 cause SA to stop? Why would a subordinate job stop SA?
if the sub-job can stop it why doesn't it restart as told to in the properties?
thanks, Bryan
Hi Bryan,
An 8198 error is normally raised when process executed within SQL Server or
from the SQL Server Agent, such as the "xp_logininfo" stored procedure, a
scheduled job, or a replication agent, needs to verify the credentials of a
Windows-authenticated login. The attempt to retrieve those credentials on
the domain failed for an unspecified reason
Please take a look at article
http://support.microsoft.com/default...b;en-us;883551 that talks
about some of the reasons for the 8198 error that you are getting.
Hope that helps !!!
Fargham