Viewing 15 posts - 691 through 705 (of 49,571 total)
There's nothing wrong here.
That event was added in SQL Server 2016.
It won't be present on a 2014 server. Nothing to do with the service pack,...
October 29, 2017 at 9:20 am
That event was added in SQL Server 2016
https://www.sqlskills.com/blogs/bobb/over-1000-xevents-in-sql-server-2016-ctp2-here-are-the-new-ones/
October 29, 2017 at 9:09 am
You can get rid of them by dropping them (DROP STATISTICS). The Query Optimiser will recreate them as soon as it needs them, so unless the pattern of work has...
October 28, 2017 at 11:14 pm
October 28, 2017 at 9:52 am
farax_x - Tuesday, October 17, 2017 4:48 AMHow can I recover this database?
Restore from backup. You cannot mix and match data files.
If...
October 28, 2017 at 9:51 am
October 27, 2017 at 3:24 pm
SQL!$@w$0ME - Friday, October 27, 2017 6:46 AMThanks Gail! Does that mean I don't have to worry about cert expiration?
Um...
October 27, 2017 at 10:12 am
Gamleur84 - Friday, October 27, 2017 9:56 AMHow about tweaking the query/index in order to get a Clustered Index Seek ?
Remove columns...
October 27, 2017 at 10:10 am
October 26, 2017 at 10:36 pm
October 26, 2017 at 10:33 pm
Key lookup and RID lookup are the same thing, they're single-row reads of either the clustered index (key) or heap (RID)
They certainly would be blocked by X locks,...
October 26, 2017 at 5:21 pm
https://docs.microsoft.com/en-us/sql/t-sql/statements/create-certificate-transact-sql
EXPIRY_DATE =' datetime'
Is the date on which the certificate expires. If not specified, EXPIRY_DATE is set to a date one year after START_DATE....
October 26, 2017 at 4:01 pm
You have a hardware problem. Corruption is mostly a hardware problem. It's got nothing whatsoever to do with the size of the index.
October 26, 2017 at 9:47 am
October 19, 2017 at 3:54 pm
October 19, 2017 at 9:39 am
Viewing 15 posts - 691 through 705 (of 49,571 total)