New answers tagged

1

I finally figured it out. The main reason for the crashes and the mysql_upgrade error was related to missing and/or corrupted primary keys of the mysql table. There were also a couple missing records in the mysql.db table, which likely couldn't update previously due to the GRANT crashes and would have been related to Plesk "Database Servers" ...


0

I have working SQL to determine which machine is the PRIMARY or SECONDARY server and to use within the Stored Procedure scheduled to run on both machines SQL: select ars.role_desc,ag.name,ars.is_local from sys.dm_hadr_availability_replica_states ars inner join sys.availability_groups ag on ars.group_id = ag.group_id NOTE: I was expecting the ...


5

You cannot restore a SQL Server 2000 database onto a SQL Server 2014 instance. You need to restore to SQL Server 2008 or 2008 R2 instance first, then take a backup of that database which you can then restore to 2014. There a lot of features from SQL Server 2000 that have been discontinued in SQL Server 2014. See this list for the details about what ...


1

Follow this article and use upgrade advisor.


5

Problem resolved by adding an alias to the instance in the SQL Server Agent Configuration. The alias was defined using the fully qualified domain name of the server. Example:servername.domain.biz\instance_name otherwise the agent will still error out and shutdown. Also, the Agent was disabled in sp_configure sp_configure 'Agent XPs', 1 go reconfigure ...


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 ...



Top 50 recent answers are included