Viewing 15 posts - 901 through 915 (of 1,157 total)
opc.three (7/13/2011)
MysteryJimbo (7/13/2011)
It is actually 32767 concurrent and running connections as its based on an smallint value but is...
July 13, 2011 at 3:25 pm
Oddly enough, this isnt true and is something Microsoft dont really reveal.
It is actually 32767 concurrent and running connections as its based on an smallint value but is generally not...
July 13, 2011 at 10:19 am
You also dont mention the type of replication, if you are inserting into the published table and if you require the data to propogate back to the publisher.
Transactional replication is...
July 12, 2011 at 9:40 am
This doesnt sound replication related.
So you have now published an article (table) and this is now on the subscriber (server B) and communicating as expected.
Assuming you need to use this...
July 12, 2011 at 9:36 am
No guarantees. SSMS will generally do things you dont expect and from experience it will almost always force a reinitialisation when making a publication change of any kind. ...
July 12, 2011 at 9:33 am
This will not work in all circumstances.
Microsoft provide the BACKUP and RESTORE facility as a minimum method of recovering a corrupt database. There is of course the other high...
July 12, 2011 at 9:29 am
modify the sp_msdel proc on the subscriber to just return
Simple alter statement which you can easily role back.
July 8, 2011 at 6:22 am
One option I would consider is "the big bang" migration by logshipping all databases prior to migration.
this will allow the set up of jobs and logins etc.
At migration time, bring...
July 7, 2011 at 3:54 am
The only problems I've had using SSIS in BID's have been XML releated.
These statements fixed the issue. You could try them, it wont hurt.
regsvr32 msxml3.dll
regsvr32 msxml6.dll
July 1, 2011 at 6:23 am
In principle this sounds like peer to peer transactional replication where all servers are publishers.
You could also do this in merge and have a central publisher.
June 30, 2011 at 3:38 am
Also, you shouldnt attempt to fail back until you applied the update to the second node as the binaries and databases will be of differing versions.
June 29, 2011 at 6:32 am
Have you considered switch to SQL2008 and using filestream? It is more efficient when dealing with large filesizes.
June 29, 2011 at 3:10 am
With a verticle partition it is likely there is one or more columns already not published. It may have been in the past so the tables match, but currently,...
June 29, 2011 at 2:11 am
Can you? I read its possible to add features to an existing cluster.
June 28, 2011 at 6:27 am
You appear to have stumbled on best practice.
1. Apply SP to passive node
2. Failover cluster
3. Apply SP to passive node
June 28, 2011 at 1:26 am
Viewing 15 posts - 901 through 915 (of 1,157 total)