Showing posts with label servers. Show all posts
Showing posts with label servers. Show all posts

Thursday, March 29, 2012

Consolidate SQL servers to single server

So processor is ruled out. That's good.
I suggest you look at the chapter we put in the SQL 2K HA
book which explains how memory works in depth. To access
8 GB of memory under 32-bit, you need to put /PAE in
boot.ini. There is no other way. With /3GB, you can get
up to 3 GB of usable memory (different space tho), and 1
GB is always reserved for the OS. Up to 16 GB, both can
technically play together, and some applications need it.
beyond 16 GB on 32-bit machines, you cannot combine /3GB
and /PAE.
So if you have 8 GB and use /PAE and /3GB, you have 7 GB
of usable memory, of which only 3 GB would be dynamic (so
one instance could potentially be set to dynamic). When
using PAE, it is best to set the AWE settings in SQL as
well as set max mem for the instance. You seem to know
what that is.
So you can run all three instances with separate memory
using /PAE only, and if you can, I'd recommend that
approach.
Thank you for your reply, though I am still a bit confused.
I understand that using /3GB and /PAE will give me 7GB of usable RAM.
However, you say "When using PAE, it is best to set the AWE settings
in SQL as well as set max mem for the instance. You seem to know what
that is.", and while this is what I have read elsewhere, I was under
the impression that AWE settings were not available on SQL 2000
Standard?
In the next paragraph you say "So you can run all three instances with
separate memory using /PAE only, and if you can, I'd recommend that
approach." I don't think I understand this sentence. Are you saying
I should run /PAE and not /3GB /PAE along with AWE settings in SQL?
Basically, I think I'm just looking to see if I can make SQL Standard
address memory above 4GB. I know you can with Enterprise using AWE, I
just thought AWE was not usable on Standard.
Thanks,
Kevin
"Allan Hirt" <anonymous@.discussions.microsoft.com> wrote in message news:<532201c47407$87fa08c0$a501280a@.phx.gbl>...
> So processor is ruled out. That's good.
> I suggest you look at the chapter we put in the SQL 2K HA
> book which explains how memory works in depth. To access
> 8 GB of memory under 32-bit, you need to put /PAE in
> boot.ini. There is no other way. With /3GB, you can get
> up to 3 GB of usable memory (different space tho), and 1
> GB is always reserved for the OS. Up to 16 GB, both can
> technically play together, and some applications need it.
> beyond 16 GB on 32-bit machines, you cannot combine /3GB
> and /PAE.
> So if you have 8 GB and use /PAE and /3GB, you have 7 GB
> of usable memory, of which only 3 GB would be dynamic (so
> one instance could potentially be set to dynamic). When
> using PAE, it is best to set the AWE settings in SQL as
> well as set max mem for the instance. You seem to know
> what that is.
> So you can run all three instances with separate memory
> using /PAE only, and if you can, I'd recommend that
> approach.
|||PMJI, but I'm 99.9% sure that SQL Standard will only ever use 2GB RAM
maximum. Doesn't matter what OS you use or what switches you have set.
Mike Kruchten
"Kevin" <kjarrard@.gmail.com> wrote in message
news:4f5b3722.0407281043.471e0365@.posting.google.c om...
> Thank you for your reply, though I am still a bit confused.
> I understand that using /3GB and /PAE will give me 7GB of usable RAM.
> However, you say "When using PAE, it is best to set the AWE settings
> in SQL as well as set max mem for the instance. You seem to know what
> that is.", and while this is what I have read elsewhere, I was under
> the impression that AWE settings were not available on SQL 2000
> Standard?
> In the next paragraph you say "So you can run all three instances with
> separate memory using /PAE only, and if you can, I'd recommend that
> approach." I don't think I understand this sentence. Are you saying
> I should run /PAE and not /3GB /PAE along with AWE settings in SQL?
> Basically, I think I'm just looking to see if I can make SQL Standard
> address memory above 4GB. I know you can with Enterprise using AWE, I
> just thought AWE was not usable on Standard.
> Thanks,
> Kevin
> "Allan Hirt" <anonymous@.discussions.microsoft.com> wrote in message
news:<532201c47407$87fa08c0$a501280a@.phx.gbl>...[vbcol=seagreen]

Consolidate SQL servers to single server

