I got a very critical SQL database which is the main database for our Public Safety 911 software it is approximately 160 GIG DB. I am trying to create a transactional replication of this data over to another SQL Server. I am only trying to replication about 20 of the 800 + tables in the database. Every time I create the publisher and subscriber and do the initialization, the 911 software slows down or crashes and I have to stop the initialization. I am fairly new to replication but I don't understand why it would slow the vendor software down. Am I overlooking something or is this the only way to get the data over to the subscriber? Any help would greatly be appreciated.
Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.
If you have heard of RFC822 date formats, they can be quite a challenge in SQL Server. RFC822 is an Internet standard format for email message headers, including all dates within those headers. The RFC822 protocols are available in detail at:
Ever needed a SQL 2008 Database replicated/mirrored/log shipped on another server but you can't take the downtime inflicted by initial snapshot or disconnect while T-logs are restored or mirror applied?
You can use SQL Server Initialize from Backup…
This video shows, step by step, how to configure Oracle Heterogeneous Services via the Generic Gateway Agent in order to make a connection from an Oracle session and access a remote SQL Server database table.