Sunday, March 11, 2012
Bi-Directional Transactional replication?
The documentation on BoL is very limited and there are not too many info
available outside too. We are planning to have active-active SQLServers, that
needs dynamic transactional replication.
I would really appreciate practical advise on BiDirectional Transactional
Replication?
Attention : Paul Ibison and JD . This is the same thread that I created
last month. I couldn't find a way to bump it up so that it becomes active
again. I did also change the subject a little bit, so that it is clear.
I have, it is pretty solid, but is not resilient to schema changes. Also
conflicts can be a pain, so the more you partition your data the easier life
will be for you.
"HowdyDowdy" <HowdyDowdy@.discussions.microsoft.com> wrote in message
news:55B8E404-3560-4016-98E1-68EA35A35F79@.microsoft.com...
> Has anyone successfully implemented Bi-Directional Transactional
> replication?
> The documentation on BoL is very limited and there are not too many info
> available outside too. We are planning to have active-active SQLServers,
> that
> needs dynamic transactional replication.
> I would really appreciate practical advise on BiDirectional Transactional
> Replication?
> Attention : Paul Ibison and JD . This is the same thread that I created
> last month. I couldn't find a way to bump it up so that it becomes active
> again. I did also change the subject a little bit, so that it is clear.
|||HC,
Do you have the Bi-Di trans repl described in detail in your book? Are there
samples in there?
Please let me know.
Thanks,
"Hilary Cotter" wrote:
> I have, it is pretty solid, but is not resilient to schema changes. Also
> conflicts can be a pain, so the more you partition your data the easier life
> will be for you.
>
> "HowdyDowdy" <HowdyDowdy@.discussions.microsoft.com> wrote in message
> news:55B8E404-3560-4016-98E1-68EA35A35F79@.microsoft.com...
>
>
|||Yes, there are. There are some in the update BOL which are pretty good as
well.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"HowdyDowdy" <HowdyDowdy@.discussions.microsoft.com> wrote in message
news:13B145A7-84DF-465F-B486-E780F4C9E9BB@.microsoft.com...
> HC,
> Do you have the Bi-Di trans repl described in detail in your book? Are
there[vbcol=seagreen]
> samples in there?
> Please let me know.
> Thanks,
> "Hilary Cotter" wrote:
life[vbcol=seagreen]
info[vbcol=seagreen]
SQLServers,[vbcol=seagreen]
Transactional[vbcol=seagreen]
created[vbcol=seagreen]
active[vbcol=seagreen]
clear.[vbcol=seagreen]
|||Thanks, Hillary.
I did see the udpated BOL and also an article from www.SqlMag.Com that
talked about BDT replication.
"Hilary Cotter" wrote:
> Yes, there are. There are some in the update BOL which are pretty good as
> well.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> "HowdyDowdy" <HowdyDowdy@.discussions.microsoft.com> wrote in message
> news:13B145A7-84DF-465F-B486-E780F4C9E9BB@.microsoft.com...
> there
> life
> info
> SQLServers,
> Transactional
> created
> active
> clear.
>
>
BiDirectional Replication
The documentation on BoL is very limited and there are not too many info
available outside too. We are planning to have active-active SQLServers, that
needs dynamic transactional replication.
I would really appreciate practical advise on BiDirectional Transactional
Repl.
This should help:
http://support.microsoft.com/default...b;en-us;820675
http://msdn.microsoft.com/library/de...lsamp_3ve6.asp
Rgds,
Paul Ibison
|||Paul,
I did already find this info from BoL.
I am looking for someone who has done this already. I spoke to a few DBAs
who haven't heard of this, but they have implemented Transaction Repl before.
"Paul Ibison" wrote:
> This should help:
> http://support.microsoft.com/default...b;en-us;820675
> http://msdn.microsoft.com/library/de...lsamp_3ve6.asp
> Rgds,
> Paul Ibison
>
>
|||This info is not in BOL - there are many setup scripts in the links I
posted. I have implemented it but didn't like the fact that I had to write
my own conflict resolvers and opted for merge instead, despite its overall
slower transfer rate (unless you are updating the same row many times I
would expect this to be generally the case). Also, schema changes will be
more restrictive. Hilary had implemented it in his work, so he can probably
add more if you want to go down this path.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Thanks, Paul. I do appreciate your time.
Hillary, Can you please shed some light on this?
PS : Paul : The updated BoL is available as a download contains the link
that you specified in your first response. I thought of providing this info,
so that people are aware of the availability of the updated BoL.
"Paul Ibison" wrote:
> This info is not in BOL - there are many setup scripts in the links I
> posted. I have implemented it but didn't like the fact that I had to write
> my own conflict resolvers and opted for merge instead, despite its overall
> slower transfer rate (unless you are updating the same row many times I
> would expect this to be generally the case). Also, schema changes will be
> more restrictive. Hilary had implemented it in his work, so he can probably
> add more if you want to go down this path.
> Rgds,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
|||Well spotted - I'm using the old one at home. Thanks for the correction
Rgds,
Paul Ibison
"HowdyDowdy" <HowdyDowdy@.discussions.microsoft.com> wrote in message
news:A961EFBF-5E13-4178-902B-4C50F8972038@.microsoft.com...
> Thanks, Paul. I do appreciate your time.
> Hillary, Can you please shed some light on this?
> PS : Paul : The updated BoL is available as a download contains the link
> that you specified in your first response. I thought of providing this
info,[vbcol=seagreen]
> so that people are aware of the availability of the updated BoL.
>
> "Paul Ibison" wrote:
write[vbcol=seagreen]
overall[vbcol=seagreen]
be[vbcol=seagreen]
probably[vbcol=seagreen]
Thursday, March 8, 2012
BI Dev Studio won't install with June CTP reinstallation
I am attempting to install the BI Development Studio, from the SQL Server 2005 June CTP, on an XP machine. It installed successfully the first time I installed it, along with all other Workstation Components and BOL.
Subsequently I have uninstalled and reinstalled the Workstation Components, but the installation process does not fully install BI Development Studio. It creates the C:\Program Files\Microsoft Visual Studio 8\Common7\IDE directory (where devenv.exe should be located), but this directory is empty other than the PrivateAssemblies and profiles subdirectories. After an installation , the Start Programs menu contains an option for “SQL Server Business Intelligence Development Studio” under "MS SQL Server 2005 CTP", but this shortcut points to the non-existent C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\devenv.exe
There are no installation errors, and everything else seems to install OK, but BI Dev Studio is simply not there..
I have used both Add/Remove Programs, and the Build Uninstall Wizard, to remove the installation before trying the reinstalls.
This machine also has Visual Studio 2003 and a SQL Server 2000 instance, but they were already in place prior to my first successful installation.
Thanks in advance!
This is not a very satisfying answer, but here's how we fixed it.After running the Build Uninstall Wizard once again, we manually removed all folders and all files throughout the hard drive related to SQL Server 2005 (i.e. 9) and Visual Studio 2005 (i.e. 8). Also all registry entries. After manually removing all of this, the installation worked successfully.
Bottom line: the Build Uninstall Wizard fails to remove quite a few files and registry settings on your machine, some of which prevented the successful reinstall of the BI Dev Studio.
Friday, February 10, 2012
Best way to confirm password change for a Credential?
Looking for opinions here on what is the best way to programmatically test that a password change to a credential has occurred successfully.
The password change was made using Alter Credential, and I can see in sys.credentials that the credential was updated by the tool that handles these updates. I would just like to be able to confirm that all of the credential updates were successful (in other words, they authenticate correctly) before anything starts to fail.
Assume that the number of SQL Servers is too great to manually check them even if the whole team worked on it together.
Thanks in advance!!
I think there is no such DMV or DMF available in this case and for multiple servers you might need to wrap in to a stored procedure to execute on relevant servers using SQLCMD scripts & variables.