We have 3 SQL servers we would like to consolidate onto a single
server. While proccessor usage is not of concern (per perfmon
monitoring and stats on the new hardware), memory usage is.
The Plan:
Migrate three SQL Server 2000 Standard servers to a Dell 6650 (4 way),
each in their own instance. The Server is running Windows 2003
Advanced server.
The Question/Problem:
While I've read about the PAE, AWE and 3/4/gb tunings, I'm still
confused on just what options we have. Each of these DB's use up
around 1 - 1.75GB of memory on a normal basis. They never exceed
1.75GB of usage so we haven't seen the need to go to SQL 2000
Enterprise. Obviously, though, 1.75GB + 1.75GB + 1.75GB !< 4GB of RAM
typically installed on a server. I've used the /3GB tuning on Windows
2000 Advanced, but that doesn't allow for enough memory in this
instance. What are my options to get each of these SQL instances 2GB
of RAM working within the confines of OS the SQL memory management?
Can I simply run Windows in PAE mode and install each copy of SQL in
their own instance to have full run of the 8GB to be installed in this
server? Does the /4gb tuning work with PAE?
KevinSo processor is ruled out. That's good.
I suggest you look at the chapter we put in the SQL 2K HA
book which explains how memory works in depth. To access
8 GB of memory under 32-bit, you need to put /PAE in
boot.ini. There is no other way. With /3GB, you can get
up to 3 GB of usable memory (different space tho), and 1
GB is always reserved for the OS. Up to 16 GB, both can
technically play together, and some applications need it.
beyond 16 GB on 32-bit machines, you cannot combine /3GB
and /PAE.
So if you have 8 GB and use /PAE and /3GB, you have 7 GB
of usable memory, of which only 3 GB would be dynamic (so
one instance could potentially be set to dynamic). When
using PAE, it is best to set the AWE settings in SQL as
well as set max mem for the instance. You seem to know
what that is.
So you can run all three instances with separate memory
using /PAE only, and if you can, I'd recommend that
approach.|||Thank you for your reply, though I am still a bit confused.
I understand that using /3GB and /PAE will give me 7GB of usable RAM.
However, you say "When using PAE, it is best to set the AWE settings
in SQL as well as set max mem for the instance. You seem to know what
that is.", and while this is what I have read elsewhere, I was under
the impression that AWE settings were not available on SQL 2000
Standard?
In the next paragraph you say "So you can run all three instances with
separate memory using /PAE only, and if you can, I'd recommend that
approach." I don't think I understand this sentence. Are you saying
I should run /PAE and not /3GB /PAE along with AWE settings in SQL?
Basically, I think I'm just looking to see if I can make SQL Standard
address memory above 4GB. I know you can with Enterprise using AWE, I
just thought AWE was not usable on Standard.
Thanks,
Kevin
"Allan Hirt" <anonymous@.discussions.microsoft.com> wrote in message news:<532201c47407$87fa08c0$a501280a@.phx.gbl>...
> So processor is ruled out. That's good.
> I suggest you look at the chapter we put in the SQL 2K HA
> book which explains how memory works in depth. To access
> 8 GB of memory under 32-bit, you need to put /PAE in
> boot.ini. There is no other way. With /3GB, you can get
> up to 3 GB of usable memory (different space tho), and 1
> GB is always reserved for the OS. Up to 16 GB, both can
> technically play together, and some applications need it.
> beyond 16 GB on 32-bit machines, you cannot combine /3GB
> and /PAE.
> So if you have 8 GB and use /PAE and /3GB, you have 7 GB
> of usable memory, of which only 3 GB would be dynamic (so
> one instance could potentially be set to dynamic). When
> using PAE, it is best to set the AWE settings in SQL as
> well as set max mem for the instance. You seem to know
> what that is.
> So you can run all three instances with separate memory
> using /PAE only, and if you can, I'd recommend that
> approach.|||PMJI, but I'm 99.9% sure that SQL Standard will only ever use 2GB RAM
maximum. Doesn't matter what OS you use or what switches you have set.
Mike Kruchten
"Kevin" <kjarrard@.gmail.com> wrote in message
news:4f5b3722.0407281043.471e0365@.posting.google.com...
> Thank you for your reply, though I am still a bit confused.
> I understand that using /3GB and /PAE will give me 7GB of usable RAM.
> However, you say "When using PAE, it is best to set the AWE settings
> in SQL as well as set max mem for the instance. You seem to know what
> that is.", and while this is what I have read elsewhere, I was under
> the impression that AWE settings were not available on SQL 2000
> Standard?
> In the next paragraph you say "So you can run all three instances with
> separate memory using /PAE only, and if you can, I'd recommend that
> approach." I don't think I understand this sentence. Are you saying
> I should run /PAE and not /3GB /PAE along with AWE settings in SQL?
> Basically, I think I'm just looking to see if I can make SQL Standard
> address memory above 4GB. I know you can with Enterprise using AWE, I
> just thought AWE was not usable on Standard.
> Thanks,
> Kevin
> "Allan Hirt" <anonymous@.discussions.microsoft.com> wrote in message
news:<532201c47407$87fa08c0$a501280a@.phx.gbl>...
> > So processor is ruled out. That's good.
> >
> > I suggest you look at the chapter we put in the SQL 2K HA
> > book which explains how memory works in depth. To access
> > 8 GB of memory under 32-bit, you need to put /PAE in
> > boot.ini. There is no other way. With /3GB, you can get
> > up to 3 GB of usable memory (different space tho), and 1
> > GB is always reserved for the OS. Up to 16 GB, both can
> > technically play together, and some applications need it.
> > beyond 16 GB on 32-bit machines, you cannot combine /3GB
> > and /PAE.
> >
> > So if you have 8 GB and use /PAE and /3GB, you have 7 GB
> > of usable memory, of which only 3 GB would be dynamic (so
> > one instance could potentially be set to dynamic). When
> > using PAE, it is best to set the AWE settings in SQL as
> > well as set max mem for the instance. You seem to know
> > what that is.
> >
> > So you can run all three instances with separate memory
> > using /PAE only, and if you can, I'd recommend that
> > approach.

Consolidate SQL servers to single server

So processor is ruled out. That's good.
I suggest you look at the chapter we put in the SQL 2K HA
book which explains how memory works in depth. To access
8 GB of memory under 32-bit, you need to put /PAE in
boot.ini. There is no other way. With /3GB, you can get
up to 3 GB of usable memory (different space tho), and 1
GB is always reserved for the OS. Up to 16 GB, both can
technically play together, and some applications need it.
beyond 16 GB on 32-bit machines, you cannot combine /3GB
and /PAE.
So if you have 8 GB and use /PAE and /3GB, you have 7 GB
of usable memory, of which only 3 GB would be dynamic (so
one instance could potentially be set to dynamic). When
using PAE, it is best to set the AWE settings in SQL as
well as set max mem for the instance. You seem to know
what that is.
So you can run all three instances with separate memory
using /PAE only, and if you can, I'd recommend that
approach.Thank you for your reply, though I am still a bit confused.
I understand that using /3GB and /PAE will give me 7GB of usable RAM.
However, you say "When using PAE, it is best to set the AWE settings
in SQL as well as set max mem for the instance. You seem to know what
that is.", and while this is what I have read elsewhere, I was under
the impression that AWE settings were not available on SQL 2000
Standard?
In the next paragraph you say "So you can run all three instances with
separate memory using /PAE only, and if you can, I'd recommend that
approach." I don't think I understand this sentence. Are you saying
I should run /PAE and not /3GB /PAE along with AWE settings in SQL?
Basically, I think I'm just looking to see if I can make SQL Standard
address memory above 4GB. I know you can with Enterprise using AWE, I
just thought AWE was not usable on Standard.
Thanks,
Kevin
"Allan Hirt" <anonymous@.discussions.microsoft.com> wrote in message news:<532201c47407$87fa0
8c0$a501280a@.phx.gbl>...
> So processor is ruled out. That's good.
> I suggest you look at the chapter we put in the SQL 2K HA
> book which explains how memory works in depth. To access
> 8 GB of memory under 32-bit, you need to put /PAE in
> boot.ini. There is no other way. With /3GB, you can get
> up to 3 GB of usable memory (different space tho), and 1
> GB is always reserved for the OS. Up to 16 GB, both can
> technically play together, and some applications need it.
> beyond 16 GB on 32-bit machines, you cannot combine /3GB
> and /PAE.
> So if you have 8 GB and use /PAE and /3GB, you have 7 GB
> of usable memory, of which only 3 GB would be dynamic (so
> one instance could potentially be set to dynamic). When
> using PAE, it is best to set the AWE settings in SQL as
> well as set max mem for the instance. You seem to know
> what that is.
> So you can run all three instances with separate memory
> using /PAE only, and if you can, I'd recommend that
> approach.|||PMJI, but I'm 99.9% sure that SQL Standard will only ever use 2GB RAM
maximum. Doesn't matter what OS you use or what switches you have set.
Mike Kruchten
"Kevin" <kjarrard@.gmail.com> wrote in message
news:4f5b3722.0407281043.471e0365@.posting.google.com...
> Thank you for your reply, though I am still a bit confused.
> I understand that using /3GB and /PAE will give me 7GB of usable RAM.
> However, you say "When using PAE, it is best to set the AWE settings
> in SQL as well as set max mem for the instance. You seem to know what
> that is.", and while this is what I have read elsewhere, I was under
> the impression that AWE settings were not available on SQL 2000
> Standard?
> In the next paragraph you say "So you can run all three instances with
> separate memory using /PAE only, and if you can, I'd recommend that
> approach." I don't think I understand this sentence. Are you saying
> I should run /PAE and not /3GB /PAE along with AWE settings in SQL?
> Basically, I think I'm just looking to see if I can make SQL Standard
> address memory above 4GB. I know you can with Enterprise using AWE, I
> just thought AWE was not usable on Standard.
> Thanks,
> Kevin
> "Allan Hirt" <anonymous@.discussions.microsoft.com> wrote in message
news:<532201c47407$87fa08c0$a501280a@.phx.gbl>...[vbcol=seagreen]

Consolidate multiple databases via merge replication

Hi
I am trying to merge a set of tables from 5 separate databases (4 on
separate servers and 2 on the same server) into one 'master' database.
The tables being replicated all have unique ID ranges
How to I organise the replication so that the subscriber database can allow
inserts which fit into the ID ranges for the related Publishers database.
ie All inserts with a Lab_ID = 'L' should ONLY be replicated back to the
associated publisher.
I am not familiar with the automatic identity range handling .. can anyone
point me to an article about how this works ?
any help would be appreciated
cheers
mike
Mike,
as you've got multiple publishers, just ordinary filters will work to
restrict the flow of data to each publisher. For identity range handling,
you'll need to design each publisher's range yourself. The subscriber table
can be created during the first initialization, and all others are nosync
ones. So, the subscriber's identity range is defined after the first
initialization, and subsequent publications need to be sure not to overlap
with this range. Make the ranges large, because assignment of another range
might cause an overlap, so if the range is so big there will never be any
need to reset then this is best.
Alternatively, all subscriptions can be nosync ones.
These might help:
http://www.replicationanswers.com/No...alizations.asp
http://www.replicationanswers.com/ManualIdentities.asp
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

Sunday, March 25, 2012

Connfig Replication via Internet

I want to replicate data via Internet using FTP Server, i have SQL 2K with SP3. i set up client network as
- Server alias: my local server's name
- Server Name: ip address on internet
- Network libraries: TCP/IP
- Port : 1433
But i connect using Enterprise Manage to SQL Server then it errors:
A Connection could not be established to Dis-server ( Dis-server is my servername)
Reason: SQL Server does not exist or accessed denied
ConnectionOpen(Connect())..
please help me..tks
Regards
NBtri
from the subscriber can you ping your publisher?
On your publisher and subscriber you have to configure the subsciber and
publisher using client network utility.
Make sure that the publsiher and subscriber are listed in the hosts file
(thanks Paul Ibison for this tidbit of tidbitosity)
Then on your Publisher go to Tools - replication - Configure Publishers,
subscribers, distributors, click on the subscribers tab, and click on the
check box to the right of your subscriber server name. Ensure you are using
a SQL Server account, and enter the subscriber sa (or an account in the
system administrator role) onthe subscriber and its password.
Then on your subscriber, set up a pull subscription.
"NBTri" <anonymous@.discussions.microsoft.com> wrote in message
news:8ABF42AE-6921-4A63-8479-CD7910909F89@.microsoft.com...
> I want to replicate data via Internet using FTP Server, i have SQL 2K with
SP3. i set up client network as
> - Server alias: my local server's name
> - Server Name: ip address on internet
> - Network libraries: TCP/IP
> - Port : 1433
> But i connect using Enterprise Manage to SQL Server then it errors:
> A Connection could not be established to Dis-server ( Dis-server is my
servername)
> Reason: SQL Server does not exist or accessed denied
> ConnectionOpen(Connect())..
>
> please help me..tks
> Regards
> NBtri
>

Connenting to a another SQL Server using Transact-SQL

Hi,

I am finding a solution for how to connect to a SQL server by using Transact-SQL.

Suppose that there are two SQL Servers Call 'A' and 'B'.I just want to connect to the SQL Server 'B' from SQL Server 'A' to Insert data.

How can i do this only using Transact-SQL without using any programming language.

Thanks,

You will have to setup Server B as a linked server on Server A first. Then you will ba able to use frou part notation to access the Server:

Select * from SomeLinkedServerName.DatabaseName.OwnerOrSchema.Objectname

See the linked server topic in the BOL for more information.

Jens K. Suessmeyer.

http://www.sqlserver2005.de

Connectivity problem-please read

Hi,
I have 3 SQL servers 7, and since yesterday, some of my
clients started receiving different error messages in the
middle of doing something like reporting, or editing,
however when i checked the event logs on all servers,
there is no error message there. all different messages
include a "General network error" for example one of them
is:
SQL Server Message 10054, Possible network error Write to
SQL Server Failed. General Network Error. Check your
documentation. Debugging info: sqlCompile...
Does anyone have any idea how to deal with this problem, I
am monitoring different switches but cannot see any
problem. Also checked ODBC settings all fine, and we have
these setting for a couple of years with no problem.
Thanks in advance for any help-RobHi Rob,
10054 is usually seen when the underlying tcp session is dropped. The
only way to tshoot this is to make network traces from the client capturing
the problem. Then work with your network staff to resolve them. More than
likely, the cause is a dropped tcp session.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Hi Kevin,
Can you explain a bit more, How can I make the Network
trace? Basically, I can not see any problem with the
network, what kind of network problems should I looking
for?
Thanks a lot-Rob
>--Original Message--
>Hi Rob,
> 10054 is usually seen when the underlying tcp session
is dropped. The
>only way to tshoot this is to make network traces from
the client capturing
>the problem. Then work with your network staff to
resolve them. More than
>likely, the cause is a dropped tcp session.
>Thanks,
>Kevin McDonnell
>Microsoft Corporation
>This posting is provided AS IS with no warranties, and
confers no rights.
>
>.
>|||Hi Rob,
So all SQL connections from clients are supported by underlying tcp or
smb sessions. ODBC and OLEdb applications rely on the integrity of the
underlying network session. If the session is torn down, then the
application will fail. In our case we tend to report "general network
Error".
So, if this is the error you're seeing, you need to make network traces
from the client and see if the underlying tcp or smb session was dropped.
Then work with your network team to resolve it.
Otherwise, you can make the traces and open a case with us to help do the
review.
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.sqlsql

Connectivity problem-please read

Hi,
I have 3 SQL servers 7, and since yesterday, some of my
clients started receiving different error messages in the
middle of doing something like reporting, or editing,
however when i checked the event logs on all servers,
there is no error message there. all different messages
include a "General network error" for example one of them
is:
SQL Server Message 10054, Possible network error Write to
SQL Server Failed. General Network Error. Check your
documentation. Debugging info: sqlCompile...
Does anyone have any idea how to deal with this problem, I
am monitoring different switches but cannot see any
problem. Also checked ODBC settings all fine, and we have
these setting for a couple of years with no problem.
Thanks in advance for any help-Rob
Hi Rob,
10054 is usually seen when the underlying tcp session is dropped. The
only way to tshoot this is to make network traces from the client capturing
the problem. Then work with your network staff to resolve them. More than
likely, the cause is a dropped tcp session.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
|||Hi Kevin,
Can you explain a bit more, How can I make the Network
trace? Basically, I can not see any problem with the
network, what kind of network problems should I looking
for?
Thanks a lot-Rob
>--Original Message--
>Hi Rob,
> 10054 is usually seen when the underlying tcp session
is dropped. The
>only way to tshoot this is to make network traces from
the client capturing
>the problem. Then work with your network staff to
resolve them. More than
>likely, the cause is a dropped tcp session.
>Thanks,
>Kevin McDonnell
>Microsoft Corporation
>This posting is provided AS IS with no warranties, and
confers no rights.
>
>.
>
|||Hi Rob,
So all SQL connections from clients are supported by underlying tcp or
smb sessions. ODBC and OLEdb applications rely on the integrity of the
underlying network session. If the session is torn down, then the
application will fail. In our case we tend to report "general network
Error".
So, if this is the error you're seeing, you need to make network traces
from the client and see if the underlying tcp or smb session was dropped.
Then work with your network team to resolve it.
Otherwise, you can make the traces and open a case with us to help do the
review.
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

