Viewing 15 posts - 76 through 90 (of 317 total)
Have you tried to restore it with replace?
Sounds like the issue might be with the existing database you were trying to restore to.
July 25, 2014 at 4:29 pm
Do you have a job that rolls the error log at 10:39?
Did something happen to the permissions on the log folder?
July 25, 2014 at 10:09 am
Then remove the dependency.
In general you must be very careful using snapshots.
If your database has a lot of churn and frequent index maintenance you will require a lot of snapshot...
July 25, 2014 at 9:02 am
The question is, do you want to bring the SQL server resource online even if there is an issue with the snapinfo LUN?
If YES, then you do not need the...
July 24, 2014 at 3:09 pm
Agree with Gazareth.
The app will try Primary first. When it is acting as the mirror, the login attempt cannot open the mirror database, and thus fails.
July 24, 2014 at 2:59 pm
I agree that 230k rows in 6 hours seems very slow.
Couple of additional questions:
Are the two servers equivalent in term of CPU,memory and I/O subsystem?
Do they have similar work load?
July 24, 2014 at 2:36 pm
In the case of mobile devices, i am not sure what the best strategy is.
How is the metadata situation on the devices?
Google that error message. There are ways to...
June 26, 2014 at 12:16 pm
As long as you are monitoring overall disk space and have reports on database growth (optional) you should be fine.
Make sure growth increment is not set to default.
In general however...
June 25, 2014 at 6:17 pm
I run it weekly in order to keep the metadata under control (generate 8M+ contents rows per week).
I keep retention period long by default and simply shorten it while I...
June 25, 2014 at 5:36 pm
Also, what is the failover requirement?
Automatic or managed?
May 16, 2014 at 10:12 am
Yes in your failover set up, you must rebuild mirroring every time you will failover.
Re Async:
I have in the past managed geographically redundant async mirrored pairs.
With async mirroring, failover is...
May 16, 2014 at 10:07 am
Regarding mirroring, the act of of switching over requires you putting the mirroring into synchronous mode.
The process you described essentially broke the mirroring.
Any failover script of an asynchronously mirrored pair...
May 16, 2014 at 9:40 am
You should rebuild your indexes after the shrink.
When you shrink, be sure to leave enough space to accommodate the rebuild of your largest clustered index/table.
May 15, 2014 at 4:56 pm
What happens if you rebuild the clustered index?
April 30, 2014 at 12:23 pm
If a connection is hung, inactive or stuck on a single long running statement, then last_batch should not be updating.
However that does not equate with the beginning of a transaction,...
April 28, 2014 at 6:42 pm
Viewing 15 posts - 76 through 90 (of 317 total)