Solved

cannot connect to migrated DB in SQL 2014

Posted on 2015-01-15
8
104 Views
Last Modified: 2015-02-02
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
Comment
Question by:Eprs_Admin
  • 4
  • 4
8 Comments
 
LVL 47

Expert Comment

by:Vitor Montalvão
ID: 40551493
How are you trying to connect and what's the error?
0
 

Author Comment

by:Eprs_Admin
ID: 40551518
I have a user just in DB not on the server, is it enough to login ?
0
 
LVL 47

Expert Comment

by:Vitor Montalvão
ID: 40551533
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
What is SQL Server and how does it work?

The purpose of this paper is to provide you background on SQL Server. It’s your self-study guide for learning fundamentals. It includes both the history of SQL and its technical basics. Concepts and definitions will form the solid foundation of your future DBA expertise.

 

Author Comment

by:Eprs_Admin
ID: 40552952
when I tried sqlcmd this is not working.

Can you show me a testclient or cmd to test the login to a DB ?
0
 
LVL 47

Expert Comment

by:Vitor Montalvão
ID: 40552975
Please post the command that you are trying to run.
0
 

Author Comment

by:Eprs_Admin
ID: 40552978
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
 
LVL 47

Accepted Solution

by:
Vitor Montalvão earned 500 total points
ID: 40552991
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
 

Author Comment

by:Eprs_Admin
ID: 40553163
ok solved, the username was missing on the sql instances.
0

Featured Post

Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

The Delta outage: 650 cancelled flights, more than 1200 delayed flights, thousands of frustrated customers, tens of millions of dollars in damages – plus untold reputational damage to one of the world’s most trusted airlines. All due to a catastroph…
OfficeMate Freezes on login or does not load after login credentials are input.
Via a live example, show how to shrink a transaction log file down to a reasonable size.
Viewers will learn how to use the UPDATE and DELETE statements to change or remove existing data from their tables. Make a table: Update a specific column given a specific row using the UPDATE statement: Remove a set of values using the DELETE s…

776 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question