Connectivity Problem for Expert

Hi All,
I have an intriguing problem and I wanted to see if somebody could help me.
ENVIRONMENT:
Server Side: 2 identical Windows servers 2000 with SQL Server 2000
Enterprise Edition SP3a
Client Side: workstation with Windows 2000 PRO
Protocols enabled in the server and client: TCP/IP and Named Pipes.
1) I create a new user in the domain, DM001\testesql
2) I create a new login in the SQL Server (one in each SQL Server). For
this, I used script below:
EXEC sp_grantlogin 'DM001\testesql'
GO
EXEC sp_defaultdb 'DM001\testesql', 'Pubs'
GO
USE Pubs
GO
EXEC sp_grantdbaccess 'DM001\testesql', 'testesql'
GO
EXEC sp_addrolemember 'db_owner', 'testesql'
GO
sp_helpuser
THE PROBLEM:
After this, I connected myself in one workstation with the new user of
domain (DM001\testesql)and try a connection via osql utility using the
command line below. Well, in 1 server the connection was made successfully
and got the waited result, but in the other server I received the error:
Login failed for user '(null)'. Reason: Not associated with a trusted SQL
Server connection.
Comand line for SQLServer1 ==> successfully
C:\osql - SSQLServer1 - and - Q"select TOP 1 au_lname, au_fname from
pubs..authors".
--Result:
au_lname au_fname
--- --
Bennet Abraham
(1 row(s) affected)
Comand line for SQLServer2 ==> failed
C:\osql - SSQLServer2 - and - Q"select TOP 1 au_lname, au_fname from
pubs..authors".
Login failed for user '(null)'. Reason: Not associated with a trusted SQL
Server connection.
Please, somebody has idea of that can be happening?
Thx
Nilton Pinheiro
Message posted via http://www.droptable.com
Sorry... SQL Server is set up to use Mixed Mode Authentication in both the
servers.
Thx
Nilton
Message posted via http://www.droptable.com
|||Hi... I solve this problem change permission in Local Policy
thx
Message posted via http://www.droptable.com
|||If you try to connect to a SQL Server using windows
authentication and the error is:
Login failed for user '(null)'.
this generally indicates that the user can't be validated
through the domain controller or the local security database
so null is passed to SQL Server. So it's generally
indicative of an issue with the account, access to the
domain controller or something along those lines.
Check the event logs on the client PC and look for any
network, domain related issues. Check the event logs on the
DC as well.
-Sue
On Wed, 04 May 2005 20:33:12 GMT, "Nilton Pinheiro via
droptable.com" <forum@.nospam.droptable.com> wrote:

>Hi All,
>I have an intriguing problem and I wanted to see if somebody could help me.
>ENVIRONMENT:
>Server Side: 2 identical Windows servers 2000 with SQL Server 2000
>Enterprise Edition SP3a
>Client Side: workstation with Windows 2000 PRO
>Protocols enabled in the server and client: TCP/IP and Named Pipes.
>1) I create a new user in the domain, DM001\testesql
>2) I create a new login in the SQL Server (one in each SQL Server). For
>this, I used script below:
>EXEC sp_grantlogin 'DM001\testesql'
>GO
>EXEC sp_defaultdb 'DM001\testesql', 'Pubs'
>GO
>USE Pubs
>GO
>EXEC sp_grantdbaccess 'DM001\testesql', 'testesql'
>GO
>EXEC sp_addrolemember 'db_owner', 'testesql'
>GO
>sp_helpuser
>
>THE PROBLEM:
>After this, I connected myself in one workstation with the new user of
>domain (DM001\testesql)and try a connection via osql utility using the
>command line below. Well, in 1 server the connection was made successfully
>and got the waited result, but in the other server I received the error:
>Login failed for user '(null)'. Reason: Not associated with a trusted SQL
>Server connection.
>Comand line for SQLServer1 ==> successfully
>C:\osql - SSQLServer1 - and - Q"select TOP 1 au_lname, au_fname from
>pubs..authors".
>--Result:
>au_lname au_fname
>--- --
>Bennet Abraham
>(1 row(s) affected)
>Comand line for SQLServer2 ==> failed
>C:\osql - SSQLServer2 - and - Q"select TOP 1 au_lname, au_fname from
>pubs..authors".
>Login failed for user '(null)'. Reason: Not associated with a trusted SQL
>Server connection.
>Please, somebody has idea of that can be happening?
>Thx
>Nilton Pinheiro
|||Hi Nilton,
I am having similar issue, can you share what steps you followed to resolve
this issue.
--Manoj
"Nilton Pinheiro via droptable.com" wrote:

> Hi... I solve this problem change permission in Local Policy
> thx
> --
> Message posted via http://www.droptable.com
>

Connectivity Problem for Expert

Hi All,
I have an intriguing problem and I wanted to see if somebody could help me.
ENVIRONMENT:
Server Side: 2 identical Windows servers 2000 with SQL Server 2000
Enterprise Edition SP3a
Client Side: workstation with Windows 2000 PRO
Protocols enabled in the server and client: TCP/IP and Named Pipes.
1) I create a new user in the domain, DM001\testesql
2) I create a new login in the SQL Server (one in each SQL Server). For
this, I used script below:
EXEC sp_grantlogin 'DM001\testesql'
GO
EXEC sp_defaultdb 'DM001\testesql', 'Pubs'
GO
USE Pubs
GO
EXEC sp_grantdbaccess 'DM001\testesql', 'testesql'
GO
EXEC sp_addrolemember 'db_owner', 'testesql'
GO
sp_helpuser
THE PROBLEM:
After this, I connected myself in one workstation with the new user of
domain (DM001\testesql)and try a connection via osql utility using the
command line below. Well, in 1 server the connection was made successfully
and got the waited result, but in the other server I received the error:
Login failed for user '(null)'. Reason: Not associated with a trusted SQL
Server connection.
Comand line for SQLServer1 ==> successfully
C:\osql - SSQLServer1 - and - Q"select TOP 1 au_lname, au_fname from
pubs..authors".
--Result:
au_lname au_fname
--- --
Bennet Abraham
(1 row(s) affected)
Comand line for SQLServer2 ==> failed
C:\osql - SSQLServer2 - and - Q"select TOP 1 au_lname, au_fname from
pubs..authors".
Login failed for user '(null)'. Reason: Not associated with a trusted SQL
Server connection.
Please, somebody has idea of that can be happening?
Thx
Nilton Pinheiro
Message posted via http://www.droptable.comSorry... SQL Server is set up to use Mixed Mode Authentication in both the
servers.
Thx
Nilton
Message posted via http://www.droptable.com|||Hi... I solve this problem change permission in Local Policy
thx
Message posted via http://www.droptable.com|||If you try to connect to a SQL Server using windows
authentication and the error is:
Login failed for user '(null)'.
this generally indicates that the user can't be validated
through the domain controller or the local security database
so null is passed to SQL Server. So it's generally
indicative of an issue with the account, access to the
domain controller or something along those lines.
Check the event logs on the client PC and look for any
network, domain related issues. Check the event logs on the
DC as well.
-Sue
On Wed, 04 May 2005 20:33:12 GMT, "Nilton Pinheiro via
droptable.com" <forum@.nospam.droptable.com> wrote:

