Saturday, February 25, 2012

Machine Name Change slows ODBC link intolerably

Hello Everyone,
I have had an ODBC link between Access and Oracle at work for some time
now which has worked without problem. The other day, one of our
technicians came to change the name of my machine. Despite my best
efforts, I could not keep him off my machine and sure enough, my ODBC
linking to Oracle is now incredibly slow. I've tried deleting the
Microsoft Oracle ODBC DSN, but to no avail. I know this is the
sqlserver group but the only results for a machine name change came up
in this group, I am presuming the principal is the same. Can anyone
tell me the full procedure to re-establish my working link? Thanks.
P.S. I work for a local council, so I can't ask anyone here. I have had
to explain file permissions to a Network Manager before... :-(The issues with machine name changes with SQL Server are completely
different. In SQL Server, when you change the machine name, you have
to update system tables that store the name of the local server and
update the registry for the new machine name. It's really a different
issue as it has to do with how the SQL Server service knows what is
local to itself as a server.
-Sue
On 4 Nov 2004 02:39:01 -0800, reclusive.monkey@.gmail.com wrote:

>Hello Everyone,
>I have had an ODBC link between Access and Oracle at work for some time
>now which has worked without problem. The other day, one of our
>technicians came to change the name of my machine. Despite my best
>efforts, I could not keep him off my machine and sure enough, my ODBC
>linking to Oracle is now incredibly slow. I've tried deleting the
>Microsoft Oracle ODBC DSN, but to no avail. I know this is the
>sqlserver group but the only results for a machine name change came up
>in this group, I am presuming the principal is the same. Can anyone
>tell me the full procedure to re-establish my working link? Thanks.
>P.S. I work for a local council, so I can't ask anyone here. I have had
>to explain file permissions to a Network Manager before... :-(

No comments:

Post a Comment