I have a requirement to use Sql replication from a sql server 2005 instance to a Sql 2000 instance over a vpn. The vpn is permanent between the 2 sites and there are only a few tables that need replicated. Can anyone give me any advantages/disadvantages of replication over vpn or any issues with replication between SQL 2005 and Sql 2000.
Thanks
Well,
I think as long as the amount of data is not that much and speed is not a k.o. criteria,
this will work from the networking point of view. I have several applications communicating
via VPN which basically works smoothly, but of course latency is notably higher compared to
nonVPN communication.
HTH
Related
I have a MS SQL server that I've start working with and I think I have an idea on the organization of MS SQL Server but I'm not absolutely sure of that idea's correctness. In relation to this idea, I have a question about a memory setting that might be an issue if my assumptions are correct.
My assumptions:
I know you can have multiple SQL servers on a Host server and that they are connected to by SSMS as separate connections.
You can have multiple Databases under the given server.
The host server has 24GB of RAM. From what I can tell, there is only one MS SQL server running. Under this SQL Server there are several databases.
While digging around in the settings I found a setting that set the "Maximum server memory (in MB)" to 8192MB.
Based on my assumptions that the databases are not separate "servers", would
it be correct to say that all of those databases are sharing the 8192MB of RAM?
Based on my assumptions that the databases are not separate "servers", would it be correct to say that all of those databases are sharing the 8192MB of RAM?
That's Right..
You are assigning memory to an instance of sqlserver(multiple instances can coexist in same box) and databases share memory available to them
I have a local SQL Server database with many tables. I need to transfer data to a remote SQL Server database using vb.net, and task should be run every 2 hr from application. How is it possible to do this? Please suggest the best way for this.
I think the better way is replication. i don't know the possibilities in SQL Server but it works great in mysql. if you enables the replication in two database(Master- Slave) what ever be the changes you have made in the master will simultaneously in the slave. there is possibilities for Bi-Directional Replication in MySQL.
SQL Server provides various types of replication to extend the possibilities. this article helps you to establish replication in Sql Server
We are finding Azure SQL Database very slow. Its probably about 10x slower than the same spend on a SQL on an Azure VM.
However a VM based solution requires maintenance and backups and im concerned I'll loose the VM and data if something horrible goes wrong.
Thus the SQL Azure solution seems safer to me. So I have two specific questions.
Are you seeing this speed difference and if so is there a solution
Is there any nice solution for ensure the SQL on VM is backed up automatically and offsite.
Azure SQL database is slightly slower than SQL Server on Azure Virtual Machine. However, we didn't find it as slow as 10X. May be you should try Premium tier, which delivers more powerful and predictable performance, in case your database is in some other tier.
Regarding SQL Server on Azure Virtual Machine, there is support available for automated backup and patching. Please visit the below link for more details.
http://azure.microsoft.com/blog/2015/01/29/automated-everything-with-sql-server-on-iaas-vms/
While performance analysis, it is worth checking for ASYNC_NETWORK_IO wait type. Make Sure your client application is deployed close to your database in Azure.
I was looking for some advise on a current task and sifting though on the net I am not finding anything direct. I have full SQL Server 2008 in my central location and then 5 remote sites that use SQL Server 2008 Express for the database services. I am looking for a way to synch or replicate the databases in the 2008 Express instances back to my central 2008 developer edition instance.
What is blocking me is the editions and what is possible, I have been told log shipping and mirroring will not work with Express editions of SQL Server.
One thought was SSIS maybe from the central location pulling from the express instance, but again I don't know if this is possible.
Any ideas however big or small would be really appreciated!
Thanks!
Neither log shipping nor mirroring are replication solutions. They are high availability/disaster recovery solutions which allow you to have the same database in two (or more with log-sipping) locations. Only the source location can update the database.
What you want is replication, see Replicating Data to SQL Server Express. Merge Replication will allow you to update data at the periphery (on the SQL Express instances).
Note that all scenarios require static and available SQL Express instances. Replication will not work with if the SQL express instances are mobile (show up on the network with different names/IPs, think a laptop being moved around) or occasionally available (again, think a laptop that appears on and off the network as the user opens it in the corp WiFi or at home). For mobile/occasionally connected scenarios the right approach is Sync Framework.
One thought was SSIS maybe from the central location pulling from the express instance, but again I don't know if this is possible.
No, is not possible in practice, because of the impossibility of detecting changes ('what records need to be pulled?') and the lack of support for update conflict resolution.
Another approach, which I did see it deployed with success, is to use Service Broker since is freely available in Express. But it only solves the problem of transport (delivery the changes), and does not address detecting changes (usually solved via either app specific logic or via triggers) and applying the changes (this is not hard to solve though). Update conflicts are hard to handle.
I am sending data across a link with very little bandwidth and I will probably be sending large data files.
I have Merge Replication and Snapshot replication configured at present.
Is it possible to enable compression in SQL Server 2005 replication and if so, how?
Thanks.
Google turned up this article on the Microsoft SQL Server Development Customer Advisory Team [sic!] Blog:
SQL Server 2005 Transactional Replication: Benefit of using SubscriptionStreams for low bandwidth, high latency environments
Not exactly what you were asking for, but maybe of value still.