Activity overview
Latest activity by kiyohara
My original post used an unfortunate choice of words in referring to "clusters". We are not using any of the MS clustering technologies on our SQL Server 2005 Standard machines.
The configuration for this problem is:
SQL 2005 Standard on stand-alone W2K3 server "A", no domain, IP=192.168.10.100, TCP Port=12345
SQL 2005 Standard on stand-alone W2K3 server "B", no domain, IP=192.168.20.100, TCP Port=12345
SQL Compare on XP workstation "C", in a domain
When using SQL Compare "Comparison Settings" dialog, I specify the two servers as:
192.168.10.100,12345 (Windows Authentication), Database=Foo
192.168.20.100,12345 (Windows Authentication), Database=Foo
The fact that I can select database "Foo" from the combobox below each server choice means that SQL Compare is correctly contacting each server.
When I click the compare button, I get an "Unknown" dialog: Cannot open database "Foo" requested by the login. The login failed. Login failed for user 'A\joe'.
-Keith. / comments
My original post used an unfortunate choice of words in referring to "clusters". We are not using any of the MS clustering technologies on our SQL Server 2005 Standard machines.
The configuration ...
Hello Brian,
I'm only using Windows Authentication. I am only using Windows Authentication in SQL Compare and SQL Management Studio.
SQL Authentication is not being used. I am not using SQL Authentication in SQL Compare or SQL Management Studio.
As I mentioned in my earlier posts, SQL Compare fails to open the databases when using Windows Authentication.
-Keith. / comments
Hello Brian,
I'm only using Windows Authentication. I am only using Windows Authentication in SQL Compare and SQL Management Studio.
SQL Authentication is not being used. I am not using SQL Authent...
I'm only using Windows Authentication. For most Windows applications, including Management Studio, using the same username/password combination will work regardless of domain. This is a common technique supported by Windows to get around problems with multiple domains. For example, setting up accounts for each domain:
user: domainA\joe; pass: foo
user: domainB\joe; pass: foo
user: domainC\joe; pass: foo
will allow domainA\joe to access most things domainC\joe can without having to re-login.
As I mentioned previously, SQL Compare is able to connect successfully in the "Connection Settings" dialog. Otherwise it wouldn't be able to obtain the list of databases for each server to populate the Database combo box. It's only when I hit "Compare" that something is failing.
Thanks for you quick reply,
-Keith. / comments
I'm only using Windows Authentication. For most Windows applications, including Management Studio, using the same username/password combination will work regardless of domain. This is a common tech...
Windows Authentication Error
I'm trying to compare two servers that are in separate domain controller-less clusters (cluster A and cluster . I am running SQL Compare from a domain controlled workstation (domain C). A, B and C ...