How do I delete a filesystem from the ImageServer Configuration.

I have made it off-line (by removing read and write) and merged the studies on that filesystem to another store, but I can't remove the partition from the configuration?

 

Hans,

Unfortunately we don't have a way to delete filesystems from the Web GUI. We mostly do not do this right now because we are not tracking how many studies are on a filesystem (although you can infer this from the database), which we'd use to enable/disable a delete button where appropriate.

Anyways, assuming there are no studies left on the filesystem, you could delete it from SQL using this script in SQL Management Studio (and substituting the real path of the filesystem you're working with):

declare @FilesystemGUID as uniqueidentifier
select @FilesystemGUID=GUID from Filesystem where FilesystemPath='c:\FS'
delete from ServiceLock where FilesystemGUID=@FilesystemGUID
delete from Filesystem where GUID=@FilesystemGUID

Steve
Steve

hello everyone, why do i feel so hmm gifted when it comes to sql: which can mean one of two things in this politically correct world we live in... smart or retarded, in my case its retarded when it comes to sql.. sometimes i wish i had gotten into programming and database management instead of networking and radiology...

anyways i added a file system to do a test to see if a study that is manually copied in there can be processed into clear canvas, my buddy user: alara: has a dilemma he needs to add a drive that is full of patient studies from another PACS: RAMSOFT and set that drive as a fie system, in order to run services on it so all the studies in there can be imported into clear canvas in order for CC to do a File-system Re-inventory and rebuild the XML so the DIR structure is correct and then he can copy the directories back into the main partition and re-inventory/rebuild, we have been struggling with this migration for while..

after realizing its a partition that the service scheduling can be done on i tried it that way, nothing seems to happen file system re-inventory runs but nothing happens no studies are imported into the new partition ??

so can this be done this way ? of is the DICOM transfer the only alternative ?

he has tried a DICOM transfer but the PET studies transfer over via RAMSOFT server with the headers changed and then they are not viewable, if the studies are imported into the workstation first then everything is fine but doing it this was is very time consuming.

so this would mean another server in place so it auto transfers the files over via rules?

im also trying to remove the file system i added but no delete button, the above post by Steve would probably be helpful if i understood SQL database management better but i dont and im stuck trying to delete the file system, sheesh what a nightmare..

the file system name is TEST any help with this and getting the old studies imported correctly would be appreciated..

thanks robert

Robert,

The reinventory mechanism requires that the files already be in the directory structure of the ImageServer. It does scan other formats and then move files around, it expects them to be in place already. From what you've described, I'd assume this is the source of some of your problems.

Concerning the service scheduling, this actually linked to filesystems, and not partitions. The reinventory will scan files from each partition on a filesystem, if they exist.

As for importing, the 2.0 ImageServer has an "Import" folder, where you can drag DICOM files into, and the system will automatically import the files into the partition associated with the folder. Note that only 1 import folder is created on one of your filesystems, there is not an import folder on all the filesystems. You can look at the service scheduling page to see which filesystem the folder was placed on. You should be able to just copy your files onto this folder, and the system will import the studies, and automatically copy the files to the filesystem with the most free space available...

Steve

Robert,

First, no, there is no easy way to point the primary incoming directory to another directory. The directory must be within the actual "filesystem" that's configured. The Filesystem is supposed to correspond to a physical filesystem, and the import directory is supposed to be within that directory.

As for some SQL to delete a filesystem with a Description set to 'TEST', this should do it:

declare @FilesystemGUID as uniqueidentifier
select @FilesystemGUID=GUID from Filesystem where Description='TEST'
declare @Count as int
select @Count=COUNT(*) from FilesystemStudyStorage where FilesystemGUID=@FilesystemGUID
if @Count = 0
BEGIN
delete from ServiceLock where FilesystemGUID=@FilesystemGUID
delete from Filesystem where GUID=@FilesystemGUID
END

Note that there cannot be any studies stored on the filesystem for this to work. if there are studies stored on the filesystem, it will not delete the filesystem.

Steve

I tried your script to delete a filesystem and recreated a new one. Now I do not see any Incoming directory? Is there a way to recreate the Incoming directory?

If you just run this insert, the first time it runs, it will assign itself to a filesystem on tier 1:

INSERT INTO [ImageServer].[dbo].ServiceLock
([GUID],[ServiceLockTypeEnum],[Lock],[ScheduledTime],[FilesystemGUID],[Enabled])
VALUES (newid(),202,0,getdate(),null,1)

Thanks for the tip!

I tried the script and I got this error

Invalid object name 'ImageServer.dbo.ServiceLock'

Sorry - I figured it out , I tried the script on an ImageServerAlpha database.