Viewing 15 posts - 2,056 through 2,070 (of 59,091 total)
We never intended for SQL to be used for text management. You ought to be using the proper tool to store this data. As part Lane put it in...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 2, 2023 at 3:38 am
A few of the other folks share the same sentiment as I... why are you doing this in PoSh? To be sure, that's a rhetorical question. 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
February 2, 2023 at 3:31 am
I would manually update the file from a folder, and this list of tables won't change. The alert will run daily maybe every x hours..
We had an issue where...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 1, 2023 at 10:42 pm
I'm using OPENROWSET to put the contents of a text file into a VARCHAR(MAX) column. However, it is stripping the carriage returns and line feeds out, so when I...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 1, 2023 at 10:37 pm
Heh... all of this reminds me of the great "Toilet Paper" debate... Unroll from the top or the bottom? Of course, there are people like me that prefer a vertical...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 1, 2023 at 5:49 pm
I STRONGLY second the notion that index maintenance on rowstore indexes is pretty useless if based on logical fragmentation. I'll also tell you that it can cause major blocking on...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 1, 2023 at 4:18 pm
Thanks, Steve. I've been doing that same thing for years to create "character usage histograms" using either a Tally Table or fnTally. So has Itzik with his "GetNums"...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 1, 2023 at 4:06 pm
thanks everyone. i will review and get back to you if I have any questions
If you do a shrink, make sure that you do a check on fragmentation both...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 31, 2023 at 6:49 am
I apologize... that last post slipped right past me. I know it's been a couple of months but thank you for the feedback on the ISO algorithm. Also, I thought...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 31, 2023 at 5:00 am
It's always a pain. Have you considered investing in something like "SQL Clone" from RedGate?
Redgate also has tools to help you modify PII so that it's no longer PII... it'll...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 31, 2023 at 12:27 am
Tom Uellner ,
If you're still around, do you have any links on the subject at hand?
--Jeff Moden
Change is inevitable... Change for the better is not.
January 30, 2023 at 11:54 pm
Thanks, Grant. I remember you speaking of Brad's input on the subject before. I've not found it, yet, either.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 30, 2023 at 11:53 pm
I realize this thread is a couple of years old now but, I have to ask the question, can either of you share some links to articles where someone states...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 30, 2023 at 6:53 pm
I want to replicate them continuously (once a day) on postgres.
Wholesale table change or only things that have changed?
Either way, I'd explore the possibility of a BCP OUT...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 30, 2023 at 5:08 pm
Heh... another "metric" that I'm really sick and tired of is "index fragmentation", especially when it comes to 3rd party vendors, both good and bad. You call them and ask...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 30, 2023 at 3:21 pm
Viewing 15 posts - 2,056 through 2,070 (of 59,091 total)