Viewing 15 posts - 16 through 30 (of 107 total)
generally understood sequence is
client application makes new connection
SQL engine authenticates client [as LOGIN], and allocates a SPID
subsequent TSQL sent to SPID
SPID checks...
September 25, 2008 at 3:11 am
the distribution db is used by various agents
LogReader (writes)
Distrib Agent (read+write)
Distribution clean up: distribution (delete)
plus other players
Agent history clean up: distribution
Replication agents checkup
Expired subscription clean up
where these run every 10...
September 19, 2008 at 4:01 am
you can have several pubs to several subs (e.g. N:M) but no overlaps (multiple {P,S,T1})
you might want to split a big (eg 1500 table) pub into several so that multiple...
September 19, 2008 at 2:17 am
try these URLs for starters [no, I don't necessarily agree with posters]
http://www.microsoft.com/technet/prodtechnol/sql/2005/dbmirror.mspx
http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=227&SiteID=1
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=263505&SiteID=1
you should consider
volume of data sent (and speed of your WAN)
are...
September 17, 2008 at 4:26 pm
my steer is to use Log-Shipping which has these components
Source (Ohio)
normal tranlog job "LSBackup_db1" (say every 15 mins)
- write the *.TRN to a share (eg \\OHIOS1\SqlDumps)
Secondary (Florida)
copy job (say every...
September 17, 2008 at 10:17 am
as well-noted already, transactional repl will normally invoke sprocs that are scripted for you at the distributor and applied at the subscriber (as part of the initial snapshot delivery). But...
September 17, 2008 at 4:13 am
there are several technologies to choose from
replication (eg Snapshot, Transactional)
mirroring (supported SQL2005-SP1 or later)
log-shipping
and your choice should be driven by business SLA's and risk assessments
Snapshot replication would ship everything (e.g....
September 17, 2008 at 3:47 am
LogReader writes to distribution
distrib.exe (Distrib Agent) jobs read from distribution
various jobs tidy up (eg after all subs have received changes)
Agent history clean up: distribution
Distribution clean up: distribution
Expired subscription clean up
Replication...
September 16, 2008 at 8:32 am
Replication is but one tool in the armoury, and there is a danger of those with hammers thinking all problems are nails !
The business-led analysis should identify what data is...
September 16, 2008 at 7:30 am
the comments on his post suggests a repeat with SQL2008 (now RTM'ed) would be cool to see if anything has changed.
If either of you know the dude perhaps you could...
August 21, 2008 at 8:32 am
The use of UNIQUEIDENTIFIER datatype (GUID) occupies more storage than a simple INT. The consequence of such a decision is not only storage but the number of keys that can...
August 20, 2008 at 10:57 am
you mentioned loadbalancing, webservers and database servers but remember these are normally configured as
[font="Courier New"]
inter/intranet
external FW1
loadbalancing ...
August 20, 2008 at 10:33 am
simply that either we should either encourage usage of undocumented features [with due warnings] or not [like pregnancy, there's no middle ground]
but no matter, I wasn't popping at you ;)...
August 4, 2008 at 8:49 am
true, is undocumented in distributed BOL content ["offline"]
however the docviewer online search documents it 2001/5/31 by a certain Brian Knight
what a pity his simplistic article on db sizing [2001/7/25] failed...
August 4, 2008 at 7:09 am
recycling a 2001 article for SQL2000 is unlikely to be optimal for 2008 (SQL2005 going SQL2008)
- come on guys, come out of your cave there's been interim life these 7...
August 4, 2008 at 4:17 am
Viewing 15 posts - 16 through 30 (of 107 total)