Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 113
  • Last Modified:

cannot connect to migrated DB in SQL 2014

Hi Experts,

I have two nodes with SQL2014 and AlwaysOn configured.
With my client I cannot connect to my DB.
Do you have any hints to help me out ?
0
Eprs_Admin
Asked:
Eprs_Admin
  • 4
  • 4
1 Solution
 
Vitor MontalvãoMSSQL Senior EngineerCommented:
How are you trying to connect and what's the error?
0
 
Eprs_AdminSystem ArchitectAuthor Commented:
I have a user just in DB not on the server, is it enough to login ?
0
 
Vitor MontalvãoMSSQL Senior EngineerCommented:
It's the same requisites that you need to access a non-AlwaysOn database, i.e. a SQL Server login mapped to a database.
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
Eprs_AdminSystem ArchitectAuthor Commented:
when I tried sqlcmd this is not working.

Can you show me a testclient or cmd to test the login to a DB ?
0
 
Vitor MontalvãoMSSQL Senior EngineerCommented:
Please post the command that you are trying to run.
0
 
Eprs_AdminSystem ArchitectAuthor Commented:
sqlcmd -s servername

this is not responding...
HResult 0x2, Level 16, State 1
Named Pipes Provider: Could not open a connection to SQL Server [2].
Sqlcmd: Error: Microsoft SQL Server Native Client 10.0 : A network-related or instance-specific error has occurred while establishing a connection to
 Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online..
Sqlcmd: Error: Microsoft SQL Server Native Client 10.0 : Login timeout expired.
0
 
Vitor MontalvãoMSSQL Senior EngineerCommented:
Ok, that command is kind of sort. It's missing more parameters.
Here are two examples:
-- Connect to a named instance with trusted connection
sqlcmd -S servername\instancename -E -d DatabaseName

-- Connect to a default instance with a SQL Server user
sqlcmd -S servername -U LoginName -P Password -d DatabaseName

Open in new window

0
 
Eprs_AdminSystem ArchitectAuthor Commented:
ok solved, the username was missing on the sql instances.
0

Featured Post

NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

  • 4
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now