Can't connect to remote SQL Server 2014 Standard with VS 2012

Hi all,
I am trying to create a development environment using SQL Server 2014 (not Express).  The SQL server instance is on a Windows 8.1 Pro machine in a non-domain environment.  I have Visual Studio 2012 installed on the same machine which can connect
to the SQL server instance without problems.  I have another machine with VS 2012 that cannot connect.  SQL server is configured for mixed authentication.  The SSDT on the remote machine can see the SQL server networked instance, but will not
connect with SQL authentication. 
I have rounded up all the usual suspects;
- The SQL server service is running
- Remote connections are enabled on SQL server and the relevant firewall ports are open.
- TCP/IP and named pipes are enabled
- Remote connections are enabled in Management Studio
- SQL Server Browser service in enabled and running
What am I missing?  I have been out of developer mode for a few years and all of the tools have changed, but I seem to be missing something obvious.
Many thanks in advance,
Tim
Tim in Dublin

Hello,
Have you configured the Windows Firewall on the Visual Studio computer too? Is there any other security software on those
2 computers?
Can you ping between both computers by computer name? If not, try connecting using the IP address. For example:
10.0.0.10,1433
1433 is the default SQL Server port number.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Similar Messages

  • Oracle 10.2 on AIX -- need to connect to remote SQL server by dblink

    oracle 10.2 on AIX -- need to connect to remote SQL server by dblink
    i didn't see a odbc diectory in our oracle home path. how do i know odbc driver is installed in the oracle on our AIX server.
    If it is there, do i just need to modify the odbc.ini and then the inithsodbc.ora, linster.ora, tnsnammes.ora files, or am I missing something
    Appreciate your response
    Edited by: user10876711 on May 12, 2011 9:18 AM
    Edited by: user10876711 on May 12, 2011 9:18 AM

    when you want to connect from Oracle to a SQl Server you need the Oracle Gateway (HSODBC or even better Dg4ODBC) and a FOREIGN ODBC DRIVER for your foreign database - a SQL Server ODBC driver. You have to get this driver from a 3rd party vendor - Oracle does not offer any foreign ODBC drivers.
    So before being able to use DG4ODBC/HSODBC you need to install from a 3rd paryt vendor a SQL Server ODBC driver. Commercial vendrs are for example Data Direct, Openlink or Easysoft.
    On Unix ODBC drivers commonly also require a driver manager. If the ODBC driver vendor does not ship one with the ODBC driver you can get it from www.unixodbc.org

  • Can you replicate databases from SQL Server 2014 Enterprise Edition to SQL Server 2014 Standard edition?

    Hello,
    Can you replicate databases from SQL Server 2014 Enterprise Edition to SQL Server 2014 Standard edition? 
    Thanks. 

    Yes, you can replicate from Enterprise edition to Standard edition.  The only caveat is Peer-to-Peer Replication requires all nodes to be Enterprise Edition.
    Brandon Williams (blog |
    linkedin)

  • Issues enabling AlwaysON in SQL Server 2014 Standard

    Hi 
    I am trying to configure AlwaysOn and having issues enabling in SQL Server configuration manager
    OS : Windows Server 2012 R2
    SQL : SQL Server 2014 Standard Edition
    Here is what i see in config manager : 
    The AlwaysOn Availability Groups feature requires the x86(non-Wow) or x64 Enterprise Edition of SQL Server 2012 (or later version) running on Windows Server 2008 (or later version) with WSFC hotfix KB 2494036 installed. This SQL Server edition and/or Windows
    Server system do not meet one or more of these requirements.
    I patched both the nodes and ran the cluster validation as well which didn't report any missing patches. Couldn't find any documentation/solution for this. 
    Can someone please help me with this ???

    Thanks. 
    Is the configuration of Always on FCI is same as Traditional WSFC ?
    Yes just think of it as a regular clustered sql instance
     An FCI is a single instance of SQL Server that is installed across Windows Server Failover Clustering (WSFC) nodes
    and, possibly, across multiple subnets. 
    https://msdn.microsoft.com/en-us/library/ms189134(v=sql.110).aspx

  • Windows Server 2012 Essentials and Microsoft SQL Server 2014 Standard Core Edition

    Our company is planning to buy Windows Server 2012 R2 Essentials edition (Volume license) and install it on Citrix Xenserver based virtual machine with 4 virtual processor cores. Can we install Microsoft SQL Server 2014 Standard Core Edition (2 licenses
    for 2 cores) and run it on this virtual machine?

    you can install SQL Server Standard 2014/2012 on the Essentials Windows Server but without Server core Installation while installing SQL Server 2014 is supported on the Server Core mode of the following editions of Windows Server:
    Windows Server 2012 R2 Datacenter 64-bit
    Windows Server 2012 R2 Standard 64-bit
    Windows Server 2012 Datacenter 64-bit
    Windows Server 2012 Standard 64-bit
    Windows Server 2008 R2 SP1 Datacenter 64-bit
    Windows Server 2008 R2 SP1 Enterprise 64-bit
    Windows Server 2008 R2 SP1 Standard 64-bit
    Windows Server 2008 R2 SP1 Web 64-bit
    http://msdn.microsoft.com/en-us/library/ms143506.aspx
    thanks
    diramoh
     

  • Upgrating SQL Server 2008 R2 SP2 to SQL Server 2014 Standard "UpgradeFeatureSpecificRules: KJRTMUpgradeBlockRule"

    I've been searching for HOURS how to resolve this issue:
    I am trying to upgrade SQL Server 2008 R2 (Express Edition with advanced services) to SQL SERVER 2014 Standard edition, my first issue was to update the 2008 R2 to Service pack 2 on the first FEATURE RULE TEST, at this time on it's keep saying this:
    ======================================================================================
    Rule Check Result
    Rule "SQL Server 2008 R2 Service pack 2 or later is requered for upgrade.: failed.
    This SQL Server 2008 R2 features that have been selected to be upgraded to SQL Server 2014 are not at the require service pack. To continue with this upgrade, install SQL Server 2008 Service Pack 2 or lager to the selected instance and the shared features.
    =====================================================================================
    This is the Configuration Report issue:
    Microsoft SQL Server 2014 - System Configuration Check Report
    UpgradeFeatureSpecificRules: SQL Server 2014 Setup configuration checks for rules group 'UpgradeFeatureSpecificRules'
        KJRTMUpgradeBlockRule     
    Checks if the currently selected SQL Server 2008 R2 features to upgrade are at the supported service pack.     Failed     The SQL Server 2008 R2 features that have been selected to be upgraded to SQL Server 2014 are not at the
    required service pack. To continue with this upgrade, install SQL Server 2008 Service Pack 2 or later to the selected instance and the shared features.
    ====================================================================================
    I try after hours and finally did install the Upgrade Advisor and got not issues, the last choice I was to uninstall the Management Studio because in other upgrade express versions got blocked, but in this new version of SQL Server 2014 I don't see any way
    out!!!
    Thanks.

    Hi again
    This is the scenario:
    -I have installed the SQL SERVER 2008 R2 With Advanced services (version 10.50.1600.1), and now my guest decide to upgrade to an STARNDARD version which nowadays Microsoft is offering the 2014 version.
    -As all IT Support and DBA I try to upgrade to SQL 2014 to check and see with requirements were missing or updates. The first check report only ask to upgrade to SQL SERVER 2008 R2 SP2 (version 10.51.2500.0) which I found in the optional update list and
    resolved immediately with the Windows Update service.
    -Finally, I realise doing the discovery report (suggested in the last post) is that Windows update only download the service pack 2 for SQL Server 2008 instead of the 2008 R2 (I downloaded manually) then the version was upgrade to 10.52.4000.0
    Next time I might download the updates manually and not loosing a lot hours with Windows Update, another point very important is that when SQL Server 2008 R2 is installed, create the Microsoft SQL Server 2008 folder at all programas in the Startup menu:
    with the SQL Server Installation Center, but there is not one R2, when you execute this one just show the 2008 installed features.
    Now we are on 12.0.2000.8
    Thanks anyway and all of you for your interest!!!

  • Issue of Text Qualiffier after upgrading to SQL Server 2014 Standard

    Hi,
    I'm facing an issue of Text Qualifier after I upgrading my system to SQL Server 2014 Standard Edition (Microsoft SQL Server 2014 - 12.0.2000.8 (X64)
        Feb 20 2014 20:04:26
        Copyright (c) Microsoft Corporation
        Standard Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: ) (Hypervisor)
    I have a csv file with format: Text Qualifier is double pipes ||, Vertical Bar (|) as Column Delimiter and  Row Delimiter is CRLF.
    For example file:
    ||Col1|||||Col2||
    ||ABC|||||XYZ||
    This file is working OK in SQL Server 2008 R2 (SP2) but it does not work in SQL Server 2014. It raised error message while running.
    Error: An error occurred while skipping data rows.
    [SSIS.Pipeline] Error: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED.  The PrimeOutput method on MediaAgencyGroup returned error code 0xC0202091.  The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure
    code is defined by the component, but the error is fatal and the pipeline stopped executing.  There may be error messages posted before this with more information about the failure.
    Any suggestion here?
    Thanks,

    Yes
    There's a difference in the way text qualifiers are parsed from 2012 onwards
    see
    http://www.proactivespeaks.com/2012/06/22/my-5-favorite-sql-2012-ssis-features-so-far/
    http://blog.concentra.co.uk/2013/06/24/ssis-2012-flat-files-now-greatly-improved-but-are-they-good-enough-yet/
    ANyways my preferred way to do this is as below
    http://visakhm.blogspot.in/2014/06/ssis-tips-handling-embedded-text.html
    Please Mark This As Answer if it solved your issue
    Please Vote This As Helpful if it helps to solve your issue
    Visakh
    My Wiki User Page
    My MSDN Page
    My Personal Blog
    My Facebook Page

  • SQL Server 2014 Standard, but only 2 GB RAM used

    Hello,
    I just installed MS SQL Server 2014 Standard Single x64 on a Windows 8 PC. It was bought to replace the Server Express because the RAM limitation of Express.
    I set min server memory to 500 MB and max server memory to 28672 MB. PC has 32 GB Ram.
    Now I start a very crazy procedure/query that is running for hours.
    The problem is now that task manager shows:
    - SQL Server Management Studio (32 Bit): 0% CPU and 135,4 MB RAM
    - SQL Server Windows NT - 64 Bit: 60% CPU and 2.032,6 MB RAM
    If I use: SELECT * FROM sys.dm_os_process_memory  I get:
    physical_memory_in_use_kb : 2124632
    memory_utilization_percentage : 100
    So why is there Management Studio 32 Bit if I installed it through MS SQL Server 2014 Standard Single x64 installation?
    And much more important: Why is only 2 GB RAM used if 32 GB are there and 28 GB should be used?
    kind regards
    Peter

    Hello,
    Could you try to enable Lock Pages in Memory option for the SQL Server service account?
    http://www.sqlcoffee.com/Tuning05.htm
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

  • How to connect to remote sql server database?

    Hallo,
    I am a new member, so please excuse me if my questions are dummy.
    I am using CR2008 SP2 to make reports from sql server 2005 databases.
    Localy there is no connection problem and everything works perfect.
    I would like to establish a connection with a remote sql server 2005,
    but i am not familiar with remote data retriving. which driver should i use? static ip? vpn? server ports?
    Any answer will be really appreciated

    Hello,
    This is more a question for Microsoft to see what and how they support remote connections to databases. As long as you have the connection made CR will not have any problems. You may find it is slow so optimizing your queries is highly recommended. Passing a million records through your web connector is going to take time.....
    I've personally used a VPN connection and then set the ODBC or OLE DB connection info to my test server here at work and it worked fine. But they were small data sets.
    Thank you
    Don

  • How can i connect to a SQL Server 2000 database usgin JSP?

    I need (URGENT) to connect to SQL Server 2000 databse using JSP. I do not know how to program using JSP, so if anyone has any code snippet please let me see it. What i need is to give my site some login/password security.
    Anyone?
    Thx.

    just create an ODBC of your database from control pannel -> administrative tools -> data sources (ODBC) ,double click it .....
    go to the tab SYstem DSN , click on ADD button. select the driver for your connection. it will be the last one in the list "SQL Server".
    click Next then give ur DSN name there, description and Server Name , on next give your username and password of SQL server. when it will be connected to the server celect your database from there and hence there will be an ODBC bridge same as in case of MS Access.
    code for connecting to ODBC is
    // DSN-NAME same as in System DSN.
    // username and password are of your databse
    try
              url = "jdbc:odbc:DSN-NAME";
              Class.forName( "sun.jdbc.odbc.JdbcOdbcDriver" );
              connect = DriverManager.getConnection( url,"username","password" );
              catch ( ClassNotFoundException cnfex ) {
                        setErrorMsg( cnfex.getMessage() );
              catch ( SQLException sqlex ) {
                        setErrorMsg( sqlex.getMessage() );
              catch ( Exception ex ) {
                        setErrorMsg( ex.getMessage() );
    Now you are connected to the SQL Server ..... use connect object for further processing .........

  • Install Guide - SQL Server 2014, Failover Cluster, Windows 2012 R2 Server Core

    I am looking for anyone who has a guide with notes about an installation of a two node, multi subnet failover cluster for SQL Server 2014 on Server Core edition

    Hi KamarasJaranger,
    According to your description, you want configure a SQL Server 2014 Multi-Subnet failover Cluster on Windows Server 2012 R2. Below are the whole steps for the configuration. For the detailed steps about the configuration, please download
    and refer to the
    PDF file.
    1.Add Required Windows Features (.NET Framework 3.5 Features, Failover Clustering and Multipath I/O).
    2.Discover target portals.
    3.Connect targets and configuring Multipathing.
    4.Initialize and format the Disks.
    5.Verify the Storage Replication Process.
    6.Run the Failover Cluster Validation Wizard.
    7.Create the Windows Server 2012 R2 Multi-Subnet Cluster.
    8.Tune Cluster Heartbeat Settings.
    9.Install SQL Server 2014 on a Multi-Subnet Failover Cluster.
    10.Add a Node on a SQL Server 2014 Multi-Subnet Cluster.
    11.Tune the SQL Server 2014 Failover Clustered Instance DNS Settings.
    12.Test application connectivity.
    Regards,
    Michelle Li

  • SQL Server 2014 Bug - with Clustered Index On Temp Table with Identity Column

    Hi,
    Here's a stored procedure.  (It could be shorter, but this will show the problem.)
              CREATE PROCEDURE dbo.SGTEST_TBD_20141030 AS
              IF OBJECT_ID('TempDB..#Temp') IS NOT NULL
                 DROP TABLE #Temp
              CREATE TABLE #Temp
               Col1        INT NULL
              ,Col2        INT IDENTITY NOT NULL
              ,Col3        INT NOT NULL
              CREATE CLUSTERED INDEX ix_cl ON #Temp(Col2)
              SET IDENTITY_INSERT #Temp ON;
              RAISERROR('Preparing to INSERT INTO #Temp...',0,1) WITH NOWAIT;
              INSERT INTO #Temp (Col1, Col2, Col3)
              SELECT 1,2,3
              RAISERROR('Insert Success!!!',0,1) WITH NOWAIT;
              SET IDENTITY_INSERT #Temp OFF;
    In SQL Server 2014, If I execute this (EXEC dbo.SGTEST_TBD_20141030)   It works.   If I execute it a second time - It fails hard with: 
            Msg 0, Level 11, State 0, Line 0
            A severe error occurred on the current command.  The results, if any, should be discarded.
            Msg 0, Level 20, State 0, Line 0
            A severe error occurred on the current command.  The results, if any, should be discarded.
    In SQL Server 2012, I can execute it over and over, with no problem.  I've discovered two work-a-rounds:   
    1) Add "WITH RECOMPILE" to the SP CREATE/ALTER statement, or 
    2) Declare the cluster index in the TABLE CREATE statement, e.g. ",UNIQUE CLUSTERED (COL2)" 
    This second option only works though, if the column is unique.    I've opted for the "WITH RECOMPILE" for now.  But, thought I should share.

    Hi,
    I did not get any error Message:
             CREATE TABLE #Temp
               Col1        INT NULL
              ,Col2        INT IDENTITY NOT NULL
              ,Col3        INT NOT NULL
              CREATE CLUSTERED INDEX ix_cl ON #Temp(Col2)
              SET IDENTITY_INSERT #Temp ON;
              RAISERROR('Preparing to INSERT INTO #Temp...',0,1) WITH NOWAIT;
              INSERT INTO #Temp (Col1, Col2, Col3)
              SELECT 1,2,3
              RAISERROR('Insert Success!!!',0,1) WITH NOWAIT;
              SET IDENTITY_INSERT #Temp OFF;
    SELECT * FROM #Temp
    OUTPUT:
    Col1 Col2
    Col3
    1 2 3
    1 2 3
    1 2 3
    Select @@version
    --Microsoft SQL Server 2012 (SP1) - 11.0.3000.0 (X64) 
    Oct 19 2012 13:38:57 
    Copyright (c) Microsoft Corporation
    Enterprise Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
    Thanks Shiven:) If Answer is Helpful, Please Vote

  • SQL server 2014 express with advanced features

    Dear All,
    i am migrating from SQL server 2008 r2 enterprize edition to 2014 express with advanced service..
    Please, guide me what will be consideration points ..
    Regarding Reporting Services ..
    also TSQL support ..
    Help must appreciated ..
    Dilip Patil..

    i am migrating from SQL server 2008 r2 enterprize edition to 2014 express with advanced service..
    Please, guide me what will be consideration points ..
    Regarding Reporting Services ..
    also TSQL support ..
    Inplace upgrade of SQL server 2008 r2 enterprise to SQL server 2014 express is not supported. But you can do side by side which I would not recommend. Please see
    Version and edition upgrade supported
    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
    My Technet Wiki Article
    MVP

  • Upgrading from SQL Server 2012 Standard to SQL Server 2014 Standard Failover Cluster

    Goal: To upgrade my default instance from SQL Server 2012 to SQL Server 2014 in a failover cluster.
    Given:
    1) Operating System Windows 2012 R2
    2) 2 Virtual Machines in a cluster with SQL Server as a Guest Cluster resource.  The two VMS are called APPS08 and APPS09.  They are our development environment that is setup similar to our production environment.
    Problem:  When running the SQL Server 2014 upgrade, I started on the VM that was not running the instance.  I then moved onto upgrading on the node that was running the instance.  As soon as the install attempt to failover the running instance
    an install error occurred that it could not failover.  After many install attempts I consistently received the error
    The SQL Server Failover cluster instance name 'Dev01'
    already exists as a cluster resource.  Opening Failover cluster manager there is no record of a DEV01.
    New Strategy:  Create a SQLCluster called DEV07.  At the end of the Install I get 'Resource for instance 'MSSQLSERVER' should not exists.  Neither I nor my Windows 2012 guy understand what Resource the install may be referring to.  
    We do not see anything out of the ordinary.
    Any suggestions as to what Resource may be seeing the default instance would be greatly appreciated.

    Hi PSCSQLDBA,
    As your description, you want to upgrade the default instance in SQL Server cluster.
    >> 'SQL Server failover cluster instance name 'Dev01' already exists as cluster resource'
    This error could occur when there is a previously used instance name which may not be removed completely.
    To work around the issue, please use one of the ways below.
    1. At command prompt, type Cluster res. This command will list you all the resources including orphan resources. To delete the orphan resource, type Cluster res <resource name>/delete.
    For more information about the process, please refer to the article:
    http://gemanjyothisqlserver.blogspot.in/2012/12/sql-2008r22012-cluster-installation.html
    2. Delete DNS entries, and force a replication of DNS to the other DNS servers.
    For more information about the process, please refer to the article:
    http://jon.netdork.net/2011/06/07/failed-cluster-install-and-name-already-exists/#solution
    >> 'Resource for instance 'MSSQLSERVER' should not exist'
    This error could occur when you already have MSSQLSERVER as a resource in the cluster, which may not be removed completely. To work around the issue, you could rebuild the SQL Server cluster node.
    Regards,
    Michelle Li

  • Can I recover a damaged SQL Server 2008 database with the undamaged .mdb and .ldf files?

    Their original SQL Server was 2008, with SP unknown, but installed on D: and C: drives.  The power spike corrupted their O/S on the C:
    drive and someone reinstalled both the O/S and the SQL Server, which is now SQL 2008, SP4.  They have intact files for all system databases, both .mdb and .ldf.  Is there some way they can reconnect with the user databases using the intact copies
    of the previous system databases? I have heard that if the SQL Server is stopped, previous Master and Msdb .mdb and .ldf files moved into place and the server restarted, that any previous user database .mdb and .ldf files can be accessed by the SQL server.
    Is this the case, or are there details missing?

    Hello! try this steps
     1 Open your SQL Server Management Studio console. This application shortcut is available in the SQL Server directory in the Windows Start button.
    2  Enter the system administrator user name and password. SQL Server's administrator user name is "sa." This account is required for privileges to restore the database. If your restoring on a host provider server, use the administrator user name
    and password they supplied for your account.
     3 Right-click your database name and select "Attach." In the new window that opens, click the "Add" button to open a dialog box.
     4 Select your MDF file and press the "Ok" button. It may take several minutes to restore the database if it is a large file. Once the process is finished, browse your tables to verify the data. The database is now restored.
    If nothing helped try to use: 
    https://www.youtube.com/watch?v=1cbOYdvBW2c

Maybe you are looking for