Create linked server between MS SQL Server 2008 standard edition to MS SQL Server 2008 express edition

For the captioned issue, is it possible?  We have successfully created linked server between 2 MS SQL server 2008 standard edition, but failed for the standard and express edition.  Is there any trick to setup?  Thanks.

Hello,
SQL Server Management Studio Express Edition may not allow to create a linked server, but the workaround is to use the T-SQL. You can use sp_addlinkedserver and sp_addlinkedsrvlogin.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Similar Messages

  • How to create linked server to multiple database on same server?

    Hi Experts
    I want to create linked server to multiple databases on the same server.
    I have 2 database servers (ServerA and ServerB) and want to create linked server on ServerB to link multiple databases on ServerA).
    I have admin right on ServerB.
    I don't have admin right on ServerA but have different accounts to access on each databases on ServerA.
    After I created one linked server object to a database, I cannot create another linked server object for another database as it has already used the server name which is ServerA.
    Please advise.
    Thanks.

    EXEC sp_addlinkedserver 'ServerADB1', '', 'SQLNCLI', 'ServerA', @catalog = 'DB1'
    EXEC sp_addlinkedserver 'ServerADB2', '', 'SQLNCLI', 'ServerA', @catalog = 'DB2'
    etc.
    Please look up the details for sp_addlinkedserver as I typed this from memory.
    I can certainly see a point in having one linked server per database, as then you don't have to hardcode the database name in the queries, and the linked-server definitions can be changed if the database name changes.
    Erland Sommarskog, SQL Server MVP, [email protected]

  • Actual difference between exterprise oracle 9i/10edition & standard edition

    hi,
    i want to know the actual difference between exterprise oracle 9i/10edition & standard edition.
    plz reply me.
    thanks,
    regards.

    For 10g
    http://www.oracle.com/technology/products/database/oracle10g/pdf/twp_general_10gdb_product_family.pdf
    For 9i
    http://www.oracle.com/technology/products/oracle9i/pdf/o9i_family_features.pdf
    HTH
    Girish Sharma

  • How to create linked server in sql 2005 to access free table visual foxpro 9 step by step

    Hi All, I want to connect to dbf file visual foxpro by using linked server in sql 2005, but i can't do, i hope getting best anwser from every body in forum.
    Thanks all.

    Hi doanpq,
    Please download and install OLE DB Provider for Visual FoxPro 9.0, which exposes OLE DB interfaces that you can use to access Visual FoxPro databases and tables from other programming languages and applications. Please see:
    http://www.microsoft.com/en-us/download/details.aspx?id=14839
    Then, please follow up the following article to create a linked server:
    Creating Linked Servers:
    http://technet.microsoft.com/en-us/library/ff772782(v=sql.105).aspx
    For more information, you can also take a look at the following article, especially Dave K's comment:
    http://blog.dbase.integralwebsolutions.co.za/2008/10/accessing-your-dbf-tables-via-linked.html
    Elvis Long
    TechNet Community Support

  • Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON when creating linked server

    I am setting up a linked server connection in SQL Server 2012 that is "be made using the Login's current security context."  When I test connect from SSMS from my PC it fails with the above error.  If I RDP to the server and test connect
    it succeeds.  The service is running under a domain account.  Any help would greatly be appreciated.

    You need to enable Kerberos for this.  Check out the new
    Microsoft® Kerberos Configuration Manager for SQL Server®
    David
    David http://blogs.msdn.com/b/dbrowne/

  • Creating standby database from ASM production database in standard edition

    Hi,
    I am using oracle 10g release 2 standard edition. I recently created a database instance and wanted to create a standby database instance. After sorting out how to achieve this without managed standby and data guard I finally got it working and the shipped archive logs are applied and working well on the standby database.
    Now I am thinking of re-creating my production database and using ASM for storage managment. By doing this can a standby database still be created from a primary database using ASM? I want to be sure I can before I commit to using ASM for the production instance and manually creating a standby database from that instance.
    Note: I am using standard edition not enterprise edition.

    Hi
    For Oracle SE standby, you can visit www.anbultechnologies.co.uk , they have a brilliant product name DRMC which is Automatic disaster recovery solution with automatic failover in case primary goes down due to any reason.
    We are using this product for more than 2 years and it works like a dream using Oracle Standard Edition. We have depolyed more databases and Standby solution within the prices of 2 EE edition licenses.
    You can give ma try as well.
    website address is www.anbultechnologies.co.uk

  • Differences between 8i enterprise and 8i standard edition

    I have seen numerous discussions on whether 8i enterprise or 8i standard should be used in my division, can anyone point me to a source where I can get a comparision of the features between these two.
    null

    I have installed Oracle 10 XE and it just seems so easy to work with. There's a GUI for everything. It does not have SQL Plus(that I've seen), but there's an area to type your commands into inside the program that helps administrator the Database. I could not find any documents on 9.2 so Im reading documents on Orcale 10 that I have downloaded from this site.
    I am wanting to practice creating, removing,resizing tablespaces, creating databases, and other DBA things. I also want to have triggers functions and procedures working on it too. I wrote some in college against Oracle 8i.

  • Linked server issue using SQLNCLI versions on SQL 2008 & 2014

    Hi all,
    Our product creates databases on a sql server 2008 instance and creates linked servers between them to use distributed queries.
    This looks like: "EXEC sp_addlinkedserver 'linkDatabaseA', '', 'SQLNCLI10', '.', NULL, NULL, 'DatabaseA'"".
    Distributed queries from second database to DatabaseA work fine in this scenario.
    As we want to support both SQL 2008 and SQL 2014 in the next product version, I changed this to SQLNCLI11 as the provider
    and tested on SQL 2008 after installation of the SQLNCLI11 driver.
    This resulted in following error message:
    Msg 468, Level 16, State 9, Line 7
    Cannot resolve the collation conflict between "Latin1_General_CI_AS" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation.
    This is very suprising as the SQL Server 2008 instance and both DB's have "SQL_Latin1_General_CP1_CI_AS" as their collation sequence.
    Then I tried the opposite, installing SQLNCLI10 on SQL 2014. This gave exactly same error! Using SQLNCLI11 went fine ofcourse.
    Generation sp_addlinkedserver statements with correct driver based on SQL version, I'd rather not do (some of the calls are
    generated in SQL from settings in other db tables which are also used for external connx) and adding COLLATE to the queries also
    has consequences like performance degradation. Adding collate on SQL 2014 with SQLNCLI10 as linked server provider results in
    following error:
    Msg 7399, Level 16, State 1, Line 1617
    The OLE DB provider "SQLNCLI10" for linked server "linkDatabaseA" reported an error. Access denied.
    Msg 7301, Level 16, State 2, Line 1617
    Cannot obtain the required interface ("IID_IDBCreateCommand") from OLE DB provider "SQLNCLI10" for linked server "linkDatabaseA".
    Q: Is there any way that SQLNCLI11 can be made to work for linked servers on SQL2008 (preferred solution) or SQLNCLI10 on SQL2014?
    Thx for any feedback.
    Regards, Jouke

    Hi Sofiya,
    Thx for replying.
    For the deployment reasons  mentioned above, I would prefer to use only one SQLNCLI version in both 2008R2 & 2012/2014 scenario's. Most preferred would ofcourse be SQLNCLI11 as this is the latest.
    This would mean that I'd like to be able to configure linked server in SQL2008R2 using SQLNCLI11 driver.
    I would expect that it would be downward compatible with SQLNCLI10 for all client usage, including linked server, which in essence is one SQL DB doing client access to another SQL DB either on same server instance or another. I suspect it requests DB
    metadata from remote DB in order to make decisions and this seems not to work in my setup. If this metadata API is part of the public API, this could indicate that medadata API has been broken in SQLNCLI11 (heavy speculation on my part here!), which could
    also affect other usage (eg. linked server between SQL2008(R2) and SQL2012/2014 instances, (I'll try to set this up and test this, might take a few days. If someone is volunteering, below are db table schemes and query, update @datasrc to point to remote sql
    server instance)).
    Regards, Jouke
    -- This script to run on SQL2008(R2). On SQL2012/2014, install SQLNCLI10 and change @provider in sp_addlinkedserver call.
    -- Pre:
    --   - DatabaseA and DatabaseB are created manually in SSMS
    --   - SQLNCLI11 has been installed
    USE [DatabaseA]
    GO
    CREATE TABLE [dbo].[DatabaseATable](
     [IdField] [int] NOT NULL,
     [LinkField] [nchar](10) NULL,
     CONSTRAINT [PK_DatabaseATable] PRIMARY KEY CLUSTERED
     [IdField] ASC
    ) ON [PRIMARY]
    GO
    EXEC master.dbo.sp_addlinkedserver @server = N'linkDatabaseA', @srvproduct=N'',@provider=N'SQLNCLI11', @datasrc=N'.', @catalog=N'DatabaseA'
    GO
    USE [DatabaseB]
    GO
    CREATE TABLE [dbo].[DatabaseBTable](
     [IdField] [int] NOT NULL,
     [LinkField] [nchar](10) NULL,
     CONSTRAINT [PK_DatabaseBTable] PRIMARY KEY CLUSTERED
     [IdField] ASC
    ) ON [PRIMARY]
    GO
    SELECT b.*, a.*
    FROM DatabaseBTable AS b WITH(NOLOCK)
    JOIN linkDatabaseA.DatabaseA.dbo.DatabaseATable AS a
      ON a.LinkField = b.LinkField
    Hi Jouke Numan,
    According to your description, I install SQL Native Client 11.0 OLE DB Provider in SQL Server 2008R2, and as you post, create two database on the same instance with collation in server default, then create Linked Server with SQLNCI11.0.
     When I run the query statement, it can execute well. It also do not occur the collation conflict. I still recommend you check the collation of server, database, or column and so on.
    SQL Server Native Client 11.0 provides OLE DB support to applications connecting to SQL Server versions 2005, 2008, 2008R2, 2012. So for the deployment reasons, you can choose the only SQLNCLI11.0 in both SQL Server 2008R2 and SQL Server 2012/2014.
    Regards,
    Sofiya Li
    Sofiya Li
    TechNet Community Support

  • Linked Server from SQL 2008 to Connect to 2012 read only replica never works

    I have two Production Database Servers
    1. SQLServer2008 (2 Nodes Cluster)
    2. SQLServer2012 with 2 read only replica (3 Nodes Cluster)
    I would like to draw a line here, We have routing table and URL working perfectly fine. 
    We have tested LINKED Server from 2012 Box to production Server by Specifying APPLICATIONINTENT = ReadOnly; it works perfectly fine, the routing is being used.
    When we create linked server from SQL Server 2008 Box (Please note we have installed SQL Server 2012 Client tools on this box and Restarted the Servers) using the below script
    USE [master]
    EXEC master.dbo.sp_dropserver @server=N'AGL1', @droplogins='droplogins'
    GO
    EXEC master.dbo.sp_addlinkedserver @server = N'AGL1'
    ,@datasrc='AGL1'
    ,@provider='SQLNCLI11'
    ,@provstr='ApplicationIntent=ReadOnly;Database=AdventureWorks2012'
    Linked Server is created, Now when I run the Query 
    exec ('select @@servername') at AGL1
    It always brings the Primary READ/WRITE node name only, after lots of research I found that, this linked Server is always using SQL Native Client 10.0 only, even after creating Linked Server using SNC 11, That is the reason it is not going to routing
    table. Its always connecting to Primary node.
    Below is the way I found it, on 2012 Production Server I executed below Query
    SELECT session_id, protocol_type, driver_version = 
    CASE SUBSTRING(CAST(protocol_version AS BINARY(4)), 1,1)
    WHEN 0x70 THEN 'SQL Server 7.0'
    WHEN 0x71 THEN 'SQL Server 2000'
    WHEN 0x72 THEN 'SQL Server 2005'
    WHEN 0x73 THEN 'SQL Server 2008'
    ELSE 'SQL Server 2012' 
    END,client_net_address ,client_tcp_port,local_tcp_port ,T.text
    FROM sys.dm_exec_connections
    CROSS APPLY sys.dm_exec_sql_text(most_recent_sql_handle) AS T
    The help is taken from msdn (Link Provided below) for the above Query
    https://msdn.microsoft.com/en-us/library/dd339982.aspx
    and I found it always uses SQL Server 2008 SNC.
    My Question is, is there a way to force SQL Server to use SQL Server Native Client 11.
    Has anyone tried this setup?
    Thank you in advance.

    Unfortunately no, there is no other way of forcing it without restart. The SQL Server stack has no idea of the existing Native Client as it booted prior its installation. And you cannot force "DLL reload" without proper service restart. 
    Ivan Donev MCT and MCSE Data Platform

  • Importing Data from MS Access into SQL Serevr 2005 via Linked Server: User-Dependent failure

    I am operating an Express version of SQL Server 2005 on a Windows XP machine.
    I have successfully setup a linked server to a remote Access (.mdb) database. With my user account (Windows authentication) I can retrieve and store data without any problem.
    I have another user (apparently with same settings as my own account) that is always failing to get the data.
    The Error message he gets is:
    OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server "TSU_Tmp" returned message "The Microsoft Jet database engine cannot open the file '\\DSITSO-NT0001\Exchange\Database5.mdb'.  It is already opened exclusively by another
    user, or you need permission to view its data.".
    Msg 7303, Level 16, State 1, Line 1
    Cannot initialize the data source object of OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server "TSU_Tmp".
    Here below the code used to set up the linked server (coming from the Code Snippets of SQL Server 2005).
    EXEC sp_addlinkedserver
    @server = N'TSU_Tmp',
    @provider = N'Microsoft.Jet.OLEDB.4.0',
    @srvproduct = N'OLE DB Provider for Jet',
    @datasrc = N'\\DSITSO-NT0001\Exchange\Database5.mdb'
    EXEC sp_addlinkedsrvlogin
    @rmtsrvname = N'TSU_Tmp',
    @useself = N'TRUE',
    @locallogin = NULL,
    @rmtuser = N'Admin',
    @rmtpassword = NULL
    We both run the script, actually is a Stored Procedure, (see code below) on the same XP machine where SQL Server is running.
    EXEC('INSERT INTO tblFcst
    (StartBUCode, StartBUType, StartBUSeq, StartTrz, StartCty,
    EndBUCode, EndBUType, EndBUSeq, EndTrz, EndCty,
    FcstCreationPeriod, FcstValidForPeriod, Fcst, FcstExternalReference,
    IsProcessed, IsSolved)
    SELECT TSU.BUCodeSend, TSU.BUTypeSend, TSU.BuaNoSend, Null AS StartTrz, Null AS StartCty,
    TSU.BUCodeRcv, TSU.BUTypeRcv, TSU.BuaNoRcv, Null AS EndTrz, Null AS EndCty,
    TSU.[Current week], TSU.[Forecast for week], TSU.[Volume trp m3], TSU.[TSU_ID (Don''t touch me)],
    0 AS IsProcessed, 0 AS IsSolved
    FROM TSU_Tmp...tbl_TSU_trpm3 AS TSU;')
    PS: it is run using an 'EXEC(String)' format as at compile time of Store Procedure the Linked Server is not existing and otherwise compile would fail.
    We tried it with different files, in different locations. It always wors for me, never for him...
    The files were not used by anyone else. The folder(s) where they were stored are open to "Everyone".
    So I concluded it should be something linked to the User... :) But I really do not know what, as said apparently we have exactely the same setup in our Login profiles.
    Any idea or suggestion is welcome.
    Thanks
    Luca

    Hi Luca Lentati,
    According to your description and T-SQL statement, we need to verify if the download and install the Microsoft.Jet.OleDB.4.0 as a provider.
     If the 64bit SQL Server is running on the server,  The error, the Microsoft.Jet.OleDB.4.0 is not support, I reommend you download and install the Microsoft.ACE.OLEDB.12.0 as a provider.
    The error 7303 message indicates that the linked server does not have correct login mapping. You can execute the sp_helplinkedsrvlogin stored procedure to set the login information correctly. Also, verify that you have specified the correct parameters
    for the linked server configuration.
    In addition, if the issue still exists, I recommend you copy the access file to local Server, and create linked server between them , check if it can run well. If yes, it means that
     the account which SQL server uses to run the service does not have read/write access to that file share.
    There is an article about configuring a Linked Microsoft Access Server on SQL 2005 Server , you can review the following article.
    http://www.aspfree.com/c/a/Microsoft-Access/Configuring-a-Linked-Microsoft-Access-Server-on-SQL-2005-Server/
    Regards,
    Sofiya Li
    Sofiya Li
    TechNet Community Support

  • DB Link from Oracle to SQL Server error

    Dear buddies,
    I need to perfome some select on the tables which reside in SQL Server 2005 from Oracle 10g.
    I followed the steps given in :
    http://www.dba-oracle.com/t_heterogeneous_database_connections_sql_server.htm
    I could perform a TNS ping which is successful but only when I perform a select I receive this error.
    ERROR at line 1:
    ORA-28545: error diagnosed by Net8 when connecting to an agent
    Unable to retrieve text of NETWORK/NCR message 65535
    ORA-02063: preceding 2 lines from SQLS
    I have checked that my dsn name is in small caps all the way wherever it is used(Since its suggested in many sites).
    Please guide me.
    I am really looking ahead for a solution.
    Regards,
    Nith

    use the like to setup ODBC and datasource
    http://www.databasejournal.com/features/oracle/article.php/3442661/Making-a-Connection-from-Oracle-to-SQL-Server.htm
    and then create link server in sql server after you test connenction with oracle

  • Linked Server Failed created by DataFeed Publishing Wizard

    I have Created Linked Server by running the   DataFeed Publishing Wizard  and used Select Query from the View  in my another SSIS Package.   When i  run the SSIS Package manually it's working fine. 
    But   when running through SQL Agent Job..  linked server failed ERROR :can not fetch the rows from Linkedserver..

    Perhaps the Agent SSIS step needs to be
    executed under a proxy
    Arthur
    MyBlog
    Twitter

  • Linked Server to MS Access mdb file and exclusivity??

    I've got an SQL database running on SQL Server 2008.  From this server, I have a linked server to an Access database (access 2003).
    In my database I have a stored procedure that I want to query the access database (linked server) and insert / update some rows in one of my SQL tables.
    The linked server is setup without an ODBC DSN (though, I have tried it with one and still get the same results). 
    When I run the stored procedure RDP'd onto the sql server, it runs without issue.  When I run the stored procedure from management studio from my machine, I get "It is already opened exclusively by another user, or you need permission to view its
    data"
    Unfortunately, this access mdb file is pulled from all over our organizatoin - a sin from a long time ago - but I do know that in both instances, the file is still in use by others.
    My SQL Server and file server where the MDB file exists are both a member of the same domain.  Also, the account the SQL Service runs under is a domain account as well.  
    Does this make any sense?
    Thanks
    sb

    Hi kumar,
    According to your description, when you create an linked server in SQL Server 64 bit to connect to the Access database 32bit , usually, the error 7399 and 7350 will occur. As other post, you need to install SQL Server 32bit. Or you can uninstall 32bit office
    products and install 64bit Microsoft Access Database Engine. For creating Linked Server, if you run on a 64bit environment we need to download
    Microsoft Access Database Engine 2010 Redistributable from Microsoft and install suitable version of software on the machine.
    For more information, see:
    http://calyansql.blogspot.jp/2013/02/fix-cannot-initialize-data-source.html
    Regards,
    Sofiya Li
    Sofiya Li
    TechNet Community Support

  • MySQL ODBC driver (32 bit) linked server, architecture mismatch

    Hello,
    I am trying to create a linked server in SQL 2012 Management Studio with a MySQL external server. I have used the 32bit ODBC driver as instructed by the developer, following this rule:
    To manage a data source that connects to a 32-bit driver under 64-bit platform, use c:\windows\sysWOW64\odbcad32.exe.
    My connection is fine using the ODBC connector, but when I try to create the linked server I get an architecture mismatch error: The specified DSN contains an architecture mismatch between the Driver and Application Error 7303.
    Can someone help?
    Best regards
    Kostas
    Kostas Backas-Systemgraph Technologies

    Hello,
    What's the bit verison of the SQL Server ?
    Based on your description, you create a DSN connect to MySQL database with 32 bit MySQL ODBC driver under 32bit ODBC Administrator tool (sysWOW64\odbcad32.exe).
    When you create linked server on SQL Server instance, it will use 64 bit Microsoft OLE DB Provider for ODBC Drivers if the bit version of SQL Server is 64 bit. That may cause the error you received. In that case, please download 64bit MySQL ODBC driver and
    create a DSN with 64 bit ODBC Administrator tool.
    Reference: http://dev.mysql.com/downloads/connector/odbc/
    If I have any misunderstanding, please correct me.
    Regards,
    Fanny Liu
    If you have any feedback on our support, please click here. 
    Fanny Liu
    TechNet Community Support

  • Hadoop ODBC linked server error: Specified driver could not be loaded due to system error 182

    Hi,
    I am trying to connect to a Hadoop server through a linked server in SQL Server. I downloaded and installed the Microsoft Hive ODBC driver - HiveODBC64.msi. But while I am trying to create the Linked server using this ODBC driver I am getting below error.
    " Specified driver could not be loaded due to system error 182 (Microsoft Hive ODBC driver, D:\....\HiveODBC64.dll). (Microsoft SQL Server, Error: 7303)"
    When I tested it locally and in another server, it is working properly. I am getting this error only in this server. looks like a dll error. But cannot identify where/what is the error. Could someone help me fix this issue.
    Server info:
    OS Name: Microsoft Windows Server 2008 R2 Enterprise Version 6.1.7601 Service Pack 1 Build 7601
    SQL SERVER: Microsoft SQL Server 2008 R2(SP1)

    Hi LinkedServer,
    According to your description, you want to create linked server to connect to a Hadoop server in SQL Server, and you have created it successfully in the test server, the problem is that you get the issue in the production environment, right?
    Based on the error message, as you said it seems that the issue is related to the HiveOBDC64.dll assembly. Since you have done it on the test server, you can copy and replace HiveODBC64.dll to production server in the C:\Program Files\Microsoft Hive ODBC
    Driver\lib directory. Or you can reinstall the Microsoft Hive ODBC driver. Here is a blog which describe how to create a SQL Server Linked Server to HDInsight HIVE using Microsoft Hive ODBC Driver step by step, please refer to the link below to double check
    if your steps are correct.
    http://blogs.msdn.com/b/igorpag/archive/2013/11/12/how-to-create-a-sql-server-linked-server-to-hdinsight-hive-using-microsoft-hive-odbc-driver.aspx
    Regards,
    Charlie Liao
    TechNet Community Support

Maybe you are looking for