September 3, 2020 at 10:10 am
Thanks for posting your issue and hopefully someone will answer soon.
This is an automated bump to increase visibility of your question.
September 3, 2020 at 3:56 pm
As you're finding out, Partitioned Tables don't make such changes easy. I drank the MS "Kool-aid" a couple of years back (only 1.2 TB total, though) and I'm in the process of changing the one I have to a Partitioned View.
For what you want to do, I believe you going to have to go through the throws of a "Switch Out", move the result table to a file/filegroup, change the Partition File and Schema, etc, etc, and, IIRC, that might all be for naught because I don't believe you can spread a partitioned table to another "server" like that.
Hopefully, a fellow by the name of Eddie Wuerch shows up. He has more very-large partitioning experience I know.
--Jeff Moden
Change is inevitable... Change for the better is not.
September 3, 2020 at 4:07 pm
There were distributed partitioned views, but these didn't work well, created dependencies and didn't necessarily help performance - https://techcommunity.microsoft.com/t5/datacat/distributed-partitioned-views-federated-databases-lessons/ba-p/304955
Not sure they're still around. You can use a linked server for the queries, but I wouldn't join that into a local view. I'd have a separate view that users query to get archive data. Meaning they explicitly ask for it.
As for moving this data. I think bcp out is the best way, and the removing those partitions., as Jeff mentioned.
September 14, 2020 at 7:29 am
Thanks Jeff, I managed to switch out the old data, and moved the data to new server.
September 14, 2020 at 7:32 am
Thanks Steve, I did use BCP, thanks again.
Viewing 5 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply