Viewing 15 posts - 136 through 150 (of 174 total)
Correct, they are cumulative, so, you only need to apply the latest. No, you do not need to stop the Sql Services when applying the SP.
July 15, 2016 at 6:25 am
Yes, you have the basic steps, I usually follow these steps:
1) Place the SP on both nodes
2) Upgrade the passive node first by running the SP executable on it -...
July 15, 2016 at 5:18 am
Here are a few other memory related dmv queries you can also run, see the comments for the preferred values:
SELECT total_physical_memory_kb, available_physical_memory_kb,
total_page_file_kb,...
July 12, 2016 at 12:20 pm
Sorry, I completely overlooked the beginning statement that the instance was already installed. You could give an alias a try. One thing to remember with a named instance...
July 6, 2016 at 8:06 am
Hi Brandie, to un-complicate things, why not just name the named instance "MyInstanceAG", then the named instance connection would be servername\MyInstanceAG. This way, you do not have to make...
July 6, 2016 at 7:27 am
Let's go the other direction, due to the size you stated, it could be a database with very little or no activity which could be causing the restore to "skip"...
July 5, 2016 at 12:19 pm
Is the log shipping process trying to work with a very large transaction log backup when this issue occurs?
July 5, 2016 at 8:48 am
Try these queries run together as one, filling in the name of your transaction log backup file name and your location in place of what is there (in both queries):
WITH...
July 1, 2016 at 2:12 pm
Have you tried querying the transaction log backups (not the active transaction log) to get this information? Do you have a transaction log backup which contains the point in...
July 1, 2016 at 1:47 pm
If you run this script, do the results look like you expect?
DECLARE @DB_USers TABLE
(DBName sysname, UserName sysname, LoginType sysname, AssociatedRole varchar(max),create_date datetime,modify_date datetime)
INSERT @DB_USers
EXEC sp_MSforeachdb
'
use [?]
SELECT ''?'' AS...
June 29, 2016 at 6:57 am
See if this will help you -
CREATE TABLE [dbo].[TableSizeGrowth](
[id] [int] IDENTITY(1,1) NOT NULL,
[table_schema] [nvarchar](256) NULL,
[table_name] [nvarchar](256) NULL,
[table_rows] [int] NULL,
[reserved_space] [int] NULL,
[data_space] [int] NULL,
[index_space] [int] NULL,
[unused_space] [int] NULL,
[date] [datetime] NULL
) ON...
June 23, 2016 at 6:30 am
Hi James, are you asking for the failover steps for both scenarios as well as how to "re-sync" them after a failover?
June 22, 2016 at 3:37 pm
You could put this script in a Sql job pointing to master, assuming you have DB Mail setup already and a profile name (insert below), and, when you schedule it...
June 22, 2016 at 11:44 am
It appears index reorganization is not supported for SharePoint databases, only index rebuilds:
– Allow Page Blocks is not supported for SharePoint Database level indexes
– You are allowed to rebuild indexes.
June 21, 2016 at 2:43 pm
Here is a start from memory and not documented - At a high level, for an in-place upgrade, you would place the 2014 sql server software on all nodes as...
June 21, 2016 at 2:34 pm
Viewing 15 posts - 136 through 150 (of 174 total)