Solved

cannot connect to migrated DB in SQL 2014

Posted on 2015-01-15
8
101 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 45

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 45

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
 

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
Maximize Your Threat Intelligence Reporting

Reporting is one of the most important and least talked about aspects of a world-class threat intelligence program. Here’s how to do it right.

 
LVL 45

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 45

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

How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

Join & Write a Comment

Slowly Changing Dimension Transformation component in data task flow is very useful for us to manage and control how data changes in SSIS.
The recent Microsoft changes on update philosophy for Windows pre-10 and their impact on existing WSUS implementations.
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
This tutorial will show how to configure a single USB drive with a separate folder for each day of the week. This will allow each of the backups to be kept separate preventing the previous day’s backup from being overwritten. The USB drive must be s…

760 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

Need Help in Real-Time?

Connect with top rated Experts

18 Experts available now in Live!

Get 1:1 Help Now