Viewing 15 posts - 256 through 270 (of 59,099 total)
Thank you for the update, Steve. If they need someone to test, I can help.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 3, 2025 at 4:07 am
Too funny. A SPAM post was removed but the "Discussion" section still has the title with the SPAM info from the title still intact. That's another item they'll need to...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2025 at 12:43 am
On my physical laptop ... just testing the process before using Network share.
Is the "SQL Server" you're testing on also on your laptop?
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2025 at 12:35 am
I can't help because I don't use PowerShell for much but I am curious. The output file in your original post is "c:\fileloading\rmcstdetails.csv". Where is the "c:\" drive physically located? ...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2025 at 12:28 am
I remember when I was a young kid and listened to Walter Cronkite talk about the year 2000, which was decades away at the time. Once again, it's decades away...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 1, 2025 at 2:55 am
Since MS messed up with performance starting in 2019 and hasn't made it any better in 2022, I sadly pronounce that I Don't Believe Anymore but I keep Doing the...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 1, 2025 at 2:24 am
I'm confused. You're talking about Oracle but you're posting in an SQL Server 2019 forum.
Since I'm not privy to your previous attempts and have never used "CDATA", what is it...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 30, 2024 at 10:18 pm
I would recommend updating statistics after you re-attach the database.
I've seen several people say that. I have to ask "Why"? The statistics are stored in the database just like...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 30, 2024 at 10:00 pm
Just curious, Rod. Did you ever figure this out?
--Jeff Moden
Change is inevitable... Change for the better is not.
December 30, 2024 at 9:53 pm
Between updates, just set the database to "Read Only". As an alternative, you can create individual File Groups with one or more Files in each and set those File Groups...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 30, 2024 at 9:51 pm
I don't work with Powershell in most cases, which means I'm not very good with it. GOOGLE seems to work for this though.
Try this link.
https://sqlstudies.com/2022/07/07/powershellbasics-expanding-the-column-width-to-avoid-truncation/
--Jeff Moden
Change is inevitable... Change for the better is not.
December 27, 2024 at 4:58 am
The following supposedly applies only when your database is in the BULK_LOGGED or SIMPLE Recovery Models.
There is a feature known as "Fast Inserts". I wrote about that hot mess back...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 26, 2024 at 10:45 am
BWAA-HAA-HAA! This was more of a test of knowledge about Christmas songs than I thought it would be. 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
December 26, 2024 at 9:43 am
Merry Christmas, Steve, and thank you for the early present of seeing you at the Pittsburgh SQL Saturday. It was a real treat, my ol' friend.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 26, 2024 at 2:47 am
Thank you kindly for the feedback, windchaser... especially after nearly 20 years! I couldn't believe it.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 24, 2024 at 9:36 pm
Viewing 15 posts - 256 through 270 (of 59,099 total)