Newbie question on meaning of icon...

Hi! I have "inherited" a SQL server that I am quickly trying to get up to
speed on administering. There are several db's on the server. If I look at
the db's in enterprise manager one of them has what looks to be a "shared"
icon beside the db name. It looks just like the other db icons but has that
"share" hand underneath. What does this symbolize and how do I make
adjustments to this setting.
Sorry for being so obtuse! Thanks for the help!
-alex-
The 'sharing' hand means the database has been enabled for replication.
First, you read BOL (Books On-Line) and understand what replication is and
hw it works before you make any adjustments.
IMHO, your first concern should be backup and recovery. Next comes
space/performance management and monitoring. Last comes changes and
improvements.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"bairda" <bairda@.discussions.microsoft.com> wrote in message
news:F5139783-2191-442A-9584-04C743848493@.microsoft.com...
> Hi! I have "inherited" a SQL server that I am quickly trying to get up to
> speed on administering. There are several db's on the server. If I look
at
> the db's in enterprise manager one of them has what looks to be a "shared"
> icon beside the db name. It looks just like the other db icons but has
that
> "share" hand underneath. What does this symbolize and how do I make
> adjustments to this setting.
> Sorry for being so obtuse! Thanks for the help!
> -alex-

Newbie question on meaning of icon...

Hi! I have "inherited" a SQL server that I am quickly trying to get up to
speed on administering. There are several db's on the server. If I look at
the db's in enterprise manager one of them has what looks to be a "shared"
icon beside the db name. It looks just like the other db icons but has that
"share" hand underneath. What does this symbolize and how do I make
adjustments to this setting.
Sorry for being so obtuse! Thanks for the help!
-alex-The 'sharing' hand means the database has been enabled for replication.
First, you read BOL (Books On-Line) and understand what replication is and
hw it works before you make any adjustments.
IMHO, your first concern should be backup and recovery. Next comes
space/performance management and monitoring. Last comes changes and
improvements.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"bairda" <bairda@.discussions.microsoft.com> wrote in message
news:F5139783-2191-442A-9584-04C743848493@.microsoft.com...
> Hi! I have "inherited" a SQL server that I am quickly trying to get up to
> speed on administering. There are several db's on the server. If I look
at
> the db's in enterprise manager one of them has what looks to be a "shared"
> icon beside the db name. It looks just like the other db icons but has
that
> "share" hand underneath. What does this symbolize and how do I make
> adjustments to this setting.
> Sorry for being so obtuse! Thanks for the help!
> -alex-

Newbie question on meaning of icon...

Hi! I have "inherited" a SQL server that I am quickly trying to get up to
speed on administering. There are several db's on the server. If I look at
the db's in enterprise manager one of them has what looks to be a "shared"
icon beside the db name. It looks just like the other db icons but has that
"share" hand underneath. What does this symbolize and how do I make
adjustments to this setting.
Sorry for being so obtuse! Thanks for the help!
-alex-The 'sharing' hand means the database has been enabled for replication.
First, you read BOL (Books On-Line) and understand what replication is and
hw it works before you make any adjustments.
IMHO, your first concern should be backup and recovery. Next comes
space/performance management and monitoring. Last comes changes and
improvements.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"bairda" <bairda@.discussions.microsoft.com> wrote in message
news:F5139783-2191-442A-9584-04C743848493@.microsoft.com...
> Hi! I have "inherited" a SQL server that I am quickly trying to get up to
> speed on administering. There are several db's on the server. If I look
at
> the db's in enterprise manager one of them has what looks to be a "shared"
> icon beside the db name. It looks just like the other db icons but has
that
> "share" hand underneath. What does this symbolize and how do I make
> adjustments to this setting.
> Sorry for being so obtuse! Thanks for the help!
> -alex-

newbie question

Hello,
I'm new to SQL server and I've just inherited a SQL server with a single
user database. The company would like to replicate it to sql server used for
reporting services. I'm thinking that transaction replication is the way to
go as the database is over 40 Gb in size. The only requirements are that the
database be available for reporting.
I've been looking into the database schema and Ive found that there are
seven tables with identity columns and other tables that dont have a primary
key. Can I still use transaction replication? do I need to make any changes
to teh schema?
Thanks
p.s. can somebody point me to a doc that highlights how to implement
transaction replication and what the various components are?
Troy,
for a reporting setup, transactional replication is often used. Log shipping
is sometimes used, but the users have to be disconnected when the logs are
restored which means a big latency if this is done out of office hours. As
for transactional replication, books on line (BOL) is a good resource, as
well as Hilary's book and some web articles
(http://www.mssqlcity.com/Articles/Re...TR/SetupTR.htm).
The main components are the 2 agents: snapshot and distribution whiche are
essentially jobs that run the associated replication executable. The
snapshot agent will create several text files and place them in the
distribution working folder - a share that the subscriber can see. The
distribution agent reads the distribution database to see what commands are
waiting to be executed. It loads the text files and applies them to the
subscriber and then it'll read any subsequent commands involving changes to
the data, and apply these also. Plenty of details in BOL, but what I'd
recommend is to complinment the reading and set it up on one machine by
replicating a table from Northwind to Pubs and so begin to get used to the
whole setup.
Finally, don't worry about the identity columns - they're not relevant for
your purposes and the identity property will not be retained on the
subscriber.
Good luck
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

Newbie Question

I inherited a 2000 Advanced Server SQL 2000 Ent, Active-Passive setup. The
architect never got it working correctly, so he turned off the second node
and just left it running of the primary. We've been having reporting errors
in our application so I checked to see if everything was up-to-date and the
SQL Installation was still at the RTM level, no SPs at all (no wonder he had
problems). Because it's the end of the year and we needed to fix the problem
ASAP I evicted the second node and ran SP3a on the primary node to get our
reports on time.
Now what I'd like to do is set the thing up correctly, but am unsure of how
to approach bringing the evicted node back online as a failover node and get
it up to SP3a.
I'd be happy to hire an expert for a few hours if one of you MVPs lives in
Southern California, or wants to do a conference call and thinks that my
situation is too messed up to fix via newsgroup. If there is a good book I
can read on SQL clustering I'd like to hear about that as well.
Thanks.
Patrick Rouse
Microsoft MVP - Terminal Server
http://www.workthin.com
I think I may have found my answer here?
http://www.microsoft.com/windowsserv...5-d622b5b61369
&mid=8665605b-5a16-452f-8183-02b06b312b7f
"Patrick Rouse" wrote:

> I inherited a 2000 Advanced Server SQL 2000 Ent, Active-Passive setup. The
> architect never got it working correctly, so he turned off the second node
> and just left it running of the primary. We've been having reporting errors
> in our application so I checked to see if everything was up-to-date and the
> SQL Installation was still at the RTM level, no SPs at all (no wonder he had
> problems). Because it's the end of the year and we needed to fix the problem
> ASAP I evicted the second node and ran SP3a on the primary node to get our
> reports on time.
> Now what I'd like to do is set the thing up correctly, but am unsure of how
> to approach bringing the evicted node back online as a failover node and get
> it up to SP3a.
> I'd be happy to hire an expert for a few hours if one of you MVPs lives in
> Southern California, or wants to do a conference call and thinks that my
> situation is too messed up to fix via newsgroup. If there is a good book I
> can read on SQL clustering I'd like to hear about that as well.
> Thanks.
> --
> Patrick Rouse
> Microsoft MVP - Terminal Server
> http://www.workthin.com
|||Yep.. That is the correct procedure. See 'Maintaining a Failover Cluster'
in BOL for a detailed version. Pretend your second node has failed
completely.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Patrick Rouse" <PatrickRouse@.discussions.microsoft.com> wrote in message
news:12DFE27E-534D-4B31-94B3-03E15EFD3AA9@.microsoft.com...
> I think I may have found my answer here?
>
http://www.microsoft.com/windowsserv...5-d622b5b61369
&mid=8665605b-5a16-452f-8183-02b06b312b7f[vbcol=seagreen]
>
> "Patrick Rouse" wrote:
The[vbcol=seagreen]
node[vbcol=seagreen]
errors[vbcol=seagreen]
the[vbcol=seagreen]
had[vbcol=seagreen]
problem[vbcol=seagreen]
our[vbcol=seagreen]
how[vbcol=seagreen]
get[vbcol=seagreen]
in[vbcol=seagreen]
book I[vbcol=seagreen]