Hot answers tagged

3

This is bigger than a comment but something to test first and then implement : You are logshipping 800+ databases. Thats a large amount of databases that you logship every 15 mins. You should offload some databases to another server. IMHO 800 databases on a single server is a lot! We had similar problem with logshipping when we logshipped 200+ databases ...


3

Here is a starting point. The first query will give you a list of roles with either INSERT or UPDATE permission. From there you will need to look at the permissions being at the DATABASE, SCHEMA, or OBJECT level and decide if they cover the objects you are interested in. Check the state_desc column to make sure it is GRANT (it probably will be) as DENYs ...


2

It's really not THAT different to Service Pack patching whereby you'll need to do passive nodes first, then give cluster resource group ownership to one of the upgraded nodes, in order to finally upgrade the active node. Map out your upgrade sequence first and test it if you have the luxury of a dev environment. In place upgrades are supported and the ...


1

I loaded all the databases being shipped into this query: DECLARE @path NVARCHAR(260); SELECT @path = REVERSE(SUBSTRING(REVERSE([path]), CHARINDEX(CHAR(92), REVERSE([path])), 260)) + N'log.trc' FROM sys.traces WHERE is_default = 1; SELECT *, rn = ROW_NUMBER() OVER (PARTITION BY DatabaseName ORDER BY StartTime) INTO #blat FROM ...



Only top voted, non community-wiki answers of a minimum length are eligible