Viewing 15 posts - 9,421 through 9,435 (of 59,091 total)
Quite a few people use Ola Hallengrens solution for this, if you google that name it will come right up.. just schedule the job to run during your maintenance...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 25, 2019 at 1:25 am
If you don't have mirroring or log shipping or anything else running that would be damaged by changing the Recovery Model, do a log backup, change the recovery model to...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 24, 2019 at 10:00 pm
I'm thinking that "everything changes" when you're using a remote connection but don't know for sure. I supposed "It Depends" on the connection settings. If you've come across connection settings...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 24, 2019 at 9:52 pm
Another possibility along with the known problems of compression and page splits is that you may have a shedload of indexes that are all doing the same deadly dance.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 24, 2019 at 3:42 pm
The table must remain compressed
That is very likely your biggest problem. If you're updating pages and the updates are "ExpAnsive" (the rows get bigger), then you run into rampant...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 24, 2019 at 3:41 pm
Just make damned sure that you know who can access your stuff on the cloud. A lot of people don't setup security right. There's been more than one instance of...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 24, 2019 at 2:41 pm
I've got to disagree about SQL Server not being good about code reuse and say "It Depends". And it really depends when it comes to views because they're frequently written...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 24, 2019 at 2:32 pm
You'll probably get some responses if you make the data you posted "readily consumable". Please see the link in my signature line below for one way to do that.
Also, all...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 24, 2019 at 2:21 pm
Each view is bit complicated and brings back huge volume of data and they are grouped
I know it's not the answer you're looking for but the two items above...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 24, 2019 at 2:04 pm
be aware, that adding dates / times only works with the DATETIME data type but not with the new (ANSI compatible) DATETIME2 (this would cause Error 8117: Operand data...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 23, 2019 at 10:05 pm
Hi Jeff Maden, Thank you for taking time and explain things. I will try my best and study the concepts needed.
You could at least apply enough attention to...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 22, 2019 at 1:44 pm
I guess I don't understand the need for the parameters of BOTH, LEADING, and TRAILING. Apparently the industry standard has changed over time because, for me, TRIM() always meant both...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 22, 2019 at 1:40 pm
What is this PDW & Poly Database movement about? I see some errors on those services in my SQL log.
We can't see your logs. You should post the errors...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 22, 2019 at 11:57 am
TRIM can remove characters other than spaces, LTRIM and RTRIM an only remove spaces 😎 This works fine
SELECT LEN(TRIM('.' FROM '.....SSMS.....'))
Good lord... talk about a...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 22, 2019 at 11:49 am
Actual_DateReceivedVendor
201804250 10256
201805023128.57 10256
201806143103.09 10256
201808023120.19 ...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 22, 2019 at 11:46 am
Viewing 15 posts - 9,421 through 9,435 (of 59,091 total)