Viewing 15 posts - 1 through 15 (of 25 total)
it works for the transactional replication. This solution has not been tested for the snapshot, merge, and P2P replications.
December 29, 2020 at 2:17 pm
I make sure that databases are available to the business 24/7. It is the main point. Other crucial point is automating administrative tasks like backups, replication, etc.
May 24, 2019 at 7:57 am
Edward,
you are lucky to have space on I drive. What would you do if there is no space for the second filegroup?
December 27, 2017 at 8:24 am
These routes look ok unless broker_instance guid do not match. Do they match?
Can you try to add binding on the source and rerun ssbdiagnostic:
CREATE REMOTE SERVICE BINDING SourceBinding
...
March 5, 2016 at 4:31 am
Jefferson Elias (2/22/2016)
As you suggest, there might be a problem in contacting the target service.
The configuration is as follows :
192.168.98.xx for the source and...
March 3, 2016 at 6:07 am
Jefferson Elias (2/17/2016)
sorry for the delay.. I had to do some other tasks before coming back to this...
As I followed the scripts attached to the article, there is a...
February 17, 2016 at 8:13 am
It looks like route is missing or invalid on the Source db.
Do you have firewall on 4022 port? Have you created SampleServiceTarget service already?
February 12, 2016 at 5:34 am
Jefferson Elias (2/10/2016)
I'm trying to run Service Broker on two separate servers. The...
February 11, 2016 at 10:49 am
Jefferson Elias (2/10/2016)
While running the code you provided, there is a little syntax error at
CREATE ENDPOINT ServiceBrokerEndpoint AUTHORIZATION $(LoginName)
STATE= STARTED AS TCP
( LISTENER_PORT=4022, ...
February 10, 2016 at 5:29 am
Data compression is Enterprise Edition feature. There is a nice article written by MS:
https://technet.microsoft.com/en-us/library/dd894051(v=sql.100).aspx
"The data compression feature in the Microsoft® SQL Server® 2008 database software can help reduce...
January 18, 2016 at 3:55 pm
Unfortunately this sp(sp_SQLskills_ConvertTraceToExtendedEvents) does not work on SQL Server 2008, because sys.trace_xe_event_map system table was introduced later in v11. 🙂
December 26, 2015 at 4:44 pm
rgarrett (9/15/2015)
October 24, 2015 at 1:19 pm
Why did you like it? Has it helped you to solve issues?
What was bad in it?
I like critics... don't be shy.:hehe:
September 12, 2015 at 8:12 am
I would consider BULK INSERT command to use in such trivial cases.
It could be automated to populate many tables in parallel instead of running sequentially SSIS packages.
Thanks! Nice article though!
September 11, 2015 at 1:53 am
Viewing 15 posts - 1 through 15 (of 25 total)