Viewing 15 posts - 466 through 480 (of 49,571 total)
January 10, 2018 at 3:54 am
You start a subquery on line 6, but you never end it with a bracket nor alias the subquery. That should go between rows 10 and 11.
You'll also need...
January 10, 2018 at 1:10 am
January 9, 2018 at 7:34 am
Sue_H - Tuesday, January 9, 2018 6:44 AMWith dm_db_index_physical_stats, specifying default, null or 0 uses the current database.
NULL, 0 or DEFAULT...
January 9, 2018 at 7:05 am
January 9, 2018 at 3:38 am
I'm not a site moderator.
And I know Sue pointed it out, that's why my post was a reply to Sue
January 9, 2018 at 3:18 am
One problem with the script is that it is hard coded to use db_id...
January 9, 2018 at 1:30 am
Your workarounds are unfortunately useless if you can't restrict permissions. Someone who wants to drop a DB can disable the trigger, drop the DB, enable the trigger and there's no...
January 9, 2018 at 1:28 am
You should mention in that script that it's index scans since the last time the database or SQL Server were restarted. Not over all time.
January 9, 2018 at 12:57 am
Change it via the machine's Control Panel
January 8, 2018 at 9:53 am
jeffshelix - Monday, January 8, 2018 9:45 AMThanks, but not sure how to do a sub query . . 🙁
There's a subquery...
January 8, 2018 at 9:51 am
Column aliases are applied after the rest of the statement has been evaluated. Hence you can't define and use a column alias in the same level of scope.
Put...
January 8, 2018 at 9:44 am
The two different promotion tables are a concern in terms of DB design. You can also combine two of those IF statements into one, as what they do is identical.
January 8, 2018 at 5:37 am
Details?
Migrating to a new version? A different server? The cloud? A different database engine?
January 8, 2018 at 12:59 am
Few things.
If a full log caused a suspect DB, then you've hit a bug where there was insufficient log reservation. Please report that to Microsoft with a repo if...
January 7, 2018 at 10:24 am
Viewing 15 posts - 466 through 480 (of 49,571 total)