Viewing 15 posts - 2,641 through 2,655 (of 49,571 total)
It didn't get overwritten.
The default, when restoring a copy of an existing DB that's in full recovery model, is to first take a tail-log backup of the original. Bad default,...
August 14, 2016 at 2:44 pm
Please post new questions in a new thread, and give us as much information about the server and its config as possible, as well as the errors that you're getting.
August 14, 2016 at 10:56 am
PJ_SQL (8/13/2016)
It was from SQL Server Reports.
And the one you used draws its data from the default trace. (the others query default trace, DMVs or system tables depending on the...
August 14, 2016 at 4:59 am
polkadot (8/14/2016)
Usually all versions are listed in drop down, so it's inconsistent for them to only list 2012
That's the previous version of MSDN. It's been changed (though spme of the...
August 14, 2016 at 4:57 am
Sure. Start with google's first 10 results. Once you've got though that, post any questions you stuill have.
August 13, 2016 at 7:48 pm
PJ_SQL (8/13/2016)
I was able to find the information from Standard reports\Configuration Change history in sql server 2012.
So, from the default trace. Good.
August 13, 2016 at 7:46 pm
https://msdn.microsoft.com/en-us/library/hh213228.aspx
Pertenant part:
THIS TOPIC APPLIES TO: SQL Server (starting with 2012)
, and there't no "This feature is deptecated" block at the top
August 13, 2016 at 6:54 pm
It should be in the default trace, if it didn't happen too long ago (default trace keeps a limited amount of events)
August 13, 2016 at 6:50 pm
Failover clustering has a single point of failure - the storage. It's designed to protect against hardware failures of the machines (the shared storage is more commonly a SAN or...
August 13, 2016 at 3:08 am
TomThomson (8/11/2016)
GilaMonster (8/11/2016)
TomThomson (8/10/2016)
GilaMonster (8/10/2016)
First time in years that I'm flying somewhere just for a vacation, no conferences involved. Scotland, to save anyone from wondering.
Any particular place in Scotland? ...
August 12, 2016 at 3:43 pm
Because spacial indexes work by creating hidden tables. CheckDB picks up the hidden table name, but you can't directly affect that table.
And did you recreate the index? If so, is...
August 11, 2016 at 2:28 pm
Make sure your queries run fast enough that the app won't hit its timeout while waiting.
August 11, 2016 at 1:55 pm
Welsh Corgi (8/11/2016)
GilaMonster (8/11/2016)
Welsh Corgi (8/11/2016)
GilaMonster (8/11/2016)
ThomasRushton (8/11/2016)
Have you tried dropping & recreating the index on that view?as in, drop the spacial index and recreate it.
That is what I...
August 11, 2016 at 1:53 pm
Welsh Corgi (8/11/2016)
I run the following command in a test environment which contains the same index and I do not get any errors:
DBCC CHECKDB(PrismData)
WITH EXTENDED_LOGICAL_CHECKS, DATA_PURITY, NO_INFOMSGS, ALL_ERRORMSGS, TABLERESULTS
Hmm.
Why...
August 11, 2016 at 12:54 pm
Welsh Corgi (8/11/2016)
GilaMonster (8/11/2016)
ThomasRushton (8/11/2016)
Have you tried dropping & recreating the index on that view?as in, drop the spacial index and recreate it.
That is what I wanted to do...
August 11, 2016 at 12:46 pm
Viewing 15 posts - 2,641 through 2,655 (of 49,571 total)