We purchased replacement hard drives for the DR data this past... much bigger and a lot faster. Wahoo!!! We will be copying the data over to these drives.
Doug Hiteshew Johnson Memorial Hospital Franklin, IN -----Original Message----- From: Ottinger, Shawn To: [email protected] Sent: 12/28/06 9:46 AM Subject: RE: [MEDITECH-L] data Repository purge I agree with the solution below. Buy more drives. You have spent money to get this information, just spend a little more to keep it. The information can be invaluable. However, Here is an idea. Most tables, if not all, have a last updated field. You could delete purge on that. This will be very crude here is why. If you try to query on any data that relies on data you have purged or moved, there is no way of knowing that you are missing information. That means (if you choose to do this) you should never purge data you may want or need. (After all the great thing about the data repository is you have all that data and it is not slowing down the system in any way). You would only consider this if you have many years of data, and never want to query past a certain number. Example - You have ten years of data, but never want to query past 5 years. In this case, you might consider purging any data that has not been modified in 7 years. (You need to keep a buffer to ensure you don't delete anything needed for a 5 year query). If you need to query more than 5 years,,,,to bad its purged. You must resort back to the "slower drives" and that would be costly. (not monetary but time. If the drives are "slower", it will take even longer to get this data.) Sooner or later, wouldn't you have to add "Slower Drives", unless you are referring to back up tapes or Optical media. You could spend some time creating complex programs or scripts to "clean data based on criteria", but what will you gain with this? It can be very costly and time consuming and you still lose data.(as far as a useful query goes) There is only two reasons I can image someone would want to purge DR for. 1. To keep from buying new hardware to store growing data. In this case, I assume you are thinking about backing it up. The crude solution above would work in this case. Back up all data to tape, optical disks or "slower drives". Then use crude scripts to delete any data you "never" want to query. You will have a backup, but I am willing to bet (without a court order) you will never resort to this data. There is also still a potential to miss data from a 5 year query. 2. To speed up queries against the DR. In this case, there could be other solutions. The deciding factor is, "how are you using DR?". If you are creating the occasional query (like us) just be patient. (We don't utilize DR to its potential at all). If you have programs or scripts running against the tables very often and they are slowing due to the growing DR, there are other options. Depending on your application, you may have to get creative. Utilize indexes, views, and stored procedures. There are many ways to create smaller subsets of data with simple queries, then more complex queries against the subsets. To summarize buy more drives and keep the data. I hope this long explanation has at least helped you think about the value of the information in DR and what you are trying to accomplish. There are probably better solutions than "purging". I hope this helps. -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Wednesday, December 27, 2006 3:45 AM To: [email protected] Subject: Re: [MEDITECH-L] data Repository purge Fariborz: I don't know of any way to purge the data repository. Given the interdependence of the tables, I would suspect it would be a pretty difficult process to do well. The question I have is what the advantage would be in moving data to slower drives? It would seem that the utilization of the data would be really hampered, both by the lower quality hardware, plus the huge increase in the complexity of writing any queries and the performance hit more complex queries would entail. My guess is that buying bigger faster drives for your SAN would be a much cheaper solution. Thomas Stephen Laxar Coordinator, Hospital Information Systems Children's Hospital Oakland 510-428-3833 [EMAIL PROTECTED] The email message (and any attachments) is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message (and any attachments). %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% %%%%%%%%%%%%%%%%%% Mon Dec 25, 2006 11:42 pm From: "Peyjam, Fariborz" < Subject: [MEDITECH-L] data Repository purge To: <[email protected]> From: "Peyjam, Fariborz" <[EMAIL PROTECTED]> Date: Fri, 22 Dec 2006 14:25:28 -0600 This is a multi-part message in MIME format. --===============0936044256== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C72607.53114362" This is a multi-part message in MIME format. ------_=_NextPart_001_01C72607.53114362 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, Who has Meditech's data repository and has addressed purging? We are on Meditech Magic 5.5. Our data repository is up to 600 GB and is on our SAN. We are looking to purge/move the older data to slower drives. Any feedback would be greatly appreciated =20 Fariborz Peyjam Senior Clinical Systems Analyst=20 Mount Sinai Hospital Chicago, IL Phone: (773) 257-5257 Fax: (773) 257-2268 email: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>=20 =20 =20 ------_=_NextPart_001_01C72607.53114362 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <html xmlns:o=3D"urn:schemas-microsoft-com:office:office" = xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" = xmlns=3D"http://www.w3.org/TR/REC-html40";> <head> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; = charset=3Dus-ascii"> <meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)"> <o:SmartTagType = namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" name=3D"State"/> <o:SmartTagType = namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" name=3D"City"/> <o:SmartTagType = namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" name=3D"PlaceType"/> <o:SmartTagType = namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" name=3D"PlaceName"/> <o:SmartTagType = namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" name=3D"place"/> <!--[if !mso]> <style> st1\:*{behavior:url(#default#ieooui) } </style> <![endif]--> <style> <!-- /* Font Definitions */ @font-face {font-family:"MS Serif"; panose-1:0 0 0 0 0 0 0 0 0 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0in; margin-bottom:.0001pt; font-size:12.0pt; font-family:"Times New Roman";} a:link, span.MsoHyperlink {color:blue; text-decoration:underline;} a:visited, span.MsoHyperlinkFollowed {color:purple; text-decoration:underline;} span.EmailStyle17 {mso-style-type:personal-compose; font-family:Arial; color:windowtext;} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.25in 1.0in 1.25in;} div.Section1 {page:Section1;} --> </style> </head> <body lang=3DEN-US link=3Dblue vlink=3Dpurple> <div class=3DSection1> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'>Hi,<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'>Who has Meditech’s data repository and has = addressed purging? We are on Meditech Magic 5.5. Our data repository is up to 600 = GB and is on our SAN. We are looking to purge/move the older data to slower = drives. Any feedback would be greatly appreciated<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'><o:p> </o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3D"MS Serif"><span = style=3D'font-size:10.0pt; font-family:"MS Serif"'>Fariborz Peyjam</span></font><o:p></o:p></p> <p class=3DMsoNormal><font size=3D2 face=3D"MS Serif"><span = style=3D'font-size:10.0pt; font-family:"MS Serif"'>Senior Clinical Systems = Analyst </span></font><o:p></o:p></p> <p class=3DMsoNormal><st1:place w:st=3D"on"><st1:PlaceName = w:st=3D"on"><font size=3D2 face=3D"MS Serif"><span style=3D'font-size:10.0pt;font-family:"MS = Serif"'>Mount Sinai</span></font></st1:PlaceName><font size=3D2 face=3D"MS = Serif"><span style=3D'font-size:10.0pt;font-family:"MS Serif"'> <st1:PlaceType = w:st=3D"on">Hospital</st1:PlaceType></span></font></st1:place><o:p></o:p >= </p> <p class=3DMsoNormal><st1:place w:st=3D"on"><st1:City w:st=3D"on"><font = size=3D2 face=3D"MS Serif"><span style=3D'font-size:10.0pt;font-family:"MS = Serif"'>Chicago</span></font></st1:City><font size=3D2 face=3D"MS Serif"><span = style=3D'font-size:10.0pt;font-family:"MS Serif"'>, <st1:State = w:st=3D"on">IL</st1:State></span></font></st1:place><o:p></o:p></p> <p class=3DMsoNormal><font size=3D2 face=3D"MS Serif"><span = style=3D'font-size:10.0pt; font-family:"MS Serif"'>Phone: (773) = 257-5257</span></font><o:p></o:p></p> <p class=3DMsoNormal><font size=3D2 face=3D"MS Serif"><span = style=3D'font-size:10.0pt; font-family:"MS Serif"'>Fax: (773) = 257-2268</span></font><o:p></o:p></p> <p class=3DMsoNormal><font size=3D2 face=3D"MS Serif"><span = style=3D'font-size:10.0pt; font-family:"MS Serif"'>email: </span></font><a = href=3D"mailto:[EMAIL PROTECTED]"><font size=3D2 face=3D"MS Serif"><span = style=3D'font-size:10.0pt;font-family:"MS = Serif"'>[EMAIL PROTECTED]</span></font></a><o:p></o:p></p> <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span = style=3D'font-size: 12.0pt'> </span><o:p></o:p></font></p> <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span = style=3D'font-size: 12.0pt'><o:p> </o:p></span></font></p> </div> </body> </html> ------_=_NextPart_001_01C72607.53114362-- --===============0936044256== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*= To subscribe or unsubscribe to the meditech-l, visit MTUsers.COM. To check the status of the meditech-l, visit MTUsers.NET. For help, email [EMAIL PROTECTED] ______________________________________ meditech-l mailing list [email protected] http://mtusers.com/mailman/listinfo/meditech-l --===============0936044256==-- ------------------------------------------------------------------------ -------- Return-Path: <"Peyjam, Fariborz" <[EMAIL PROTECTED]>> Received: from sinai.org> by cho.org; Mon, 25 Dec 2006 23:42:05 0000 Received: from smtp2.mail.cho.org ([192.168.1.39]) by smtp2a.in.cho.org with ESMTP; Mon, 25 Dec 2006 23:41:56 -0800 X-ASG-Debug-ID: 1167118905-10502-408-0 X-Barracuda-URL: http://192.168.1.39:8000/cgi-bin/mark.cgi Received: from prosonic.com (unknown [204.202.252.254]) by smtp2.mail.cho.org (Spam Firewall) with ESMTP id DCFF32000520; Mon, 25 Dec 2006 23:41:45 -0800 (PST) Received: from prosonic.iserver.net (localhost [127.0.0.1]) by prosonic.com (8.13.6.20060614/8.13.1) with ESMTP id kBQ7aWf2098520; Tue, 26 Dec 2006 07:36:54 GMT Received: from shs1s074.global.shsystem.org (66-243-23-178.focaldata.net [66.243.23.178] (may be forged)) by prosonic.com (8.13.6.20060614/8.13.1) with ESMTP id kBMKPZdr043002 for <[email protected]>; Fri, 22 Dec 2006 20:25:35 GMT Received: from shs1s017.global.shsystem.org ([10.0.2.17]) by shs1s074.global.shsystem.org with Microsoft SMTPSVC(5.0.2195.6713); Fri, 22 Dec 2006 14:25:30 -0600 X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Fri, 22 Dec 2006 14:25:28 -0600 Message-ID: <[EMAIL PROTECTED]> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: data Repository purge Thread-Index: AccmB1I0xa1w71OISLGCYwUgbP5yFA== From: "Peyjam, Fariborz" <[EMAIL PROTECTED]> To: <[email protected]> X-OriginalArrivalTime: 22 Dec 2006 20:25:30.0426 (UTC) FILETIME=[531B19A0:01C72607] X-Mailman-Approved-At: Sat, 23 Dec 2006 12:42:40 +0000 X-ASG-Orig-Subj: [MEDITECH-L] data Repository purge Subject: [MEDITECH-L] data Repository purge X-BeenThere: [email protected] X-Mailman-Version: 2.1.5 Precedence: list List-Id: Email list for Meditech users <meditech-l.MTUsers.com> List-Unsubscribe: <http://mtusers.com/mailman/listinfo/meditech-l>, <mailto:[EMAIL PROTECTED]> List-Post: <mailto:[email protected]> List-Help: <mailto:[EMAIL PROTECTED]> List-Subscribe: <http://mtusers.com/mailman/listinfo/meditech-l>, <mailto:[EMAIL PROTECTED]> Content-Type: multipart/mixed; boundary="===============0936044256==" Sender: [email protected] Errors-To: [EMAIL PROTECTED] X-Barracuda-Bayes: INNOCENT GLOBAL 0.0000 1.0000 -2.0210 INNOCENT GLOBAL 0.0000 1.0000 -2.0210 X-Virus-Scanned: by Barracuda Spam Firewall at mail.cho.org X-Barracuda-Spam-Score: -2.02 X-Barracuda-Spam-Status: No, SCORE=-2.02 using global scores of TAG_LEVEL=3.0 QUARANTINE_LEVEL=5.0 KILL_LEVEL=7.0 tests= X-Barracuda-Spam-Report: Code version 3.02, rules version 3.0.29693 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% %%%%%%%%%%%%%%%%%% =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*= To subscribe or unsubscribe to the meditech-l, visit MTUsers.COM. To check the status of the meditech-l, visit MTUsers.NET. For help, email [EMAIL PROTECTED] ______________________________________ meditech-l mailing list [email protected] http://mtusers.com/mailman/listinfo/meditech-l This email and any files transmitted with it are confidential and are intended solely for the use of the individual or entity to whom they are addressed. This communication represents the originator's personal views and opinions, which do not necessarily reflect those of Laughlin Memorial Hospital. If you are not the original recipient or the person responsible for delivering the email to the intended recipient, be advised that you have received this email in error, and that any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. If you received this email in error, please immediately notify [EMAIL PROTECTED] =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*= To subscribe or unsubscribe to the meditech-l, visit MTUsers.COM. To check the status of the meditech-l, visit MTUsers.NET. For help, email [EMAIL PROTECTED] ______________________________________ meditech-l mailing list [email protected] http://mtusers.com/mailman/listinfo/meditech-l =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*= To subscribe or unsubscribe to the meditech-l, visit MTUsers.COM. To check the status of the meditech-l, visit MTUsers.NET. For help, email [EMAIL PROTECTED] ______________________________________ meditech-l mailing list [email protected] http://mtusers.com/mailman/listinfo/meditech-l