>Hi All,
>I have an intriguing problem and I wanted to see if somebody could help me.
>ENVIRONMENT:
>Server Side: 2 identical Windows servers 2000 with SQL Server 2000
>Enterprise Edition SP3a
>Client Side: workstation with Windows 2000 PRO
>Protocols enabled in the server and client: TCP/IP and Named Pipes.
>1) I create a new user in the domain, DM001\testesql
>2) I create a new login in the SQL Server (one in each SQL Server). For
>this, I used script below:
>EXEC sp_grantlogin 'DM001\testesql'
>GO
>EXEC sp_defaultdb 'DM001\testesql', 'Pubs'
>GO
>USE Pubs
>GO
>EXEC sp_grantdbaccess 'DM001\testesql', 'testesql'
>GO
>EXEC sp_addrolemember 'db_owner', 'testesql'
>GO
>sp_helpuser
>
>THE PROBLEM:
>After this, I connected myself in one workstation with the new user of
>domain (DM001\testesql)and try a connection via osql utility using the
>command line below. Well, in 1 server the connection was made successfully
>and got the waited result, but in the other server I received the error:
>Login failed for user '(null)'. Reason: Not associated with a trusted SQL
>Server connection.
>Comand line for SQLServer1 ==> successfully
>C:\osql - SSQLServer1 - and - Q"select TOP 1 au_lname, au_fname from
>pubs..authors".
>--Result:
>au_lname au_fname
>--- --
>Bennet Abraham
>(1 row(s) affected)
>Comand line for SQLServer2 ==> failed
>C:\osql - SSQLServer2 - and - Q"select TOP 1 au_lname, au_fname from
>pubs..authors".
>Login failed for user '(null)'. Reason: Not associated with a trusted SQL
>Server connection.
>Please, somebody has idea of that can be happening?
>Thx
>Nilton Pinheiro|||Hi Nilton,
I am having similar issue, can you share what steps you followed to resolve
this issue.
--Manoj
"Nilton Pinheiro via droptable.com" wrote:

> Hi... I solve this problem change permission in Local Policy
> thx
> --
> Message posted via http://www.droptable.com
>

Connectivity problem

Hi,
I have 3 SQL servers 7, and since yesterday, some of my
clients started receiving different error messages in the
middle of doing something like reporting, or editing.
(they run different applications).
However when i checked the event logs on all servers there
is no error message there. all different messages include
a "General network error" for example one of them is:
SQL Server Message 10054, Possible network error Write to
SQL Server Failed. General Network Error. Check your
documentation. Debugging info: sqlCompile...
Usually if I reboot their WS, thats temperary fixs their
problem.
Does anyone have any idea how to deal with this problem, I
am monitoring different switches but cannot see any
problem. Also checked ODBC settings all fine, and we have
these setting for a couple of years with no problem.
Thanks in advance for any help-RobAre the errors occurring on all 3 SQL Servers or just one SQL Server?
How is the health of the network? Are the switches in good working order?
How about the NIC's in the SQL Server machines? Is your DNS acting up?
What service packs have you applied recently to any equipment in the process
(Client, Server, routers/switches etc.).
What has changed in the last few weeks?
Rick Sawtell
MCT, MCSD, MCDBA
"Rob" <Rob@.nul.ca> wrote in message
news:d37d01c48ab6$39d66790$a601280a@.phx.gbl...
> Hi,
> I have 3 SQL servers 7, and since yesterday, some of my
> clients started receiving different error messages in the
> middle of doing something like reporting, or editing.
> (they run different applications).
> However when i checked the event logs on all servers there
> is no error message there. all different messages include
> a "General network error" for example one of them is:
> SQL Server Message 10054, Possible network error Write to
> SQL Server Failed. General Network Error. Check your
> documentation. Debugging info: sqlCompile...
> Usually if I reboot their WS, thats temperary fixs their
> problem.
> Does anyone have any idea how to deal with this problem, I
> am monitoring different switches but cannot see any
> problem. Also checked ODBC settings all fine, and we have
> these setting for a couple of years with no problem.
> Thanks in advance for any help-Rob
>|||On 2 of them. The network health is good and I can not see
any problem. As long as I am aware, we havent changed
anything recently and this problem startd since a couple
days ago.
Rob

>--Original Message--
>Are the errors occurring on all 3 SQL Servers or just one
SQL Server?
>How is the health of the network? Are the switches in
good working order?
>How about the NIC's in the SQL Server machines? Is your
DNS acting up?
>What service packs have you applied recently to any
equipment in the process
>(Client, Server, routers/switches etc.).
>What has changed in the last few weeks?
>
>Rick Sawtell
>MCT, MCSD, MCDBA
>
>
>"Rob" <Rob@.nul.ca> wrote in message
>news:d37d01c48ab6$39d66790$a601280a@.phx.gbl...
the[vbcol=seagreen]
there[vbcol=seagreen]
include[vbcol=seagreen]
to[vbcol=seagreen]
problem, I[vbcol=seagreen]
have[vbcol=seagreen]
>
>.
>|||Hi Bob,
Thanks for using MSDN Managed Newsgroup!
From your descriptions, I understood that your SQL7 received different
error and General Network Error. Have I understood you? If their is
anything I misunderstood, please feel free to let me know.
First of all, Would you please show me a detailed descriptions of what kind
of error message it will show? Is it possible for you to paste your latest
error log here?
Secondly, based on my scope, "General network error" doesn't mean a network
issue in most cases, it is a very common error that I am afraid we need
more time troubleshooting.
Thirdly, you said it will temperarily fix the problem by rebooting. How
long after rebooting will this kind of error occurs again?
Last but not the least, if it is an urgent one, you can contact Microsoft
Product Support directly to discuss additional support options you may have
available, by contacting us at 1-(800)936-5800 or by choosing one of the
options listed at
http://support.microsoft.com/defaul...d=sz;en-us;top.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!sqlsql

Connectivity problem

