Viewing 15 posts - 361 through 375 (of 3,221 total)
Jeff Moden (11/22/2016)
...There's nothing that says a table can't have more than one unique index on it.
I am always amazed at how many people struggle to believe this.
Gaz
-- Stop your grinnin' and drop your linen...they're everywhere!!!
November 23, 2016 at 5:32 am
Charles Kincaid (11/22/2016)
Gaz
-- Stop your grinnin' and drop your linen...they're everywhere!!!
November 23, 2016 at 5:31 am
Gary Varga (11/22/2016)
Thanks for posting your final solution.(Mine worked for me but maybe copy 'n' paste lost the newline character).
Looking at the original post I don't know how mine ever...
Gaz
-- Stop your grinnin' and drop your linen...they're everywhere!!!
November 22, 2016 at 8:20 am
Thanks for posting your final solution.
(Mine worked for me but maybe copy 'n' paste lost the newline character).
Gaz
-- Stop your grinnin' and drop your linen...they're everywhere!!!
November 22, 2016 at 8:19 am
I would get the individual values as such:
$v = $string.Split(",");
This splits the values as follows:
AvgSQLCpu
AVGCpu
AVGOtherCpu
100
97
2
alertType
alertStatus
alertGenerate
alertDetails
HIGHCPU
ERROR
0
Where $v[0] is the string "AvgSQLCpu", $v[1] is the string "AVGCpu", $v[2] is the string "AVGOtherCpu"...
Gaz
-- Stop your grinnin' and drop your linen...they're everywhere!!!
November 22, 2016 at 7:30 am
It seems that generally we need to consider warnings to be important enough to warn the user immediately, specific performance measurement important enough to be monitored or events important enough...
Gaz
-- Stop your grinnin' and drop your linen...they're everywhere!!!
November 22, 2016 at 7:21 am
RonKyle (11/21/2016)
I think there is a very specific distinction between data which is unnormalized vs denormalized
I agree with you, and maybe you, I, and some others can make that distinction....
Gaz
-- Stop your grinnin' and drop your linen...they're everywhere!!!
November 22, 2016 at 3:49 am
Absolutely. I have only missed two that I wanted and one of those I got when it was offered again on a different day.
Gaz
-- Stop your grinnin' and drop your linen...they're everywhere!!!
November 22, 2016 at 2:45 am
As usual it appears to be human execution and choices rather than technology that caused the issues...trouble is that technology is an enabler (often of dreadful things).
Gaz
-- Stop your grinnin' and drop your linen...they're everywhere!!!
November 21, 2016 at 9:35 am
It always amazes me the number of experienced professionals who do not consider the longevity of software and databases. Some must work on too many greenfield projects and never support...
Gaz
-- Stop your grinnin' and drop your linen...they're everywhere!!!
November 21, 2016 at 5:50 am
Markus (11/17/2016)
Microsoft releases new things for SQL Server to Azure first. Then it will become GA to on site installs after that.
Exactly that.
Gaz
-- Stop your grinnin' and drop your linen...they're everywhere!!!
November 21, 2016 at 5:12 am
All team members should do both types over time. Don't split up tasks too small but do break down what you can. Also, automate as much as possible.
Gaz
-- Stop your grinnin' and drop your linen...they're everywhere!!!
November 18, 2016 at 9:30 am
It does appear that the Azure first policy is certainly bearing the fruits of their labours.
Gaz
-- Stop your grinnin' and drop your linen...they're everywhere!!!
November 17, 2016 at 9:51 am
As a developer, I only care about two aspects (leaving all else to DBAs):
I hope that this is something that pleases...
Gaz
-- Stop your grinnin' and drop your linen...they're everywhere!!!
November 17, 2016 at 1:56 am
I have known three SQL Server and Windows using companies that seriously considered how they could leverage Linux; one stayed as they were, one moved everything except one SQL Server/Windows...
Gaz
-- Stop your grinnin' and drop your linen...they're everywhere!!!
November 17, 2016 at 12:31 am
Viewing 15 posts - 361 through 375 (of 3,221 total)