This question came up today: how can I change the IP address between the principal and mirror in database mirroring?
Not a common operation but this procedure worked in an isolated lab environment where we had full control over the application and transaction activity. We wanted to introduce a WAN latency injector so needed to change the database mirroring IP addresses on the principal and mirror.
I’ll try and find the exact scripts we used and upload them here.
I haven’t had a chance to look through these yet so I can’t comment on the content but I thought I would post here to share these new resources.
HP Business Intelligence Sizer for Microsoft SQL Server 2005/2008
HP Whitepapers on SQL Server 2008 Data Warehousing / Business Intelligence
I often see questions about transactional replication performance problems, especially around latency/delays between the publisher and subscriber(s) so I’ve put a few pointers below on what to investigate. Latency between the publisher, distributor and subscriber(s) is, more often than not, the symptom of other causes for example, poor I/O capacity on subscribers, blocking/locking, hotspots on indexes, high number of virtual log files etc.
We recently had the opportunity to test a couple of the Fusion IO PCI-Express 640GB SSD cards http://www.fusionio.com/Products.aspx in a Dell R900 server, unfortunately time was against us and we were unable to do this. The Fusion IO SSD cards would dramatically increase the IOPS capacity and personally, I think they would be suited to storing tempdb. I’m a bit cautious about using SSD for data and transaction log so tempdb seems like the best solution.