SQL 2008 View's collation ?

When creating a new Local View from a linked server on a foreign server that has different source view collation, is it correct that all of the Local View's column collations inherit the same type based on the DB that's it's within ?
If yes then would then trying to do the following be pointless ?
ALTER VIEW [dbo].[LocalCustomersView]
AS
SELECT
 CustomerCode COLLATE SQL_Latin1_General_CP1_CS_AS AS CustomerCode
FROM [LinkedForeignServer].[ForeignCustomersDB].[dbo].[ForeignCustomersView]
Thanks in advance.

is it correct that all of the Local View's column collations inherit the same type based on the DB that's it's within ?
Yes, the collation of the base table column takes effect, but you can cast the collation to a different one as you did in your T-SQL statement; it' not "pointless", it will work.
Olaf Helper
[ Blog] [ Xing] [ MVP]

Similar Messages

  • Access a view on a 32 bit Oracle 9i  from a MS SQL 2008 R2 64 bit

    NOt sure if this is the right forum for this.
    We need to access a view on a 32 bit Oracle 9i - Release 9.2.0.8.0 database running on Windows 2003 Server, from a MS SQL 2008 R2 64 bit system running on Windows Server 2008 64 bit.
    Edited by: 854859 on Apr 26, 2011 3:21 PM

    When yu want to access a view hosted in Oracle and retrieve data from this view in a MS SQl Server, then you need to use MS SQL Server Linked Server mechanism based on OLEDB/ODBC.
    Since MS SQL Server this feature is integrated in MS Integration Services and more details can be found at the MS knowledge base.

  • How do I migrate views from MS SQL 2008 to Oracle 11g through SQL Developer

    Is there any way to migrate the views from MS SQL 2008 to Oracle 11g through SQL Developer? Please give me some detail steps. Thanks for your help.
    Kevin

    Hi Kevin,
    user13531850 wrote:
    Hi Turloch,
    When I use migrate to oracle, I got a problem, the migrate tool create a new schema for me in my case (AZTECA_KSMMS), it migrates all the stuffs under that schema (AZTECA_KSMMS). However my application need the all the Oracle data under schema AZTECA instead of AZTECA_KSMMS. Is there any way to specify specific schema (AZTECA) for target oracle database? Schema remapping is available:
    First Capture (separately) then during right click convert on the captured model there is a Specify the conversion options with a Object Naming tab where the schema (and other) name changes are editable.
    I have not used this recently.
    Also during the migration process, when I choose repository, there is a check box for truncate to reset repository to empty state, Do I need to check that truncate Check Box so the repository will be cleared from last migration?The repository can hold multple migration attempts. Check truncate to get rid of previous attempts information. This cleans up the repository - not the destination database.
    There are also online database and offline database options during the migration process, what are the difference between these two choices? After I migrated to Oracle, all my views has a red cross icon next to it. Does that mean the view migration is failed or not? Please give me your comments. Thanks for your help.offline: for big (amount of data) databases with simple data types,
    uses bcp + files + scripts + sqlldr.
    online: for small (amount of data) databases (easier),
    uses (Java) jdbc.
    The view is likely to be broken - recompiling it may help.
    The Oracle schema is created using a .sql file - see under generated in the directory you gave originally in the wizard. There is a .out file that contains the result of running this script including any errors. During conversion there are also likely to be warnings displayed on the UI.
    There may be a single issue that is causing multiple issues - if viewa depends on functionb, and functionb is broken, viewa will also fail.
    >
    Kevin-Turloch
    SQLDeveloper Team

  • Error in sql 2008 reporting services with sharepoint 2013

    i have database sql 2008r2 and sharepoint 2013 enterprise
    database is in cluster server and sharepoint have 2 servers one for webfront end and one for services.
    im tring to configer ssrs in the web front end server for sharepoint and i install sql 2008 add on for sharepoint 2010  but still have this error
    The configuration parameter SharePointIntegrated is set to True but Share
    Point Object Model cannot be loaded. The error was:
    System.IO.FileNotFoundException: Could not load file or assembly
    'Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral,
    PublicKeyToken=71e9bce111e9429c' or one of its dependencies. The system cannot
    find the file specified. File name: 'Microsoft.SharePoint, Version=14.0.0.0,
    Culture=neutral, PublicKeyToken=71e9bce111e9429c' at
    Microsoft.ReportingServices.SharePoint.Objects.RSSPImpSecurity.set_StaticCatchAccessDeniedException(Boolean
    value) at
    Microsoft.ReportingServices.SharePoint.Server.SharePointServiceHelper..ctor() at
    Microsoft.ReportingServices.SharePoint.Server.SharePointServiceHelperFactory.get_ServiceHelper()
    WRN: Assembly binding logging is turned OFF. To enable assembly bind failure
    logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog]
    (DWORD) to 1. Note: There is some performance penalty associated with assembly
    bind failure logging. To turn this feature off, remove the registry value
    [HKLM\Software\Microsoft\Fusion!EnableLog]. .
    (rsSharePointObjectModelNotInstalled)
    and befour that i was install sql 2012 add on for sharepoint 2013 but was the same error so i did uninstall for it
    this error when i try to open reporting services url
    Thanks for any help :) my blog is: http://www.waelk.com

    SharePoint 2013 only supports SSRS 2012 SP1 - http://msdn.microsoft.com/en-us/library/gg492257.aspx. You'll need to upgrade your SSRS instance to 2012 SP1.
    Trevor Seward
    Follow or contact me at...
    &nbsp&nbsp
    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

  • SQL Server in Computers view but not in SQL Computers view

    I'm using SCOM 2012. I have a computer with SQL 2008 R2 installed on it and the SCOM agent is installed and running as Local System on it.
    That computer appears in the computer view in monitoring but it doesn't appear in the SQL Server Computers view - the SQL Agent isn't listed either.
    I have several other SQL servers which are all listed as expected and I'm struggling to work out why this particular server doesn't have it's SQL components listed.

    Hi,
    In addition, regarding checking WMI related issues, please also refer to the following posts:
    WMI Troubleshooting: The Repository on Vista / Server 2008
    http://blogs.technet.com/b/askperf/archive/2008/07/11/wmi-troubleshooting-the-repository-on-vista-server-2008.aspx
    WMI: Rebuilding the WMI Repository
    http://blogs.technet.com/b/askperf/archive/2009/04/13/wmi-rebuilding-the-wmi-repository.aspx
    Hope this helps.
    Thanks.
    Nicholas Li
    TechNet Community Support

  • SQL Exoress 2008 import export Wizard wont import Access 2003 mdb to SQL 2008 DB

    Just installed SQL Express with Tools, including SSME and Import Export Wizard.
    Attempted to transfer Access 2003 DB tables from an mdb file to a SQL 2008 Express DB.
    I can view the data in the tables in Access, however, when I tell it to  do the deed, it begins the process and then errors out with a Error 0xc020801c:
    "TITLE: SQL Server Import and Export Wizard
    Could not connect source component.
    Error 0xc020801c: Source - ParentingStats [1]: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER.  The AcquireConnection method call to the connection manager "SourceConnectionOLEDB" failed with error code 0xC0202009.  There may be error messages posted before this with more information on why the AcquireConnection method call failed.
    ADDITIONAL INFORMATION:
    Exception from HRESULT: 0xC020801C (Microsoft.SqlServer.DTSPipelineWrap)"
    I am unable to find anything that translates this into something mere mortals can deal with.  This is repeatable.
    Steps in the wizard:
    1.  Source: Data Source selected is "Microsoft Access".  The filename is correct.  The username is correct.  The password is blank (there is no password in the Access db).  Clicking on the "Advanced..." button, I get the opportunity to "Test Connection".  I test the connection and the test is successful.
    2.  Destination: I select my server name and the SQL Native Client, select Windows Authentication, and Select my SQL 2008 Express db from the dropdown list.
    3.  Specify Tabloe Copy or Query: I select Table copy
    4.  Select Table or Views: I check the tables I want to copy and successfully preview the data in each table that I checked.  I click on "Edit Mappings ..." and verify that I want to create a new table for each checked table.
    5.  Run package: I accept the pre-checked "Run Immediately" and click the NEXT button
    6.  I get the following:
    "Source Location : C:\Users\wb5rvz\Documents\StatisticsApp_V3_69.mdb
    Source Provider : Microsoft.Jet.OLEDB.4.0
    Destination Location : SHACK_PC\SQLEXPRESS
    Destination Provider : SQLNCLI
    Copy rows from `ParentingStats` to [dbo].[ParentingStats]
    The new target table will be created.
    Copy rows from `Statistics` to [dbo].[Statistics]
    The new target table will be created.
    Copy rows from `StatsSummary` to [dbo].[StatsSummary]
    The new target table will be created.
    Copy rows from `Volunteers_Confidential` to [dbo].[Volunteers_Confidential]
    The new target table will be created.
    Copy rows from `YearMonthTbl` to [dbo].[YearMonthTbl]
    The new target table will be created.
    The package will not be saved.
    The package will be run immediately.
    Provider mapping file : c:\Program Files\Microsoft SQL Server\100\DTS\MappingFiles\JetToMSSql9.xml"
    7.  I click the FINISH button and I get
    "Initializing Data Tasks .... Success"
    "Initializing Connections ...Success"
    "Setting SQL Commend ....20% Compoete"
    "Setting Source Connection ...Error (and an error link)"
    (All following tasks were "Stopped"
    Error detail is:
    ===================================
    Could not connect source component.
    Error 0xc020801c: Source - ParentingStats [1]: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER.  The AcquireConnection method call to the connection manager "SourceConnectionOLEDB" failed with error code 0xC0202009.  There may be error messages posted before this with more information on why the AcquireConnection method call failed.
     (SQL Server Import and Export Wizard)
    ===================================
    Exception from HRESULT: 0xC020801C (Microsoft.SqlServer.DTSPipelineWrap)
    Program Location:
       at Microsoft.SqlServer.Dts.Pipeline.Wrapper.CManagedComponentWrapperClass.AcquireConnections(Object pTransaction)
       at Microsoft.SqlServer.Dts.DtsWizard.Execute.SetSourceConnection(Exception& ex, TransformInfo ti)
    OS is Vista Home Premium SP1 (32 bit)
    Processor = Intel core 2 duo E7200 @ 2.5 GHz
    SQL Server Software was just downloaded yesterday, so it is whatever is current on the download site:
    SQL Express with Tools
    So, how do I get this transform to work?  I do not have nor do I want/afford to put Access 2003 on this machine.
    Thanks
    RRR

    I had this similar problem - 32-bit SQL Server 2005 trying to import tables from Access 2000 .mdb file, same error:
    Error 0xc020801c: Source - ParentingStats [1]: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER.  The AcquireConnection method call to the connection manager "SourceConnectionOLEDB" failed with error code 0xC0202009.  There may be error messages posted before this with more information on why the AcquireConnection method call failed.
     (SQL Server Import and Export Wizard)
    ===================================
    Exception from HRESULT: 0xC020801C (Microsoft.SqlServer.DTSPipelineWrap)
    I know you said you clicked "Advanced..." and Test Connection when you chose your Access database - but that is what resolved the error for me.  I chose my .mdb file, username is admin, password is blank, but if I don't click the Advanced button and test the connection before continuing on, the import fails with above error message.  Go figure, since the username/blank password is correct. 
    FWIW, sorry if that doesn't help you though.

  • Moving Service Manager Database From SQL 2008 R2 SP2 to SQL 2012 SP1

    Hi Guys,
    Just looking for some clarification about moving our Service Manager 2012 R2 database to a new SQL Server.
    Our Service Manager database is currently on a remote SQL server, shared with other databases, running SQL 2008 R2 SP2. It was originally setup this way as we only deployed Change Management but we are now wanting to deploy everything, fully
    utilising SCSM/Orchestrator and Cireson's suite. Due to the limited resources available on that SQL server we are seeing performance issues before even getting it all up and running.
    I want to move the Service Manager database to a new dedicated SQL server running SQL 2012 SP1. I am aware of the official DB move procedure but it does not specifically mention moving up SQL versions. I have seen some comments around here that
    it is fine to do but some feedback would be good, it is not something I have done before. 
    All servers in this are fully patched Windows 2008 R2. Also, we do not currently have a Data Warehouse so do not need to worry about that. It was dropped and uninstalled before upgrading to Service Manager 2012 R2 and will be reinstalled after this DB move
    using a separate dedicated SQL server.
    Thanks, Chris.

    As long as your collations and permissions are the same as before it
    should not be a problem. That sad i could not find any other documentation saying it's not supported. 
    I have moved SCSM databases between different SQL-versions before and it has worked fine if the collations etc are correct. 
    Cheers,
    Thomas Strömberg
    System Center Specialist
    Blog:  
    Twitter:   LinkedIn:
    Please remember to 'Propose as answer' if you find a reply helpful

  • Upgrading SQL 2008 R2 to SQL 2012 SP1

    Hi everyone,
    We are testing some upgrades in a lab environment. We have upgraded to SCCM 2012 R2 and are now looking at upgrading to SQL 2012 SP1 from SQL 2008 R2. Both SCCM and SQL are on one server. (The next step is to split SCCM and SQL but that's another topic)
    The question we are asking is, what should be our process for the upgrade? Do we need to stop SCCM services before doing the SQL upgrade? If, so, which ones?

    Hi,
    You need to stop all Configuration Manager services at the site.
    For the process of the upgrade, you could check the following document.
    http://technet.microsoft.com/en-us/library/gg682077.aspx#BKMK_SupConfigUpgradeDBSrv
    Best Regards,
    Joyce
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • SQL 2008 R2 SP2 release to WSUS

    Hello,
    With the recent release of SQL 2008 R2 SP2 I was curious as to when Microsoft will be pushing it out to WSUS services? I've already done some testing in our environment with a manual download of it, but I was hoping to release it to my production servers
    for a upcoming maintenance night through the proper channels in WSUS. I haven't been able to find any further details on the average release to WSUS time-frame, so I was hoping someone here could shed some light on the matter.
    Thanks in advance,

    Hi everyone, here is the official word on this from Microsoft
    Just finished the brainstorm with our security guys and did some internal search, please refer to below details.
    Between June 21 2012 and August 14th 2012, the internal servers which sign Microsoft software were misconfigured, as a result the signatures on a significant number of internally and externally distributed software
    by Microsoft will expire prematurely on 01/10/2013 .  The result of the signature expiration is that software binaries will be viewed as untrusted, causing them to be invalidated by Microsoft Update, fail installation, and/or detected by 3rd party security
    software. This issue is not limited to Windows operating systems nor is it limited to Security Updates; it may have unexpected consequences across all products, as a full listing of affected products is still under investigation.  Depending on how the
    different products were signed, there are several expiration “milestones” which will occur between November 2012 and summer 2013.
    As a failsafe mitigation, Windows released a bulletin in October as  Microsoft Security Advisory (2749655)
    http://technet.microsoft.com/en-us/security/advisory/2749655
    This effectively catches the WinVerifyTrust API calls in the operating system and returns success to the calling program (e.g. SQL Server) if a specific faulty certificate is detected.
    What SQL Server Products were affected: One of the SQL Server components that was affected was SQL Server 2008 R2 SP2 that was released in July. For this reason, SQL Server 2008 R2 SP2 was scheduled
    to be released via WSUS in August but was put on hold when this issue surfaced. During the testing, Other than Untrusted Publisher errors when executing a small number of affected release packages, and CAPI2 Event Log errors on WinVerifyTrust calls, no ‘hard’
    SQL Server installation or runtime failures have been identified. For this reason, we are not re-releasing SQL Server 2008 R2 SP2.
    SQL Server 2008 R2 SP2 is not being released to Windows update because it is affected by the issue described in the
    Microsoft Security Advisory (2749655)
    http://technet.microsoft.com/en-us/security/advisory/2749655.
    Users are required to get the update via download center.
    SP2 is the only update that is affected by this issue and future updates will continue to be made available via WSUS.
    In a word, honest speaking, this is a Microsoft product issue, and so I’m afraid manual installation would be the only choice. I will mark this case as non-decrement. Sincerely apologize for the inconvenience for
    you.
    Thanks, Michael.

  • SQL 2008 R2 SSRS Security Problems

    Hello,
    We have SSRS running on SQL 2008 R2, using a Windows 2008 R2 Standard Server. When we setup Systems users and also roles such as Browser all that goes through. The issue is, the security does not take effect on the system. 
    For example <domainuser>\<domainuser> can login to the site and traverse ANY folders, even ones that have folder security set, not inheritening permissions. I've came to realize it seems the Windows Group "Users" applies to who can
    get into the server. If we do not have domain users or specific logins in the Windows group you just keep getting a popup for login going to the main SSRS home. 
    I do not the behavior concerning windows group by design but at any rate adding all domain users we then perceive the folder and site settings apply to folders and report access on the Report manager. It does not simply work. Any users  can get into
    the admin folder (Which has only 3-4 people with access) and run anything. It is as if the SSRS permissions simply do not work. I've tried using a server account and also Network Service (Which it is set to now). 
    Has anyone ran into this issue and have any ideas how to resolve it? I understand the BROWSER role has access to "View Folders" but I see no granular other than folder and item permissions being set to not allow specific folders to be accessed. 
    I appreciate your time,
    KT

    Hi KT,
    Per my understanding that you have set the security in the report server but the some of the user still get some extra permission, right?
    Generally, Reporting Services uses role-based security to grant user access to a report server, and there are two types of roles:
    Item-level roles and System-level roles.
    By default, Reporting Services has assigned both System Administrator roles (System-level) and the Content Manager role (Item-level) to the BUILTIN\Administrators group. So, the user that is in the local administrators group will
    perform the role  as ”Content Manager” without extra settings, you can check if the users who have extra permissions was in this group，if the domain user in this group, please try to remove it and add it in the Local Users and Groups other
    then Administrators group :
    You have menioned that the user shouldn't have permission to the Admin folder but now they have access.
    Please check the security of the admin folder to make sure the users were not in the list of the groups and users as below:
    If the issue still exists, please check all the folder one by one to make sure this is not any inheried problem and re-set the security.
    Similar thread for your reference:
    How to remove the DELETE item from the Running report context
    list box
    If you still have any question, please feel free to ask.
    Regards
    Vicky Liu
    Vicky Liu
    TechNet Community Support

  • Installation fails W.Server 2008, Sql 2008 R2

    Hi,
    I need help ASAP please !!
    Im trying to install  BPC 75 SP03 MS version, in Windows Server 2008, SQL 2008 R2 but I cant manage to get the installation done, an error is shown up and I cant go further even though I applied 2 different workarounds.
    Please suggest something
    Error:
    15/09/2011 12:57:55 p.m. OlapVersion : : OLAP_VERSION_2005
    15/09/2011 12:57:55 p.m. GetTimeMembers : End
    15/09/2011 12:57:56 p.m. Validate base member of Time dimension. : Succeed
    15/09/2011 12:57:56 p.m. Get information of ApShel from SQL. : Succeed
    15/09/2011 12:57:56 p.m. Check Insight : Insight disabled.
    15/09/2011 12:58:00 p.m. Connect to Olap server(BPCDEMO) :
    15/09/2011 12:58:01 p.m. Step 2 : -- Create Olap DB.
    15/09/2011 12:58:01 p.m. Step 3 : -- Create DataSource.
    15/09/2011 12:58:02 p.m. Step 3 : -- Create DataSource View.
    15/09/2011 12:58:02 p.m. Step 4 : -- Create Dimensions.
    15/09/2011 12:58:11 p.m. -- C_ACCT : Fail
    15/09/2011 12:58:11 p.m. CreateNewOlapDB : True - Message:OLE DB error: OLE DB or ODBC error.
    Errors in the high-level relational engine. A connection could not be made to the data source with the DataSourceID of 'AppDef', Name of 'AppDef'.
    Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'ApShell', Name of 'C_ACCT' was being processed.
    Server: The operation has been cancelled.
    15/09/2011 12:58:11 p.m. Create ApShell : ========== END ==========
    Workaround 1.
    Open up SQL Management Studio
    2. Go to Security > Logins > NT AUTHORITYLOCAL SERVICE
    3. Right click > Properties
    4. In the User Mapping section tick ApShell
    5. In the bottom section of the screen, tick db_datareader
    Workaround 2.
    Install SQLSERVER2008_ASAMO10, SQLServer2005_ADOMD_x64 and SQLServer2008_ADOMD10_x64
    Please help
    Velázquez

    Hi there,
    Support for SQL Server 2008 R2 only became available in BPC MS 7.5 SP04
    See [Note 1512045 - Planning and Consolidation 75M SP04 Central Note|https://service.sap.com/sap/support/notes/1512045]
    Can you access and process the cubes/dims in SSAS?
    Thanks,
    John

  • Migrate SQL 2000 to SQL 2008

    Hi,
      My company needs to migrate SQL 2000 to SQL 2008.  The SQL 2000 server is running on Windows 2000 server and SQL 2008 does not support Windows 2000 server, so we can't upgrade it to SQL 2008.  Also, double upgrade (SQL 2000->SQL 2005->SQL 2008) is not an option, because we have a very very short time frame.
      The only option I can think of is manually copy everything from SQL 2000 to SQL 2008.  This is ok for tables, views, stored procedures, and functions, but how about triggers, DTS packages, and jobs?
      Is there a good tool out there can copy triggers, DTS packages, and jobs?  Or can somebody recommend another way to migrate SQL 2000 to SQL 2008?
    Thanks,
    Wei

    You can Save AS dts as a file and open on the new server . Read about DTS Designer tool to run the packages
    https://technet.microsoft.com/en-us/library/aa225178%28v=sql.80%29.aspx
    All jobs AFAIK you can script out and re-run on the destination server
    Best Regards,Uri Dimant SQL Server MVP,
    http://sqlblog.com/blogs/uri_dimant/
    MS SQL optimization: MS SQL Development and Optimization
    MS SQL Consulting:
    Large scale of database and data cleansing
    Remote DBA Services:
    Improves MS SQL Database Performance
    SQL Server Integration Services:
    Business Intelligence

  • How can change Case Sensitivity in MS SQL 2008

    hi expert,
    I want to change Case Sensitivity to Case Insensitivity  in MS SQL 2008.
    how can I do??
    any help please
    thanks and regards
    jun

    Hello,
    there is no way to change this. The SQL Server itself and the SAP Database are installed in an case sensitive collation. If you were albe to change this, your installation will be no longer supported and will, in the worst case, generate incorrect data within the SAP database.
    So, start live with it, there is no way to change it.
    Best regards
    Clas

  • 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

  • TFS 2010 Support for SQL 2008 R2 SP3

    Does TFS 2010 support SP3 on SQL 2008 R2?
    Based on this link only SP2 is supported.
    http://msdn.microsoft.com/en-us/library/vstudio/dd631889%28v=vs.110%29.aspx
    Thanks

    Hi Aravind100,  
    Thanks for your post.
    As far as I know SQL Server 2008 R2 SP3 support TFS 2010. I think that document has not been updated after SQL Server 2008 R2 SP3 released.
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

Maybe you are looking for