Hi,
I have 3 SQL servers 7, and since yesterday, some of my
clients started receiving different error messages in the
middle of doing something like reporting, or editing.
(they run different applications).
However when i checked the event logs on all servers there
is no error message there. all different messages include
a "General network error" for example one of them is:
SQL Server Message 10054, Possible network error Write to
SQL Server Failed. General Network Error. Check your
documentation. Debugging info: sqlCompile...
Usually if I reboot their WS, thats temperary fixs their
problem.
Does anyone have any idea how to deal with this problem, I
am monitoring different switches but cannot see any
problem. Also checked ODBC settings all fine, and we have
these setting for a couple of years with no problem.
Thanks in advance for any help-RobAre the errors occurring on all 3 SQL Servers or just one SQL Server?
How is the health of the network? Are the switches in good working order?
How about the NIC's in the SQL Server machines? Is your DNS acting up?
What service packs have you applied recently to any equipment in the process
(Client, Server, routers/switches etc.).
What has changed in the last few weeks?
Rick Sawtell
MCT, MCSD, MCDBA
"Rob" <Rob@.nul.ca> wrote in message
news:d37d01c48ab6$39d66790$a601280a@.phx.gbl...
> Hi,
> I have 3 SQL servers 7, and since yesterday, some of my
> clients started receiving different error messages in the
> middle of doing something like reporting, or editing.
> (they run different applications).
> However when i checked the event logs on all servers there
> is no error message there. all different messages include
> a "General network error" for example one of them is:
> SQL Server Message 10054, Possible network error Write to
> SQL Server Failed. General Network Error. Check your
> documentation. Debugging info: sqlCompile...
> Usually if I reboot their WS, thats temperary fixs their
> problem.
> Does anyone have any idea how to deal with this problem, I
> am monitoring different switches but cannot see any
> problem. Also checked ODBC settings all fine, and we have
> these setting for a couple of years with no problem.
> Thanks in advance for any help-Rob
>|||On 2 of them. The network health is good and I can not see
any problem. As long as I am aware, we havent changed
anything recently and this problem startd since a couple
days ago.
Rob
>--Original Message--
>Are the errors occurring on all 3 SQL Servers or just one
SQL Server?
>How is the health of the network? Are the switches in
good working order?
>How about the NIC's in the SQL Server machines? Is your
DNS acting up?
>What service packs have you applied recently to any
equipment in the process
>(Client, Server, routers/switches etc.).
>What has changed in the last few weeks?
>
>Rick Sawtell
>MCT, MCSD, MCDBA
>
>
>"Rob" <Rob@.nul.ca> wrote in message
>news:d37d01c48ab6$39d66790$a601280a@.phx.gbl...
>> Hi,
>> I have 3 SQL servers 7, and since yesterday, some of my
>> clients started receiving different error messages in
the
>> middle of doing something like reporting, or editing.
>> (they run different applications).
>> However when i checked the event logs on all servers
there
>> is no error message there. all different messages
include
>> a "General network error" for example one of them is:
>> SQL Server Message 10054, Possible network error Write
to
>> SQL Server Failed. General Network Error. Check your
>> documentation. Debugging info: sqlCompile...
>> Usually if I reboot their WS, thats temperary fixs their
>> problem.
>> Does anyone have any idea how to deal with this
problem, I
>> am monitoring different switches but cannot see any
>> problem. Also checked ODBC settings all fine, and we
have
>> these setting for a couple of years with no problem.
>> Thanks in advance for any help-Rob
>>
>
>.
>|||Hi Bob,
Thanks for using MSDN Managed Newsgroup!
From your descriptions, I understood that your SQL7 received different
error and General Network Error. Have I understood you? If their is
anything I misunderstood, please feel free to let me know.
First of all, Would you please show me a detailed descriptions of what kind
of error message it will show? Is it possible for you to paste your latest
error log here?
Secondly, based on my scope, "General network error" doesn't mean a network
issue in most cases, it is a very common error that I am afraid we need
more time troubleshooting.
Thirdly, you said it will temperarily fix the problem by rebooting. How
long after rebooting will this kind of error occurs again?
Last but not the least, if it is an urgent one, you can contact Microsoft
Product Support directly to discuss additional support options you may have
available, by contacting us at 1-(800)936-5800 or by choosing one of the
options listed at
http://support.microsoft.com/default.aspx?scid=sz;en-us;top.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!

Connectivity problem

Hi,
I have 3 SQL servers 7, and since yesterday, some of my
clients started receiving different error messages in the
middle of doing something like reporting, or editing.
(they run different applications).
However when i checked the event logs on all servers there
is no error message there. all different messages include
a "General network error" for example one of them is:
SQL Server Message 10054, Possible network error Write to
SQL Server Failed. General Network Error. Check your
documentation. Debugging info: sqlCompile...
Usually if I reboot their WS, thats temperary fixs their
problem.
Does anyone have any idea how to deal with this problem, I
am monitoring different switches but cannot see any
problem. Also checked ODBC settings all fine, and we have
these setting for a couple of years with no problem.
Thanks in advance for any help-Rob
Are the errors occurring on all 3 SQL Servers or just one SQL Server?
How is the health of the network? Are the switches in good working order?
How about the NIC's in the SQL Server machines? Is your DNS acting up?
What service packs have you applied recently to any equipment in the process
(Client, Server, routers/switches etc.).
What has changed in the last few weeks?
Rick Sawtell
MCT, MCSD, MCDBA
"Rob" <Rob@.nul.ca> wrote in message
news:d37d01c48ab6$39d66790$a601280a@.phx.gbl...
> Hi,
> I have 3 SQL servers 7, and since yesterday, some of my
> clients started receiving different error messages in the
> middle of doing something like reporting, or editing.
> (they run different applications).
> However when i checked the event logs on all servers there
> is no error message there. all different messages include
> a "General network error" for example one of them is:
> SQL Server Message 10054, Possible network error Write to
> SQL Server Failed. General Network Error. Check your
> documentation. Debugging info: sqlCompile...
> Usually if I reboot their WS, thats temperary fixs their
> problem.
> Does anyone have any idea how to deal with this problem, I
> am monitoring different switches but cannot see any
> problem. Also checked ODBC settings all fine, and we have
> these setting for a couple of years with no problem.
> Thanks in advance for any help-Rob
>
|||On 2 of them. The network health is good and I can not see
any problem. As long as I am aware, we havent changed
anything recently and this problem startd since a couple
days ago.
Rob

>--Original Message--
>Are the errors occurring on all 3 SQL Servers or just one
SQL Server?
>How is the health of the network? Are the switches in
good working order?
>How about the NIC's in the SQL Server machines? Is your
DNS acting up?
>What service packs have you applied recently to any
equipment in the process[vbcol=seagreen]
>(Client, Server, routers/switches etc.).
>What has changed in the last few weeks?
>
>Rick Sawtell
>MCT, MCSD, MCDBA
>
>
>"Rob" <Rob@.nul.ca> wrote in message
>news:d37d01c48ab6$39d66790$a601280a@.phx.gbl...
the[vbcol=seagreen]
there[vbcol=seagreen]
include[vbcol=seagreen]
to[vbcol=seagreen]
problem, I[vbcol=seagreen]
have
>
>.
>
|||Hi Bob,
Thanks for using MSDN Managed Newsgroup!
From your descriptions, I understood that your SQL7 received different
error and General Network Error. Have I understood you? If their is
anything I misunderstood, please feel free to let me know.
First of all, Would you please show me a detailed descriptions of what kind
of error message it will show? Is it possible for you to paste your latest
error log here?
Secondly, based on my scope, "General network error" doesn't mean a network
issue in most cases, it is a very common error that I am afraid we need
more time troubleshooting.
Thirdly, you said it will temperarily fix the problem by rebooting. How
long after rebooting will this kind of error occurs again?
Last but not the least, if it is an urgent one, you can contact Microsoft
Product Support directly to discuss additional support options you may have
available, by contacting us at 1-(800)936-5800 or by choosing one of the
options listed at
http://support.microsoft.com/default...=sz;en-us;top.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!

Thursday, March 22, 2012

connectivity in sql server with two diff public ip address

