InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comMon, 20 May 2013 20:29:37 GMT20http://www.sqlservercentral.com/Forums/Topic1037499-234-1.aspxI have encouraged our DBA team to get powershell installed (SQL 2005) - no luck yet. Meanwhile I use a procedure for each partitioning function. Here is an example where boundaries are YYYYMM. For monthly loads - we call this in ETL process before insert. You'll notice no use of filegroups - it would take a bit more code if we were strategically using filegroups. Ommitted try/catch, error handling to keep is short. create procedure [dbo].[CreateYearMonthPartition] @YearMonth int asdeclare @PartitionId int -- check if partition for this period already exists select @PartitionId = rv.boundary_id + 1 from sys.partition_functions pf join sys.partition_range_values rv on pf.function_id=rv.function_id where pf.name='YearMonth_RangeR' and rv.value=@YearMonth if @PartitionId is null begin -- partition does not exist; create it. alter partition scheme [YearMonth_RangeR_scheme] next used [PRIMARY] alter partition function [YearMonth_RangeR]() split range (@YearMonth) endTue, 21 Dec 2010 09:36:19 GMTIdea Deadbeathttp://www.sqlservercentral.com/Forums/Topic1037499-234-1.aspxThanks for continuing the series on this subject.Tue, 21 Dec 2010 09:28:21 GMTSQLRNNRhttp://www.sqlservercentral.com/Forums/Topic1037499-234-1.aspxComments posted to this topic are about the item [B]<A HREF="/articles/Partitioning/71656/">Automate Sliding Window Partition Maintenance: Part II</A>[/B]Mon, 20 Dec 2010 22:34:17 GMTHugh Scott