November 12, 2009 at 11:44 am
Hi everyone,
I would like to set up 2 difference instance of sql servers on different servers sharing same datafiles in a IBM Storage device (SAN). This is basically for load balancing. I would like to use one server for
OLTP and another one for reporting. Please let me know any issues with this kind of configuration and kindly guide me how can i do this. Basiclly i want to know the sharing of datafiles for 2 different instances.
Thanks
November 12, 2009 at 11:55 am
I do not think that you can share the Data / Log Files between 2 different servers at the same time.
Instead have use Replication on the OLTP and see that the replicated DB is used for replication.
You have SAN based snapshots that can help you to have the Datafiles cloned and then try to use them on the other Server.
Log Shipping/ DB Mirroring is can also be used but not a straightforward on, you need to further make changes on the destination to use it for read only purpose.
Blog -- LearnSQLWithBru
Join on Facebook Page Facebook.comLearnSQLWithBru
Twitter -- BruMedishetty
November 13, 2009 at 5:16 pm
Bru is correct. You cannot share the data files for load balancing. There is a shared READ system using a SAN for Enterprise edition, but it will not work for write files, only read only.
Bru has some good suggestions for you, but replication may be the best for a reporting situation.
July 19, 2010 at 2:03 am
You have 3 options:
Replication
Logshipping
Database mirroring with database snapshot
Choose anyone for reporting.....ut yes again Trasactional Replication would be best option here
July 19, 2010 at 12:44 pm
There is a 3rd party appliance that helps to simulate load balancing. It in essence creates a replication type of setup and keeps multiple databases in sync on different servers. But the data and log files of each cannot be shared.
I can't remember the name of the vendor, but it is out there.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
July 19, 2010 at 1:09 pm
If you choose to use database mirroring with a database snapshot, then you need to ensure that none of your data files is over 64GB in size. There's a Windows sparse file issue that you can encounter. And my environment did, and it caused downtime as the transaction log filled up on the primary server since the mirroring records didn't get cleared from the tlog. We were using the database snapshot for internal folks to run some adhoc queries every now and then. We've avoided the sparse file issue by adding multiple data files (my 1TB database has 21 data files now), but we decided not to use a database snapshot on the mirror just in case.
I use transactional replication for all of our reporting needs.
Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
Ramblings of a DBA (My SQL Server Blog)[/url]
Subscribe to my blog
July 20, 2010 at 7:55 am
CirquedeSQLeil (7/19/2010)
There is a 3rd party appliance that helps to simulate load balancing. It in essence creates a replication type of setup and keeps multiple databases in sync on different servers. But the data and log files of each cannot be shared.I can't remember the name of the vendor, but it is out there.
Xkoto or Gridscale maybe?
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply