Can we use ManagePartition 3.0 for a remote database?

Jul 3, 2013 at 4:28 PM

We have an ETL server that runs our SSIS packages. Our DW database is on another server. When I run ManagePartition on the ETL Server in our SSIS package (and from the command prompt) it looks like it expects our database to be on the same server as where the executeable is located. Is this true. We do have a sql instance on the ETL server but the databases there are more for logging (Not our DW database). I get this error on the ETL server.

I even tried using the executeable on the db server from the ETL server and got the same error.

E:\3rdPartyExecuteables>\server\d$\3rdPartyExecuteables\ManagePartition.exe /C:ClearPartition /d:DW/s:DW /A:FactAux /t:Fact /p:1 /K:+
Object reference not set to an instance of an object.

Jul 3, 2013 at 5:44 PM

Hi Sean –

ManagePartition will work with any SQL Server instance on your network. Inside the Readme file is a description of call syntac, excerpt below:


/Command:<string> short form /C command, default = CreateStagingFull

/Server:<string> /S Server name, default = (local)

/User:<string> /U User name, default = null

/Password:<string> /P Password, default = null

/Integrated[+|-] /E Integrated Security, default +

/Database:<string> /d Database name

/Schema:<string> /s Schema name – use quotes as delimiter if needed

What is missing below is your remote server name preceded by /S:


E:\3rdPartyExecuteables>\server\d$\3rdPartyExecuteables\ManagePartition.exe /C:ClearPartition /S:MyServer /d:DW/s:DW /A:FactAux /t:Fact /p:1 /K:+

Jul 3, 2013 at 6:11 PM
Thank you. I did read the readme about 4 times but I missed this. Thank you!