You could say that..
We've had to change the IP of just the BAGs itself a few times due to ip conflict, so the steps used there have been the...

Thank you!
Could you please clarify on step #6. remove the second IP address from the listener -- I did not see the option to perform this step through SSMS...

hi Michael,
Are those BAGs (Basic Availability Groups)?
Did you perform the IP changes in Failover Cluster Manager, or within SSMS?
I believe the IPs in a BAG can't be...

hi Sue,

correct, those were the steps i carried out, and constantly keeping an eye on Event Viewer and Services, which both indicate that SQL Server Agent is in...

hi Sue,

i actually did try restarting SQL Server Agent earlier, and it did restart with no issue, however when i ran a job that job failed and then...

Node has to be added back to cluster first, see http://msdn.microsoft.com/en-us/library/ms181075(v=sql.90).aspx

I have tried creating a snapshot but it failed, error message:

[font="Courier New"]Msg 1823, Level 16, State 2, Line 1

A database snapshot cannot be created because it failed to start.

Msg 5119,...

Erland,

All data files (including those dbs that have dbcc run successfully against it) reside on the same disk drive, file system is NTFS.

Gail,

The error log only shows the DBCC results for those databases that completed successfully.

The errors are captured in the maintenance plan history:

[font="Courier New"]Executing the query "DBCC CHECKDB(N'ReportServer') WITH NO_INFOMSGS

"...

That clarifies it, thanks Lynn!

The script above does indeed work -- the email just went to the junk folder

hi gail,

we finally had the downtime to implement the -g startup parameter, specifying -g 512

so although we saw much less frequent "AppDomain 2 is marked for unload due to memory...

the results for

select * from sys.indexes where object_id=1591012749

name ...

gail,

the complete output for

DBCC CHECKDB (ExampleProd3x) WITH NO_INFOMSGS, ALL_ERRORMSGS

is

Msg 2576, Level 16, State 1, Line 1

The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer...

sorry wrong forum, my bad.

this db is restored in test, so i am trying out the dbcc repair_allow_data_loss first in the test area.

I am unable to determine which index this...