Viewing 15 posts - 151 through 165 (of 266 total)
You should only use REPAIR_ALLOW_DATA_LOSS as a last resort.
Do you mean you haven't taken full backups? Have you taken diff or log backups?
Thanks
October 31, 2017 at 6:57 am
I think the the only you can do it is to separately install Express and then attach the mdf and ldf files to your Express default location.
Thanks
October 31, 2017 at 3:13 am
SELECT OBJECT_NAME(ind.OBJECT_ID)
October 25, 2017 at 7:32 am
river1 - Wednesday, October 25, 2017 3:12 AMHello,What is the link to find the OLA scripts?
They are all here:
https://ola.hallengren.com/
Thanks
October 25, 2017 at 3:21 am
ramrajan - Monday, October 23, 2017 6:47 AMBut nobody replied
Yes they did, you were given all the information you need to write...
October 23, 2017 at 7:05 am
dextrous - Wednesday, October 18, 2017 4:51 AMDefinately locked in at 8gb
Here's the SCR from the query
80000 mb is 80gb...
October 18, 2017 at 4:56 am
October 18, 2017 at 4:20 am
Here's a SCR of the top memory munchers.
Yes the server was rebooted...
October 18, 2017 at 3:47 am
October 18, 2017 at 3:27 am
October 18, 2017 at 1:47 am
SQL Server will use all the memory it is able to, that is normal behaviour. What have you set as the Max Server Memory?
Thanks
October 18, 2017 at 1:38 am
Do you take log backups? If you have your full backup from yesterday then restore your logs up to the point where the data files were deleted.
Thanks
October 17, 2017 at 5:10 am
October 16, 2017 at 8:34 am
You should be fine to shrink the log on your principal as a one off activity, obviously it will be mirrored.
Thanks
October 16, 2017 at 3:22 am
Your log will probably be 60gb for a reason. Have a look at any maintenance tasks you have scheduled particularly index rebuilds as this is pretty heavy on the log....
October 16, 2017 at 2:54 am
Viewing 15 posts - 151 through 165 (of 266 total)