Exec/Query across servers (unlinked)

Can I exec/query across unlinked servers that are on the network but
physically different server instances? If so, how, please?
TIA!
RobertTake a look at OPENROWSET and OPENDATASOURCE in Books On line
Denis the SQL Menace
http://sqlservercode.blogspot.com/|||You can use OPENROWSET
SELECT *
FROM OPENROWSET('SQLOLEDB','otherinstance';'u
ser';'pwd',
'SELECT * FROM somedb.dbo.mytable')|||My bad...
I wasn't using fully qualified naming. I was using something like
ABC123.dbo.TableName instead of DEV.ABC123.dbo.TableName.
Thanks!
Robert
"Robert Davis" <radbase@.yahoo.com> wrote in message
news:OKtDvGkXGHA.3660@.TK2MSFTNGP04.phx.gbl...
> Can I exec/query across unlinked servers that are on the network but
> physically different server instances? If so, how, please?
> TIA!
> Robert
>

Exchange 5.5 email problem

I have an Active Directory network with an Exchange 5.5 server running on a
Windows NT box.
I am hosting 3 email domains on that box. For example lets call them
mydomain1.com, mydomain2.com and mydomain3.com.
All external emails come in and work just fine except for the mydomain3.com
emails. My internal Active Dirctory domain is mydomain3.com.
Currently my Exchange server on the NT box is pointing at the internal DNS
server that forwards requests to the outside. I was thinking my problem is
that and that I might need to have the NT box with Exchange on it use our
ISP DNS servers instead.
Any ideas? I read something about Active Directory Connector, but didn't
know if I need to look at that or how the DNS settings are set up on the
Exchange server.
Thanks...if anyone wants to email me directly...feel free!!
"CJ" <chrisj@.illicom.net> wrote:

