Viewing 15 posts - 76 through 90 (of 180 total)
Try the next thing.
Create a database with the same exact name and exact files in the correct orders.
i.e: DB NAME = TEST
FILES = File1.mdf, file2.mdf, file3.mdf and log.ldf.
take the database...
January 3, 2020 at 1:36 pm
Usually, the dashboard shows every replica, is the secondary replica displayed in the dashboard?
January 2, 2020 at 1:47 pm
Hello,
I suppose you have access to the package, the only way to find out is downloading it and executing it and while you are at it, you can actually set...
November 25, 2019 at 12:42 pm
Why not just take the backup in that server?
Just share a folder/drive on that server and give the sql server service account permissions to write there.
November 14, 2019 at 12:29 am
To add something,
Its recommended to have all the tempdb data files the same size, that's why Microsoft have added a feature in which not only one file but all of...
November 5, 2019 at 1:44 pm
We had this issue migrating from 2008 R2 to 2016 and by issues i mean, performance degradation in some queries. don't know if you upgraded from that early of a...
October 4, 2019 at 7:37 pm
If you have corruption in older backups, try restoring and executing DBCC CHECKDB with repair_allow_data_loss in another environment.
If it fix the issues great, run DBCC checkdb again to check for...
October 1, 2019 at 7:41 pm
Which version of SQL Server are you using?
There's a blog post from Paul Randal regarding an issue when migrating from 2014 to 2016 or later versions, you might wanna take...
October 1, 2019 at 3:05 pm
Yes Jeff, i think the SAN guys found some issues and have been working with the provider, no outages, thank god it was only one filegroup.
prettsons, looks like defunct filegroups...
September 25, 2019 at 1:38 pm
Thanks!.
We could restore and even though the database was corrupted, we used the standard restore procedure.
Full > differential > logs
At the time we got corruption, our full and differential backups...
September 23, 2019 at 3:57 pm
Thanks for your reply guys,
We could not remove the corrupted filegroup.
Mr. Steve, we found the issue and fixed is asap, we have open cases with our different partners and finding...
September 23, 2019 at 12:48 pm
The last one completed and this was the SQL Server message:
DBCC CHECKDB WITH REPAIR_ALLOW_DATA_LOSS
Date 9/18/2019 4:02:02 PM
Log SQL Server (Current - 9/18/2019 4:44:00 PM)
Source spid67
Message
DBCC CHECKDB (DB_CLONE, repair_allow_data_loss) WITH all_errormsgs,...
September 19, 2019 at 11:58 am
Hi Jeff!, thanks for replying!
There were errors and the new CHECKDB WITH REPAIR_ALLOW_DATA_LOSS fixed again lots of errors, i'll add the output(attached) and the SQL Message.
After it completed we ran...
September 18, 2019 at 4:09 pm
After running DBCC CHECKDB with REPAIR_ALLOW_DATA_LOSS, it lasted 3-4 hours in a VLDB, not even mad, that's amazing
this was the output.
SQL server log:
Message
DBCC CHECKDB (DB, repair_allow_data_loss) WITH all_errormsgs, no_infomsgs executed...
September 18, 2019 at 1:35 pm
Viewing 15 posts - 76 through 90 (of 180 total)