Does the administrator windows login name and password of all servers
participate in replication must be the same?, or may I use the SQL
authentication?IIRC, Replication using windows authentication requires a trusted connection
using the same account on both end. BOL also has this:
Connections to a server (Publisher, Distributor, or Subscribers) can use
Windows Authentication or SQL Server security. Windows Authentication is
generally preferred for greater security and ease of use; however,
connections to Windows 98 servers must use SQL Server security because
Windows Authentication is a feature only on Windows NT 4.0 and Windows 2000.
It is recommended that the Subscriber connection have dbo permissions in the
subscription database to make sure the proper permissions are granted, and
for overall simplification; however, dbo permissions are not
If you are connecting to an untrusted domain you may wish to use SQL
authentication although this will weaken security.
Neil MacMurchy
"Tal" <talg@.nice.com> wrote in message
news:OjhYTt2$DHA.2348@.TK2MSFTNGP09.phx.gbl...
> Does the administrator windows login name and password of all servers
> participate in replication must be the same?, or may I use the SQL
> authentication?
>
Showing posts with label administrator. Show all posts
Showing posts with label administrator. Show all posts
Wednesday, March 21, 2012
Replication and Windows login
Does the administrator windows login name and password of all servers
participate in replication must be the same?, or may I use the SQL
authentication?IIRC, Replication using windows authentication requires a trusted connection
using the same account on both end. BOL also has this:
Connections to a server (Publisher, Distributor, or Subscribers) can use
Windows Authentication or SQL Server security. Windows Authentication is
generally preferred for greater security and ease of use; however,
connections to Windows 98 servers must use SQL Server security because
Windows Authentication is a feature only on Windows NT 4.0 and Windows 2000.
It is recommended that the Subscriber connection have dbo permissions in the
subscription database to make sure the proper permissions are granted, and
for overall simplification; however, dbo permissions are not
If you are connecting to an untrusted domain you may wish to use SQL
authentication although this will weaken security.
Neil MacMurchy
"Tal" <talg@.nice.com> wrote in message
news:OjhYTt2$DHA.2348@.TK2MSFTNGP09.phx.gbl...
> Does the administrator windows login name and password of all servers
> participate in replication must be the same?, or may I use the SQL
> authentication?
>sql
participate in replication must be the same?, or may I use the SQL
authentication?IIRC, Replication using windows authentication requires a trusted connection
using the same account on both end. BOL also has this:
Connections to a server (Publisher, Distributor, or Subscribers) can use
Windows Authentication or SQL Server security. Windows Authentication is
generally preferred for greater security and ease of use; however,
connections to Windows 98 servers must use SQL Server security because
Windows Authentication is a feature only on Windows NT 4.0 and Windows 2000.
It is recommended that the Subscriber connection have dbo permissions in the
subscription database to make sure the proper permissions are granted, and
for overall simplification; however, dbo permissions are not
If you are connecting to an untrusted domain you may wish to use SQL
authentication although this will weaken security.
Neil MacMurchy
"Tal" <talg@.nice.com> wrote in message
news:OjhYTt2$DHA.2348@.TK2MSFTNGP09.phx.gbl...
> Does the administrator windows login name and password of all servers
> participate in replication must be the same?, or may I use the SQL
> authentication?
>sql
Saturday, February 25, 2012
replication
wot should be the ans of the below scenario..
You are the administrator of a SQL Server 2000 computer. You want to set up snapshot replication on the server. The server will serve as Publisher and Distributor for a minimum of 40/50 Subscribers. Currently, you want to publish 3GB/4GB of data, but the data is expected to grow over time. Subscribers will receive a new snapshot each month. You want to minimize the workload on the Publisher/Distributor. Which two actions should you take to configure snapshot replication? (Each correct answer presents part of the solution. Choose two)
a. Store the snapshot in the default folder on the Publisher/Distributor.
b. Store the snapshot in an alternative folder on the Publisher/Distributor.
c. Store the snapshot in a shared folder on a file server.
d. Create pull subscriptions.
e. Create push subscriptions.I would store the snapshot on a file server
and create pull subscriptions
--
Dandy Weyn, Belgium
MCSE, MCSA, MCDBA, MCT
http://www.dandyman.net
Check my SQL Server resource pages (currently under construction)
http://www.dandyman.net/sql
"rahul" <anonymous@.discussions.microsoft.com> wrote in message
news:A26AAAD3-6275-4C3D-90D9-F97CEB0FE429@.microsoft.com...
> wot should be the ans of the below scenario...
> You are the administrator of a SQL Server 2000 computer. You want to set
up snapshot replication on the server. The server will serve as Publisher
and Distributor for a minimum of 40/50 Subscribers. Currently, you want to
publish 3GB/4GB of data, but the data is expected to grow over time.
Subscribers will receive a new snapshot each month. You want to minimize the
workload on the Publisher/Distributor. Which two actions should you take to
configure snapshot replication? (Each correct answer presents part of the
solution. Choose two)
>
> a. Store the snapshot in the default folder on the Publisher/Distributor.
> b. Store the snapshot in an alternative folder on the
Publisher/Distributor.
> c. Store the snapshot in a shared folder on a file server.
> d. Create pull subscriptions.
> e. Create push subscriptions.
>|||Although I am not a replication expert, I would choose c and d.
Pull subscriptions ( by default) cause the distribution process to run at
the subscriber ( and not the publisher) which offloads work from the
publisher... ( As a side note, SQL 2000 allows a push subscription to have
the subscriber do his own work as well, it is called remote activation..)
Storing the snapshot files somewhere OTHER than the publisher/distributor
simply means that the publisher does NOT have to do IO during the initial
sync with the subscriber..
Hope this help.s
"rahul" <anonymous@.discussions.microsoft.com> wrote in message
news:A26AAAD3-6275-4C3D-90D9-F97CEB0FE429@.microsoft.com...
> wot should be the ans of the below scenario...
> You are the administrator of a SQL Server 2000 computer. You want to set
up snapshot replication on the server. The server will serve as Publisher
and Distributor for a minimum of 40/50 Subscribers. Currently, you want to
publish 3GB/4GB of data, but the data is expected to grow over time.
Subscribers will receive a new snapshot each month. You want to minimize the
workload on the Publisher/Distributor. Which two actions should you take to
configure snapshot replication? (Each correct answer presents part of the
solution. Choose two)
>
> a. Store the snapshot in the default folder on the Publisher/Distributor.
> b. Store the snapshot in an alternative folder on the
Publisher/Distributor.
> c. Store the snapshot in a shared folder on a file server.
> d. Create pull subscriptions.
> e. Create push subscriptions.
>
You are the administrator of a SQL Server 2000 computer. You want to set up snapshot replication on the server. The server will serve as Publisher and Distributor for a minimum of 40/50 Subscribers. Currently, you want to publish 3GB/4GB of data, but the data is expected to grow over time. Subscribers will receive a new snapshot each month. You want to minimize the workload on the Publisher/Distributor. Which two actions should you take to configure snapshot replication? (Each correct answer presents part of the solution. Choose two)
a. Store the snapshot in the default folder on the Publisher/Distributor.
b. Store the snapshot in an alternative folder on the Publisher/Distributor.
c. Store the snapshot in a shared folder on a file server.
d. Create pull subscriptions.
e. Create push subscriptions.I would store the snapshot on a file server
and create pull subscriptions
--
Dandy Weyn, Belgium
MCSE, MCSA, MCDBA, MCT
http://www.dandyman.net
Check my SQL Server resource pages (currently under construction)
http://www.dandyman.net/sql
"rahul" <anonymous@.discussions.microsoft.com> wrote in message
news:A26AAAD3-6275-4C3D-90D9-F97CEB0FE429@.microsoft.com...
> wot should be the ans of the below scenario...
> You are the administrator of a SQL Server 2000 computer. You want to set
up snapshot replication on the server. The server will serve as Publisher
and Distributor for a minimum of 40/50 Subscribers. Currently, you want to
publish 3GB/4GB of data, but the data is expected to grow over time.
Subscribers will receive a new snapshot each month. You want to minimize the
workload on the Publisher/Distributor. Which two actions should you take to
configure snapshot replication? (Each correct answer presents part of the
solution. Choose two)
>
> a. Store the snapshot in the default folder on the Publisher/Distributor.
> b. Store the snapshot in an alternative folder on the
Publisher/Distributor.
> c. Store the snapshot in a shared folder on a file server.
> d. Create pull subscriptions.
> e. Create push subscriptions.
>|||Although I am not a replication expert, I would choose c and d.
Pull subscriptions ( by default) cause the distribution process to run at
the subscriber ( and not the publisher) which offloads work from the
publisher... ( As a side note, SQL 2000 allows a push subscription to have
the subscriber do his own work as well, it is called remote activation..)
Storing the snapshot files somewhere OTHER than the publisher/distributor
simply means that the publisher does NOT have to do IO during the initial
sync with the subscriber..
Hope this help.s
"rahul" <anonymous@.discussions.microsoft.com> wrote in message
news:A26AAAD3-6275-4C3D-90D9-F97CEB0FE429@.microsoft.com...
> wot should be the ans of the below scenario...
> You are the administrator of a SQL Server 2000 computer. You want to set
up snapshot replication on the server. The server will serve as Publisher
and Distributor for a minimum of 40/50 Subscribers. Currently, you want to
publish 3GB/4GB of data, but the data is expected to grow over time.
Subscribers will receive a new snapshot each month. You want to minimize the
workload on the Publisher/Distributor. Which two actions should you take to
configure snapshot replication? (Each correct answer presents part of the
solution. Choose two)
>
> a. Store the snapshot in the default folder on the Publisher/Distributor.
> b. Store the snapshot in an alternative folder on the
Publisher/Distributor.
> c. Store the snapshot in a shared folder on a file server.
> d. Create pull subscriptions.
> e. Create push subscriptions.
>
replication
wot should be the ans of the below scenario...
You are the administrator of a SQL Server 2000 computer. You want to set up
snapshot replication on the server. The server will serve as Publisher and D
istributor for a minimum of 40/50 Subscribers. Currently, you want to publis
h 3GB/4GB of data, but the
data is expected to grow over time. Subscribers will receive a new snapshot
each month. You want to minimize the workload on the Publisher/Distributor.
Which two actions should you take to configure snapshot replication? (Each c
orrect answer presents part
of the solution. Choose two)
a. Store the snapshot in the default folder on the Publisher/Distributor.
b. Store the snapshot in an alternative folder on the Publisher/Distributor.
c. Store the snapshot in a shared folder on a file server.
d. Create pull subscriptions.
e. Create push subscriptions.I would store the snapshot on a file server
and create pull subscriptions
Dandy Weyn, Belgium
MCSE, MCSA, MCDBA, MCT
http://www.dandyman.net
Check my SQL Server resource pages (currently under construction)
http://www.dandyman.net/sql
"rahul" <anonymous@.discussions.microsoft.com> wrote in message
news:A26AAAD3-6275-4C3D-90D9-F97CEB0FE429@.microsoft.com...
up snapshot replication on the server. The server will serve as Publisher
and Distributor for a minimum of 40/50 Subscribers. Currently, you want to
publish 3GB/4GB of data, but the data is expected to grow over time.
Subscribers will receive a new snapshot each month. You want to minimize the
workload on the Publisher/Distributor. Which two actions should you take to
configure snapshot replication? (Each correct answer presents part of the
solution. Choose two)
Publisher/Distributor.
Pull subscriptions ( by default) cause the distribution process to run at
the subscriber ( and not the publisher) which offloads work from the
publisher... ( As a side note, SQL 2000 allows a push subscription to have
the subscriber do his own work as well, it is called remote activation..)
Storing the snapshot files somewhere OTHER than the publisher/distributor
simply means that the publisher does NOT have to do IO during the initial
sync with the subscriber..
Hope this help.s
"rahul" <anonymous@.discussions.microsoft.com> wrote in message
news:A26AAAD3-6275-4C3D-90D9-F97CEB0FE429@.microsoft.com...
up snapshot replication on the server. The server will serve as Publisher
and Distributor for a minimum of 40/50 Subscribers. Currently, you want to
publish 3GB/4GB of data, but the data is expected to grow over time.
Subscribers will receive a new snapshot each month. You want to minimize the
workload on the Publisher/Distributor. Which two actions should you take to
configure snapshot replication? (Each correct answer presents part of the
solution. Choose two)
Publisher/Distributor.
You are the administrator of a SQL Server 2000 computer. You want to set up
snapshot replication on the server. The server will serve as Publisher and D
istributor for a minimum of 40/50 Subscribers. Currently, you want to publis
h 3GB/4GB of data, but the
data is expected to grow over time. Subscribers will receive a new snapshot
each month. You want to minimize the workload on the Publisher/Distributor.
Which two actions should you take to configure snapshot replication? (Each c
orrect answer presents part
of the solution. Choose two)
a. Store the snapshot in the default folder on the Publisher/Distributor.
b. Store the snapshot in an alternative folder on the Publisher/Distributor.
c. Store the snapshot in a shared folder on a file server.
d. Create pull subscriptions.
e. Create push subscriptions.I would store the snapshot on a file server
and create pull subscriptions
Dandy Weyn, Belgium
MCSE, MCSA, MCDBA, MCT
http://www.dandyman.net
Check my SQL Server resource pages (currently under construction)
http://www.dandyman.net/sql
"rahul" <anonymous@.discussions.microsoft.com> wrote in message
news:A26AAAD3-6275-4C3D-90D9-F97CEB0FE429@.microsoft.com...
quote:
> wot should be the ans of the below scenario...
> You are the administrator of a SQL Server 2000 computer. You want to set
up snapshot replication on the server. The server will serve as Publisher
and Distributor for a minimum of 40/50 Subscribers. Currently, you want to
publish 3GB/4GB of data, but the data is expected to grow over time.
Subscribers will receive a new snapshot each month. You want to minimize the
workload on the Publisher/Distributor. Which two actions should you take to
configure snapshot replication? (Each correct answer presents part of the
solution. Choose two)
quote:
>
> a. Store the snapshot in the default folder on the Publisher/Distributor.
> b. Store the snapshot in an alternative folder on the
Publisher/Distributor.
quote:|||Although I am not a replication expert, I would choose c and d.
> c. Store the snapshot in a shared folder on a file server.
> d. Create pull subscriptions.
> e. Create push subscriptions.
>
Pull subscriptions ( by default) cause the distribution process to run at
the subscriber ( and not the publisher) which offloads work from the
publisher... ( As a side note, SQL 2000 allows a push subscription to have
the subscriber do his own work as well, it is called remote activation..)
Storing the snapshot files somewhere OTHER than the publisher/distributor
simply means that the publisher does NOT have to do IO during the initial
sync with the subscriber..
Hope this help.s
"rahul" <anonymous@.discussions.microsoft.com> wrote in message
news:A26AAAD3-6275-4C3D-90D9-F97CEB0FE429@.microsoft.com...
quote:
> wot should be the ans of the below scenario...
> You are the administrator of a SQL Server 2000 computer. You want to set
up snapshot replication on the server. The server will serve as Publisher
and Distributor for a minimum of 40/50 Subscribers. Currently, you want to
publish 3GB/4GB of data, but the data is expected to grow over time.
Subscribers will receive a new snapshot each month. You want to minimize the
workload on the Publisher/Distributor. Which two actions should you take to
configure snapshot replication? (Each correct answer presents part of the
solution. Choose two)
quote:
>
> a. Store the snapshot in the default folder on the Publisher/Distributor.
> b. Store the snapshot in an alternative folder on the
Publisher/Distributor.
quote:
> c. Store the snapshot in a shared folder on a file server.
> d. Create pull subscriptions.
> e. Create push subscriptions.
>
Subscribe to:
Posts (Atom)