>I have an Active Directory network with an Exchange 5.5 server running on a
>Windows NT box.
>I am hosting 3 email domains on that box. For example lets call them
>mydomain1.com, mydomain2.com and mydomain3.com.
>All external emails come in and work just fine except for the mydomain3.com
>emails. My internal Active Dirctory domain is mydomain3.com.
>Currently my Exchange server on the NT box is pointing at the internal DNS
>server that forwards requests to the outside. I was thinking my problem is
>that and that I might need to have the NT box with Exchange on it use our
>ISP DNS servers instead.
>Any ideas? I read something about Active Directory Connector, but didn't
>know if I need to look at that or how the DNS settings are set up on the
>Exchange server.
>Thanks...if anyone wants to email me directly...feel free!!
>
If your Exchange server is running without ADC then it's not AD aware
(but you'd worked that out)
The Internet Mail Service should receive mail for all three domains
and route them to wherever you need.
Can you confirm that all three domains are set to "Route Inbound"? Or
alternatively two of the domains are routed to a third domain (be it
1, 2 or 3)
Then you need to make sure that you are receiving the mails for
domain3.com in the first place. Is it a registered domain? Does it
have MX records that point to a valid A record in the ISP DNS?
If domain3 isn't valid then you're not going to get mail into it.
Check by doing an nslookup against all three domains and make sure
that they point to the same A record and that the A record matches the
IP address you want the mail delivered to.#
Mark Arnold MCSA MCSE+M MVP,
FAQ: http://www.swinc.com/resource/exchange.htm
Blog: http://www.msexchange.me.uk
|||Figured it out.. the problem ended up being i simply needed my Exchange
server to have the DNS settings for my ISP, not my internal DNS servers
"Mark Arnold [MVP]" <mark@.mvps.org> wrote in message
news:9gaif051c15fpakgru8be75a35dgaefh9p@.4ax.com... [vbcol=seagreen]
> "CJ" <chrisj@.illicom.net> wrote:
a[vbcol=seagreen]
mydomain3.com[vbcol=seagreen]
DNS[vbcol=seagreen]
is
> If your Exchange server is running without ADC then it's not AD aware
> (but you'd worked that out)
> The Internet Mail Service should receive mail for all three domains
> and route them to wherever you need.
> Can you confirm that all three domains are set to "Route Inbound"? Or
> alternatively two of the domains are routed to a third domain (be it
> 1, 2 or 3)
> Then you need to make sure that you are receiving the mails for
> domain3.com in the first place. Is it a registered domain? Does it
> have MX records that point to a valid A record in the ISP DNS?
> If domain3 isn't valid then you're not going to get mail into it.
> Check by doing an nslookup against all three domains and make sure
> that they point to the same A record and that the A record matches the
> IP address you want the mail delivered to.#
>
> Mark Arnold MCSA MCSE+M MVP,
> FAQ: http://www.swinc.com/resource/exchange.htm
> Blog: http://www.msexchange.me.uk

Excessive network usage with SQL 2000 to SQL 2005 transactional replication

We have a SQL2000 database (Publisher) replicating inserts and updates across a 10Mb link to a SQL 2005 database (Subscriber). The Publisher has two tables we are interested in, 1 with 50 columns and 1 with 15. Both tables have 6 insert/update triggers that fire when a change is made to update columns on the publisher database.

We have set up a pull transactional replication from the Subscriber to occur against the Publisher every minute. We have limited the subscription/replication configuration to Publsih 6 columns from table 1 and 4 from table 2. Any change occuring on any other columns in the Publisher are of no interest. The SQL 2005 database has a trigger on table 1 and table 2 to insert values into a third table. There are around 7,000 insert/updates on table 1 and 28,000 on table 2 per day. All fields in the tables are text.

We are seeing "excessive" network traffic occuring of approximately 1MB per minute (approx 2GB per 24 hrs). We also see that the Distributor databases are getting very large -- upto around 30GB and growing until they get culled. We have reduced the culling intrval from 72 hrs to 24 hours to reduce the size.

Does anyone have any suggestions as to how this "excessive" network traffic can be minimised and how the distributor database size can be minimised. I think that maybe they are both related?

Thanks,

Geoff

WA POLICE

is this merge or tran?

|||

i will guess it's merge replication. MErge replication does transfer a lot of metadata over the wire, you can see what's being replicated by running a profiler trace.

|||

sorry, i totally misread your thread, you do have transactional replication. You need to understand the data changes you are making at the publisher and what is getting replicated. Every change made to a table that is enabled for replication will get marked as a change that needs to be replicated. These changes, one by one, are inserted into the distribution database. So if your database is growing to 30 GB, you must either be doing a lot of inserts or updates, or you might be touching BLOB columns as well. You should investigate exactly what you're replicating to understand your scenario.

|||Thanks for the information Gerg. Yes we do have transactional and yes we have determined that the traffic seems to be related to the triggers on the publisher. We are looking at ways to limit these at present without impacting the business functions that use that database.

Excessive network usage with SQL 2000 to SQL 2005 transactional replication

We have a SQL2000 database (Publisher) replicating inserts and updates across a 10Mb link to a SQL 2005 database (Subscriber). The Publisher has two tables we are interested in, 1 with 50 columns and 1 with 15. Both tables have 6 insert/update triggers that fire when a change is made to update columns on the publisher database.

We have set up a pull transactional replication from the Subscriber to occur against the Publisher every minute. We have limited the subscription/replication configuration to Publsih 6 columns from table 1 and 4 from table 2. Any change occuring on any other columns in the Publisher are of no interest. The SQL 2005 database has a trigger on table 1 and table 2 to insert values into a third table. There are around 7,000 insert/updates on table 1 and 28,000 on table 2 per day. All fields in the tables are text.

We are seeing "excessive" network traffic occuring of approximately 1MB per minute (approx 2GB per 24 hrs). We also see that the Distributor databases are getting very large -- upto around 30GB and growing until they get culled. We have reduced the culling intrval from 72 hrs to 24 hours to reduce the size.

Does anyone have any suggestions as to how this "excessive" network traffic can be minimised and how the distributor database size can be minimised. I think that maybe they are both related?

Thanks,

Geoff

WA POLICE

is this merge or tran?

|||

i will guess it's merge replication. MErge replication does transfer a lot of metadata over the wire, you can see what's being replicated by running a profiler trace.

|||

sorry, i totally misread your thread, you do have transactional replication. You need to understand the data changes you are making at the publisher and what is getting replicated. Every change made to a table that is enabled for replication will get marked as a change that needs to be replicated. These changes, one by one, are inserted into the distribution database. So if your database is growing to 30 GB, you must either be doing a lot of inserts or updates, or you might be touching BLOB columns as well. You should investigate exactly what you're replicating to understand your scenario.

|||Thanks for the information Gerg. Yes we do have transactional and yes we have determined that the traffic seems to be related to the triggers on the publisher. We are looking at ways to limit these at present without impacting the business functions that use that database.

Excessive network usage with SQL 2000 to SQL 2005 transactional replication

We have a SQL2000 database (Publisher) replicating inserts and updates across a 10Mb link to a SQL 2005 database (Subscriber). The Publisher has two tables we are interested in, 1 with 50 columns and 1 with 15. Both tables have 6 insert/update triggers that fire when a change is made to update columns on the publisher database.

We have set up a pull transactional replication from the Subscriber to occur against the Publisher every minute. We have limited the subscription/replication configuration to Publsih 6 columns from table 1 and 4 from table 2. Any change occuring on any other columns in the Publisher are of no interest. The SQL 2005 database has a trigger on table 1 and table 2 to insert values into a third table. There are around 7,000 insert/updates on table 1 and 28,000 on table 2 per day. All fields in the tables are text.

We are seeing "excessive" network traffic occuring of approximately 1MB per minute (approx 2GB per 24 hrs). We also see that the Distributor databases are getting very large -- upto around 30GB and growing until they get culled. We have reduced the culling intrval from 72 hrs to 24 hours to reduce the size.

Does anyone have any suggestions as to how this "excessive" network traffic can be minimised and how the distributor database size can be minimised. I think that maybe they are both related?

Thanks,

Geoff

WA POLICE

is this merge or tran?

|||

i will guess it's merge replication. MErge replication does transfer a lot of metadata over the wire, you can see what's being replicated by running a profiler trace.

|||

sorry, i totally misread your thread, you do have transactional replication. You need to understand the data changes you are making at the publisher and what is getting replicated. Every change made to a table that is enabled for replication will get marked as a change that needs to be replicated. These changes, one by one, are inserted into the distribution database. So if your database is growing to 30 GB, you must either be doing a lot of inserts or updates, or you might be touching BLOB columns as well. You should investigate exactly what you're replicating to understand your scenario.

|||Thanks for the information Gerg. Yes we do have transactional and yes we have determined that the traffic seems to be related to the triggers on the publisher. We are looking at ways to limit these at present without impacting the business functions that use that database.

Excessive network usage with SQL 2000 to SQL 2005 transactional replication

We have a SQL2000 database (Publisher) replicating inserts and updates across a 10Mb link to a SQL 2005 database (Subscriber). The Publisher has two tables we are interested in, 1 with 50 columns and 1 with 15. Both tables have 6 insert/update triggers that fire when a change is made to update columns on the publisher database.

We have set up a pull transactional replication from the Subscriber to occur against the Publisher every minute. We have limited the subscription/replication configuration to Publsih 6 columns from table 1 and 4 from table 2. Any change occuring on any other columns in the Publisher are of no interest. The SQL 2005 database has a trigger on table 1 and table 2 to insert values into a third table. There are around 7,000 insert/updates on table 1 and 28,000 on table 2 per day. All fields in the tables are text.

We are seeing "excessive" network traffic occuring of approximately 1MB per minute (approx 2GB per 24 hrs). We also see that the Distributor databases are getting very large -- upto around 30GB and growing until they get culled. We have reduced the culling intrval from 72 hrs to 24 hours to reduce the size.

Does anyone have any suggestions as to how this "excessive" network traffic can be minimised and how the distributor database size can be minimised. I think that maybe they are both related?

Thanks,

Geoff

WA POLICE

is this merge or tran?

|||

i will guess it's merge replication. MErge replication does transfer a lot of metadata over the wire, you can see what's being replicated by running a profiler trace.

|||

sorry, i totally misread your thread, you do have transactional replication. You need to understand the data changes you are making at the publisher and what is getting replicated. Every change made to a table that is enabled for replication will get marked as a change that needs to be replicated. These changes, one by one, are inserted into the distribution database. So if your database is growing to 30 GB, you must either be doing a lot of inserts or updates, or you might be touching BLOB columns as well. You should investigate exactly what you're replicating to understand your scenario.

|||

Thanks for the information Gerg. Yes we do have transactional and yes we have determined that the traffic seems to be related to the triggers on the publisher. We are looking at ways to limit these at present without impacting the business functions that use that database.

excessive network traffic

Hi all,
I have a Win2000 server with Exchange2003 and SQL
server2000 SP1.
The system seems to work OK, but after about 1 hour after
startup, the SQL server starts to generate networktraffic
that completely floods the network. It is now impossible
to log into the server, get on the network or access the
internet from any workstation that is connected to the
network. In about one hour more than 50.000.000 network
packets are sent into space. When I disconnect the
internet connection, it just continues to do so. When I
stop the SQL service in the service manager, traffic stops
and everything works again.
Any thoughts?
Piet Koenekoop
"Piet Koenekoop" <pietkoenekoop@.hotmail.com> wrote in message
news:1baf501c42130$42cc0430$a501280a@.phx.gbl...
> Hi all,
> I have a Win2000 server with Exchange2003 and SQL
> server2000 SP1.
> The system seems to work OK, but after about 1 hour after
> startup, the SQL server starts to generate networktraffic
> that completely floods the network. It is now impossible
> to log into the server, get on the network or access the
> internet from any workstation that is connected to the
> network. In about one hour more than 50.000.000 network
> packets are sent into space. When I disconnect the
> internet connection, it just continues to do so. When I
> stop the SQL service in the service manager, traffic stops
> and everything works again.
> Any thoughts?
I'm no expert, but the symtoms looks like Slammer virus.
Steven Ung
"The source of all greatness lies within you" - Anonymous
|||Yep, looks like the slammer virus to me as well...
Update your SQL Server to SP3a, and reboot... and life gets good again...
"Piet Koenekoop" <pietkoenekoop@.hotmail.com> wrote in message
news:1baf501c42130$42cc0430$a501280a@.phx.gbl...
> Hi all,
> I have a Win2000 server with Exchange2003 and SQL
> server2000 SP1.
> The system seems to work OK, but after about 1 hour after
> startup, the SQL server starts to generate networktraffic
> that completely floods the network. It is now impossible
> to log into the server, get on the network or access the
> internet from any workstation that is connected to the
> network. In about one hour more than 50.000.000 network
> packets are sent into space. When I disconnect the
> internet connection, it just continues to do so. When I
> stop the SQL service in the service manager, traffic stops
> and everything works again.
> Any thoughts?
> Piet Koenekoop
|||Thanks a lot for the two suggestions. The Slammer virus was not detected by the AV software, but the installation of SP3 has solved my problem.
Piet Koenekoop

excessive network traffic

Hi all,
I have a Win2000 server with Exchange2003 and SQL
server2000 SP1.
The system seems to work OK, but after about 1 hour after
startup, the SQL server starts to generate networktraffic
that completely floods the network. It is now impossible
to log into the server, get on the network or access the
internet from any workstation that is connected to the
network. In about one hour more than 50.000.000 network
packets are sent into space. When I disconnect the
internet connection, it just continues to do so. When I
stop the SQL service in the service manager, traffic stops
and everything works again.
Any thoughts'
Piet Koenekoop"Piet Koenekoop" <pietkoenekoop@.hotmail.com> wrote in message
news:1baf501c42130$42cc0430$a501280a@.phx
.gbl...
> Hi all,
> I have a Win2000 server with Exchange2003 and SQL
> server2000 SP1.
> The system seems to work OK, but after about 1 hour after
> startup, the SQL server starts to generate networktraffic
> that completely floods the network. It is now impossible
> to log into the server, get on the network or access the
> internet from any workstation that is connected to the
> network. In about one hour more than 50.000.000 network
> packets are sent into space. When I disconnect the
> internet connection, it just continues to do so. When I
> stop the SQL service in the service manager, traffic stops
> and everything works again.
> Any thoughts'
I'm no expert, but the symtoms looks like Slammer virus.
--
Steven Ung
"The source of all greatness lies within you" - Anonymous|||Yep, looks like the slammer virus to me as well...
Update your SQL Server to SP3a, and reboot... and life gets good again...
"Piet Koenekoop" <pietkoenekoop@.hotmail.com> wrote in message
news:1baf501c42130$42cc0430$a501280a@.phx
.gbl...
> Hi all,
> I have a Win2000 server with Exchange2003 and SQL
> server2000 SP1.
> The system seems to work OK, but after about 1 hour after
> startup, the SQL server starts to generate networktraffic
> that completely floods the network. It is now impossible
> to log into the server, get on the network or access the
> internet from any workstation that is connected to the
> network. In about one hour more than 50.000.000 network
> packets are sent into space. When I disconnect the
> internet connection, it just continues to do so. When I
> stop the SQL service in the service manager, traffic stops
> and everything works again.
> Any thoughts'
> Piet Koenekoop|||Thanks a lot for the two suggestions. The Slammer virus was not detected by
the AV software, but the installation of SP3 has solved my problem.
Piet Koenekoop

excessive network traffic

Hi all,
I have a Win2000 server with Exchange2003 and SQL
server2000 SP1.
The system seems to work OK, but after about 1 hour after
startup, the SQL server starts to generate networktraffic
that completely floods the network. It is now impossible
to log into the server, get on the network or access the
internet from any workstation that is connected to the
network. In about one hour more than 50.000.000 network
packets are sent into space. When I disconnect the
internet connection, it just continues to do so. When I
stop the SQL service in the service manager, traffic stops
and everything works again.
Any thoughts'
Piet Koenekoop"Piet Koenekoop" <pietkoenekoop@.hotmail.com> wrote in message
news:1baf501c42130$42cc0430$a501280a@.phx.gbl...
> Hi all,
> I have a Win2000 server with Exchange2003 and SQL
> server2000 SP1.
> The system seems to work OK, but after about 1 hour after
> startup, the SQL server starts to generate networktraffic
> that completely floods the network. It is now impossible
> to log into the server, get on the network or access the
> internet from any workstation that is connected to the
> network. In about one hour more than 50.000.000 network
> packets are sent into space. When I disconnect the
> internet connection, it just continues to do so. When I
> stop the SQL service in the service manager, traffic stops
> and everything works again.
> Any thoughts'
I'm no expert, but the symtoms looks like Slammer virus.
--
Steven Ung
"The source of all greatness lies within you" - Anonymous|||Yep, looks like the slammer virus to me as well...
Update your SQL Server to SP3a, and reboot... and life gets good again...
"Piet Koenekoop" <pietkoenekoop@.hotmail.com> wrote in message
news:1baf501c42130$42cc0430$a501280a@.phx.gbl...
> Hi all,
> I have a Win2000 server with Exchange2003 and SQL
> server2000 SP1.
> The system seems to work OK, but after about 1 hour after
> startup, the SQL server starts to generate networktraffic
> that completely floods the network. It is now impossible
> to log into the server, get on the network or access the
> internet from any workstation that is connected to the
> network. In about one hour more than 50.000.000 network
> packets are sent into space. When I disconnect the
> internet connection, it just continues to do so. When I
> stop the SQL service in the service manager, traffic stops
> and everything works again.
> Any thoughts'
> Piet Koenekoop|||Thanks a lot for the two suggestions. The Slammer virus was not detected by the AV software, but the installation of SP3 has solved my problem
Piet Koenekoop