I 've two machines (Linux Servers) with firewall installed at two
geographical locations. Now I want to make replication of data using
sqlserver2000 from two other machines which are behind the two servers . Both
of them have have private IP address and they can access the internet
through the firewall . Now I have enabled the ports 1433 on both sides and
had given the IP address of the receiving machine at the sending machine
(Public IP at the network client -alias TCP/IP protocal) and vice versa.
Proper mapping of IP (public to private is done ) at the two servers.
But still I 'm getting the message, Failed to register the Sql Server
Pl help
Soumen,
you'll need to register an alias. Have a look at this article:
http://support.microsoft.com/?id=321822
(these may also be of interest
http://www.microsoft.com/resources/d...rt5/sqc07.mspx
http://support.microsoft.com/default...32&Product=sql)
HTH,
Paul Ibison
|||Did you define these two servers using Client Network Utiltity?
If you did, you can then create ODBC DSN's to them and test general
connectivity, or merely register these SQL Server as enabled Subscribers, or
register them in EM.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Soumen ( India)" <SoumenIndia@.discussions.microsoft.com> wrote in message
news:57461CAD-F259-4D49-8710-7217F7AFFE43@.microsoft.com...
> I 've two machines (Linux Servers) with firewall installed at two
> geographical locations. Now I want to make replication of data using
> sqlserver2000 from two other machines which are behind the two servers .
Both
> of them have have private IP address and they can access the internet
> through the firewall . Now I have enabled the ports 1433 on both sides and
> had given the IP address of the receiving machine at the sending machine
> (Public IP at the network client -alias TCP/IP protocal) and vice versa.
> Proper mapping of IP (public to private is done ) at the two servers.
> But still I 'm getting the message, Failed to register the Sql Server
> Pl help

Connectivity from Non Sql Servers

How would I configure a DB2, SAP Or Teradata as source in SSIS

How do you usually connect to them? If you have an ODBC driver then you should be able to do it.

I dare say there are issues aorund this but having never connected to these systems I can't tell you more than that. there are people on here that HAVE connected to these systems.

-Jamie

|||

Hi Jamie,

Thanks for the quick response, but base product of Sql Server 2k5 does not have these odbc drivers. Does microsoft provides these or we need to purchase these drivers.

Thanks

Dharmbir

|||

I have no idea. My guess is you will have to buy them.

-Jamie

|||MS provides a OLE DB driver for DB2. You can find it on the following page.

http://www.microsoft.com/downloads/details.aspx?familyid=D09C1D60-A13C-4479-9B91-9E8B9D835CDC&displaylang=en

As far as SAP goes, that depends on the underlying DB. If it runs

on Oracle, then MS offers a OLE DB driver, or you can download ODP.Net

from Oracle directly. If it runs on their SAPDB, which was handed

over to MySQL AB, then you should be able to find a OLEDB driver from www.mysql.com. MySQL rebranded the DB as MaxDB.

As far as Teradata goes, I've never worked with it so I can't be much help.

Larry Popesqlsql

Connectivity across Domains.

Can you create linked SQL servers across domains ? If so do you need to do
something different from a normal linked server ?
Thanks
Si
Hi
Unless you have a trust relationship between the 2 domains, you need to use
a SQL Server login for the linked server.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Simon" <Simon@.discussions.microsoft.com> wrote in message
news:89D3E5FE-EA5E-458F-B0FB-F91E1E8467D9@.microsoft.com...
> Can you create linked SQL servers across domains ? If so do you need to do
> something different from a normal linked server ?
> Thanks
> Si
|||The two domains do not trust each other and the Network guys have no
intention of changing this. However when i try and link the server with
username and password I still can`t connect to run a query on the linked
server.
Si
"Mike Epprecht (SQL MVP)" wrote:

> Hi
> Unless you have a trust relationship between the 2 domains, you need to use
> a SQL Server login for the linked server.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Simon" <Simon@.discussions.microsoft.com> wrote in message
> news:89D3E5FE-EA5E-458F-B0FB-F91E1E8467D9@.microsoft.com...
>
>
|||Make sure the request is going over TCP rather than named pipes. The latter
tries to enforce a network login even though you're using SQL
authentication.
Cheers,
'(' Jeff A. Stucker
\
Senior Consultant
www.rapidigm.com
"Simon" <Simon@.discussions.microsoft.com> wrote in message
news:D01D0AB4-7741-4BE2-8DEF-A24AA303F1B7@.microsoft.com...[vbcol=seagreen]
> The two domains do not trust each other and the Network guys have no
> intention of changing this. However when i try and link the server with
> username and password I still can`t connect to run a query on the linked
> server.
> Si
> "Mike Epprecht (SQL MVP)" wrote:
|||And use an IP address for the server name.
-Sue
On Tue, 13 Dec 2005 05:17:07 -0800, "Simon"
<Simon@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>The two domains do not trust each other and the Network guys have no
>intention of changing this. However when i try and link the server with
>username and password I still can`t connect to run a query on the linked
>server.
>Si
>"Mike Epprecht (SQL MVP)" wrote:

Connectivity across Domains.

Can you create linked SQL servers across domains ? If so do you need to do
something different from a normal linked server ?
Thanks
SiHi
Unless you have a trust relationship between the 2 domains, you need to use
a SQL Server login for the linked server.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Simon" <Simon@.discussions.microsoft.com> wrote in message
news:89D3E5FE-EA5E-458F-B0FB-F91E1E8467D9@.microsoft.com...
> Can you create linked SQL servers across domains ? If so do you need to do
> something different from a normal linked server ?
> Thanks
> Si|||The two domains do not trust each other and the Network guys have no
intention of changing this. However when i try and link the server with
username and password I still can`t connect to run a query on the linked
server.
Si
"Mike Epprecht (SQL MVP)" wrote:

> Hi
> Unless you have a trust relationship between the 2 domains, you need to us
e
> a SQL Server login for the linked server.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Simon" <Simon@.discussions.microsoft.com> wrote in message
> news:89D3E5FE-EA5E-458F-B0FB-F91E1E8467D9@.microsoft.com...
>
>|||Make sure the request is going over TCP rather than named pipes. The latter
tries to enforce a network login even though you're using SQL
authentication.
Cheers,
'(' Jeff A. Stucker
\
Senior Consultant
www.rapidigm.com
"Simon" <Simon@.discussions.microsoft.com> wrote in message
news:D01D0AB4-7741-4BE2-8DEF-A24AA303F1B7@.microsoft.com...[vbcol=seagreen]
> The two domains do not trust each other and the Network guys have no
> intention of changing this. However when i try and link the server with
> username and password I still can`t connect to run a query on the linked
> server.
> Si
> "Mike Epprecht (SQL MVP)" wrote:
>|||And use an IP address for the server name.
-Sue
On Tue, 13 Dec 2005 05:17:07 -0800, "Simon"
<Simon@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>The two domains do not trust each other and the Network guys have no
>intention of changing this. However when i try and link the server with
>username and password I still can`t connect to run a query on the linked
>server.
>Si
>"Mike Epprecht (SQL MVP)" wrote:
>

Monday, March 19, 2012

ConnectionCheckForData((null)())?

Hi all,

I have 2 servers - Financial and Trilogy. Trilogy is a linked server on the Financial Database. It uses MSDASQL to link it. Now I have a insert trigger on one of the tables on the financial Database that inserts data to a table that resides on the trilogy database. A few days ago it was working fine. Any inserts into the financial table would insert data into the trilogy table, however now I get the following error when I try to an insert into the financial table....

Changed Language setting to Us_English
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionCheckForData((null)()).
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]General Network Error. Check your Network Documentation.

