Viewing 15 posts - 4,606 through 4,620 (of 22,211 total)
How are your wait statistics?
This indicator is just an indicator of load. If it goes up or down compared to the baseline (which I get that you're just establishing), it...
July 11, 2016 at 5:45 am
you might want to explore Minion Reindex. It has a bunch of mechanisms for dealing with blocking that might make it work better for you than Ola's scripts.
July 8, 2016 at 10:40 am
SQL!$@w$0ME (7/8/2016)
Grant Fritchey (7/8/2016)
So the majority of your queries, or the most frequently called queries use all these columns when filtering:
[Col1] ASC,
[Col2] ASC,
[Col3] ASC,
[Col4] ASC
Majority of the queries use all...
July 8, 2016 at 10:34 am
So the majority of your queries, or the most frequently called queries use all these columns when filtering:
[Col1] ASC,
[Col2] ASC,
[Col3] ASC,
[Col4] ASC
That's a very wide key, three 256 varchars. To...
July 8, 2016 at 8:37 am
The core guideline that the best clustered index is a unique, not null, monotonically increasing integer column (basically, identity), is true. That said, it doesn't rule my life. For example,...
July 8, 2016 at 8:30 am
SQL!$@w$0ME (7/8/2016)
Or is it better to create Primary key (identity...
July 8, 2016 at 7:19 am
Phil Parkin (7/8/2016)
Grant Fritchey (7/8/2016)
Since the clustered index defines data storage, I recommend that the cluster be the most commonly used path to the storage. If...
July 8, 2016 at 6:38 am
Phil Parkin (7/8/2016)
SQL!$@w$0ME (7/8/2016)
Does the clustered key column(s) has to be NOT NULL/UNIQUE as best practice?
Yes. Otherwise SQL Server has to create its own 'uniquifier', to make the rows unique....
July 8, 2016 at 6:31 am
I'm in agreement with Kevin.
Since the clustered index defines data storage, I recommend that the cluster be the most commonly used path to the storage. If that's the primary key,...
July 8, 2016 at 4:28 am
You'll be able to see the objects, but you won't be able to tell what they are or where they came from.
July 7, 2016 at 7:45 am
So, my suggestion is, leave the compatibility at 120 and just add the traceflag to force it to use the older cardinality estimator.
July 7, 2016 at 5:13 am
There are differences, and this could account for everything. The first plan I looked at, 1027.sqlplan, is using the 70 Cardinality Estimation Engine. That means that database is using the...
July 7, 2016 at 4:05 am
Jeff Moden (7/6/2016)
tezsb (7/6/2016)
July 6, 2016 at 10:22 am
Generally, you'll have the same IP address for very long periods of time. However, I travel a lot and demo Azure at many different locations. It's quite easy to quickly...
July 6, 2016 at 4:08 am
I absolutely would not seek licensing advice on the internet. Microsoft is going to decide if you're in compliance or not. I'd go there to ask.
July 6, 2016 at 4:02 am
Viewing 15 posts - 4,606 through 4,620 (of 22,211 total)