i am not making the database into single user mode. I just leave the latest partition to read write and change the rest of the filegroups to read only. As paritions are based on date column, all new rows will be inserted into the latest file group.
That part of what I'm talking about. Last I heard, you had to set a database to "Single User" in order to be able to set a related file group to Read Only unless, of course, you're the only one in the database to begin with. Yeah... you can change it back Multi-User but I was just wondering how you set file groups to read only only without going through a pass through "SINGLE_USER".
Shifting gears back to your partitioning problem... it sounds like your table is actually a type of audit table table because you're setting partitions to Read Only based on a date. Is the date column, by any chance, a part of your PK?
is pronounced ree-bar and is a Modenism for R
First step towards the paradigm shift of writing Set Based code: Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
Although they tell us that they want it real bad, our primary goal is to ensure that we dont actually give it to them that way.
Although change is inevitable, change for the better is not.
Just because you can do something in PowerShell, doesnt mean you should. Helpful Links:
How to post code problemsHow to post performance problemsForum FAQs