The only thing that has been done within these few days was a reboot of the trilogy server.

Also when I remove this trigger and do an insert into the financial table it works fine, so I unsure whether this error occurs due to ODBC or MSDTC?? Can anyone help with this?? And what causes this error and how do I go about fixing it??

Thanks
AnthonyThis sounds like a known issue. Please see article for info.

http://support.microsoft.com/?id=317852

Thursday, March 8, 2012

Connection to remote server using VPN

Hi - I am a relative newbie to setting up and configuring servers so am a
bit baffled by all the server techno-speak.
My issue - I have a client who is based about 40 miles away who want me to
do some database work for them. I am a freelancer and he is a small company
who relies on a non sql server specific moonlighter for tech support (it's
not as wing and prayer as it might seem!).
They bought MS Small Biz server which includes SQL 2000. I tried to install
it on my XPHome pc but came to the view that you need a 2000/2003 server to
run anything bigger than a 4Gb database. Given that the db will be much
bigger than 4Gb we therefore need to install SQL Server on his server and
run it as a sql server with me installing query analyser and eneterprise
manager on my PC and connect. All fine in theory. Now for security I am
assuming the best way to connect is by using VPN? If this is so, can any
one point me to any info on setting up my end + his end and what may be
required h/w + s/w etc?
His moonlight techie says I need a static IP address... I think I have a
dynamic one, and that all he need to do is set up some filters his end. I
also have a Lynksys router (BEFSR41) and Norton Proff Fiewall. He has router
and firewall his end.
I looked for past postings and find ref to this link
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad
but now it's dead.
Any help much appreciated!
Happy New Year.
Andythere is a thread going on at www.sqlservercentral.com
http://www.sqlservercentral.com/forum/link.asp?TOPIC_ID=19507
maybe that will get you on track
jobi
"Andreww" <andrew@.fake.com> wrote in message
news:kwyIb.2561$tH.23625741@.news-text.cableinet.net...
> Hi - I am a relative newbie to setting up and configuring servers so am a
> bit baffled by all the server techno-speak.
> My issue - I have a client who is based about 40 miles away who want me to
> do some database work for them. I am a freelancer and he is a small
company
> who relies on a non sql server specific moonlighter for tech support (it's
> not as wing and prayer as it might seem!).
> They bought MS Small Biz server which includes SQL 2000. I tried to
install
> it on my XPHome pc but came to the view that you need a 2000/2003 server
to
> run anything bigger than a 4Gb database. Given that the db will be much
> bigger than 4Gb we therefore need to install SQL Server on his server and
> run it as a sql server with me installing query analyser and eneterprise
> manager on my PC and connect. All fine in theory. Now for security I am
> assuming the best way to connect is by using VPN? If this is so, can any
> one point me to any info on setting up my end + his end and what may be
> required h/w + s/w etc?
> His moonlight techie says I need a static IP address... I think I have a
> dynamic one, and that all he need to do is set up some filters his end. I
> also have a Lynksys router (BEFSR41) and Norton Proff Fiewall. He has
router
> and firewall his end.
> I looked for past postings and find ref to this link
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad
> but now it's dead.
> Any help much appreciated!
> Happy New Year.
> Andy
>|||Jobi - thanks. I took a look and it seems more about how to set things up
once the VPN is set up... which helps.
In the firts instance, my question was about... is VPN the way to connect a
SQL client to server?
Help appreciated... even if it's that I'm in the wrong news group!
Regards
Andy
"jobi" <jobi@.reply2.group> wrote in message
news:bsud5v$fhp$1@.reader08.wxs.nl...
> there is a thread going on at www.sqlservercentral.com
> http://www.sqlservercentral.com/forum/link.asp?TOPIC_ID=19507
> maybe that will get you on track
> jobi
> "Andreww" <andrew@.fake.com> wrote in message
> news:kwyIb.2561$tH.23625741@.news-text.cableinet.net...
> > Hi - I am a relative newbie to setting up and configuring servers so am
a
> > bit baffled by all the server techno-speak.
> >
> > My issue - I have a client who is based about 40 miles away who want me
to
> > do some database work for them. I am a freelancer and he is a small
> company
> > who relies on a non sql server specific moonlighter for tech support
(it's
> > not as wing and prayer as it might seem!).
> >
> > They bought MS Small Biz server which includes SQL 2000. I tried to
> install
> > it on my XPHome pc but came to the view that you need a 2000/2003 server
> to
> > run anything bigger than a 4Gb database. Given that the db will be much
> > bigger than 4Gb we therefore need to install SQL Server on his server
and
> > run it as a sql server with me installing query analyser and eneterprise
> > manager on my PC and connect. All fine in theory. Now for security I am
> > assuming the best way to connect is by using VPN? If this is so, can
any
> > one point me to any info on setting up my end + his end and what may be
> > required h/w + s/w etc?
> >
> > His moonlight techie says I need a static IP address... I think I have a
> > dynamic one, and that all he need to do is set up some filters his end.
I
> > also have a Lynksys router (BEFSR41) and Norton Proff Fiewall. He has
> router
> > and firewall his end.
> >
> > I looked for past postings and find ref to this link
> >
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad
> > but now it's dead.
> >
> > Any help much appreciated!
> >
> > Happy New Year.
> >
> > Andy
> >
> >
>|||"In the firts instance, my question was about... is VPN the way to connect a
SQL client to server?"
Given what little knowledge I have about your situation, I would say that VPN is your best bet. It's going to be the most economical, practical, and easiest way to connect to your client using SQL. Anything else would be expensive and/or unsecure.
But that's just my opinion...
Hope this helps.
Shaun

Connection to MSDE fails

I'm troubleshooting a connection to an MSDE install. I tried to register
the MSDE install on the server's EM. The register server wizard shows the
laptop's MSDE install but it refuses to connect.
-No software firewall is running on the laptop
-I added TCP/IP using port 1433 to the MSDE install
-The MSDE server shows up when I browse for SQL servers on the network
-I've tried integrated security and SQL authentication but neither work.
-I can connect to the MSDE install from the laptop using both authentication
types
Any ideas why EM can browse the MSDE server but not connect?
I'm using MSDE 2000 sp3 and SQL Server 2000 sp3
Thanks
If you come up with an answer, I would appreciate notice. I am having
the same problem.
If I connect an .adp directly it is fine. Query Analyzer is fine.
I cannot connect to either remote SQL Server DB I have. It is very
frustrating.
Thank you. Sorry I can't help you either.
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||Check the SQL Errorlogs for the MSDE instance. See what protocols it's
listening on.
You should see Shared Memory, Named Pipes and TCP.
Also, the default security is Windows Authentication.
Next try connecting using either ISQL.exe or a Test ODBC DSN. You need the
OS error to tshoot the problem.
Example:
OS Error 53 == Network Name not found. (Named Pipe connection without
Netbios Name Resolution)
OS Error 10060 == TCP Connection Timeout
OS Error 10061 == TCP connection Refused. Possibly the client is
connecting on the wrong socket. Or the server isn't listening on tcp.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.