Viewing 15 posts - 31 through 45 (of 317 total)
That do in account must exist on the subscriber and have sufficient permissions in the database that you are replicating to
November 4, 2014 at 8:22 am
use patindex to find the location of your delimiters and use those loactions for start and end in substring.
November 3, 2014 at 12:31 pm
Perry Whittle (10/28/2014)
mbricker-600840 (10/28/2014)
In this case the entire netwrok may go down.Take the instances offline during this period then and keep the downtime short.
+1
November 3, 2014 at 12:26 pm
What user is it trying to connect as and does it exist on the subscriber?
Is this the snapshot agent or the distributor agent?
November 3, 2014 at 12:22 pm
So are you finding that the index is used or not?
If it is being used, then you may not want to drop it.
However, if it is not being used, then...
November 3, 2014 at 11:42 am
It is best practice that you use AD accounts specifically created as service accounts for the SQL server services.
Then grant these accounts the minimum rights on the box to run...
November 3, 2014 at 11:01 am
Furthermore, if you use SQL Server native backup compression, it may be substantially smaller
November 3, 2014 at 10:55 am
Since transaction_id is unique, it looks like the second index may be extraneous, unless it is used for covered queries.
Have you checked if it is being used? Google 'SQL Server...
November 3, 2014 at 10:52 am
What are the errors in the distributor Agent SQL Agent job?
November 3, 2014 at 10:47 am
What type of replication is this?
Transactional or merge?
November 3, 2014 at 10:45 am
Job history settings limit total rows in sysjobhistory and number of rows for any given job.
If you have an old backup of msdb, you could restore it with a different...
October 31, 2014 at 9:37 am
Gary Varga (10/31/2014)
October 31, 2014 at 7:58 am
Just run something like this:
USE [master]
GO
ALTER DATABASE [foo] SET RESTRICTED_USER WITH ROLLBACK IMMEDIATE
GO
RESTORE DATABASE [foo] .....
GO
USE [master]
GO
ALTER DATABASE [foo] SET MULTI_USER WITH ROLLBACK IMMEDIATE
GO
October 30, 2014 at 3:48 pm
Occasionally I expose the 1433 port on a SQL server instance to the outside world for testing purposes.
Every time within ~12 minutes I see failed sa login attempts and buffer...
October 30, 2014 at 3:32 pm
Viewing 15 posts - 31 through 45 (of 317 total)