Results 1 to 3 of 3

Thread: Linked Server - SQL 2000 to SQL 2005

  1. #1

    Thread Starter
    MS SQL Powerposter szlamany's Avatar
    Join Date
    Mar 2004
    Location
    Connecticut
    Posts
    18,263

    Linked Server - SQL 2000 to SQL 2005

    We want to create a linked server from a SQL 2000 box to a SQL 2005 box.

    We will have a database on the SQL 2000 box use "views" to a database on the
    SQL 2005 box.

    The user will connect (with an ACCESS front-end) to the SQL 2000 database.
    They use SQL authentication at this time to get to that database.

    The SQL 2005 box will only have WINDOWS AUTHENTICATION. Every user already
    has WINDOWS GROUP rights to the DATABASE on the SQL 2005 box.

    Will this work? Any suggestions on setup?

    Right now we tried creating a linked server on SQL 2000 to SQL 2005 and
    using this query:

    SELECT * FROM FPSSQL05.STUFILES.DBO.STUFILES_T

    and are getting this error:

    Msg 18456, Level 14, State 1, Line 1
    Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.

    *** Read the sticky in the DB forum about how to get your question answered quickly!! ***

    Please remember to rate posts! Rate any post you find helpful - even in old threads! Use the link to the left - "Rate this Post".

    Some Informative Links:
    [ SQL Rules to Live By ] [ Reserved SQL keywords ] [ When to use INDEX HINTS! ] [ Passing Multi-item Parameters to STORED PROCEDURES ]
    [ Solution to non-domain Windows Authentication ] [ Crazy things we do to shrink log files ] [ SQL 2005 Features ] [ Loading Pictures from DB ]

    MS MVP 2006, 2007, 2008

  2. #2
    PowerPoster techgnome's Avatar
    Join Date
    May 2002
    Posts
    34,687

    Re: Linked Server - SQL 2000 to SQL 2005

    I don't know that a 2000 box can talk to a 2005 box.... I know that 2005 can talk to 2000, but I don't know that it can go the other way.... but then I've never tried to do so either. I have had trouble getting EM to talk to a 2005 instance, which is what makes me think that a 2000SQL instance won't talk to the 2005 one.

    -tg
    * I don't respond to private (PM) requests for help. It's not conducive to the general learning of others.*
    * I also don't respond to friend requests. Save a few bits and don't bother. I'll just end up rejecting anyways.*
    * How to get EFFECTIVE help: The Hitchhiker's Guide to Getting Help at VBF - Removing eels from your hovercraft *
    * How to Use Parameters * Create Disconnected ADO Recordset Clones * Set your VB6 ActiveX Compatibility * Get rid of those pesky VB Line Numbers * I swear I saved my data, where'd it run off to??? *

  3. #3

    Thread Starter
    MS SQL Powerposter szlamany's Avatar
    Join Date
    Mar 2004
    Location
    Connecticut
    Posts
    18,263

    Re: Linked Server - SQL 2000 to SQL 2005

    @tg - thanks for that answer.

    I think it might be possible - but the authentication issues are huge (found lots of pages when googling of people with these issues - turn on named pipes - user kerberos - and many more possible solutions).

    I think we ultimately convinced the developer to switch to windows-authentication - and this problem goes away - as their DB can come onto the SQL 2005 box now as well.

    *** Read the sticky in the DB forum about how to get your question answered quickly!! ***

    Please remember to rate posts! Rate any post you find helpful - even in old threads! Use the link to the left - "Rate this Post".

    Some Informative Links:
    [ SQL Rules to Live By ] [ Reserved SQL keywords ] [ When to use INDEX HINTS! ] [ Passing Multi-item Parameters to STORED PROCEDURES ]
    [ Solution to non-domain Windows Authentication ] [ Crazy things we do to shrink log files ] [ SQL 2005 Features ] [ Loading Pictures from DB ]

    MS MVP 2006, 2007, 2008

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width