RNase, back in the early 1990s, posed a serious threat to laboratories working with RNA isolation. My graduate work involved isolating RNA from the tissues of Lyme disease-infected mice and hamsters. We struggled to DEPC-treat glass and plasticware, or autoclave anything that could be autoclaved, kept tissues cold during RNA harvest and held our breaths (truly, as aerosol could be another source of ribonuclease) until PAGE proved us successful in RNA isolation.
Ribonuclease (RNase) was omnipresent and the arch rival of our work, across several species, due to its RNA destroying abilities.
Now, a July 13, 2015 publication by researchers at the University of Wisconsin-Madison provided both a catch-up for this former lab rat on modern day research with and knowledge of RNase, as well as an exciting look at what may be a real purpose for this RNA-destroying molecule: RNase has moved to clinical trials due to the discovery of it’s cytotoxicity for cancer cells.
Working with RNA can be a tricky thing…it falls apart easily, and RNases (enzymes that degrade RNA) are ubiquitous. Successfully isolating RNA and maintaining its integrity is critical, especially when sensitive downstream applications are used (e.g., RNA-Seq).
Good techniques for RNA handling are simple to employ but crucial for success. All RNA purification and handling should take place in an RNase-free, RNA-only zone of the lab. Segregating RNA work from protein and DNA purification and handling will help minimize the potential for RNase contamination and help keep your RNA intact. Only buffer and water stocks treated to be RNase-free should be kept in the RNA area of the lab, and gloves should be worn at all times to prevent accidental contamination. Tools and equipment such as pipets, tips, and centrifuges should be designated for use only in the RNA zone as well. The location of the RNA zone in the lab is also important. Keeping traffic to a minimum and moving the RNA zone away from doors, windows, and vents can also help minimize contamination.
Using an RNase inhibitorcan also help safeguard your samples from RNase degradation. These inhibitors can bind to any RNases that may have been introduced into your sample and prevent them from cutting the RNA present.
By clicking “Accept All”, you consent to the use of ALL the cookies. However you may visit Cookie Settings to provide a controlled consent.
If you are located in the EEA, the United Kingdom, or Switzerland, you can change your settings at any time by clicking Manage Cookie Consent in the footer of our website.
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".
The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.
The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Advertisement".
This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".
6 months 2 days
This cookie is set by the provider Media.net. This cookie is used to check the status whether the user has accepted the cookie consent box. It also helps in not showing the cookie consent box upon re-entry to the website.
This cookie is used to store the language preferences of a user to serve up content in that stored language the next time user visit the website.
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
This cookie is associated with Sitecore content and personalization. This cookie is used to identify the repeat visit from a single user. Sitecore will send a persistent session cookie to the web client.
This domain of this cookie is owned by Vimeo. This cookie is used by vimeo to collect tracking information. It sets a unique ID to embed videos to the website.
1 month 18 hours 24 minutes
This cookie is used to calculate unique devices accessing the website.
This cookie is installed by Google Analytics. The cookie is used to calculate visitor, session, campaign data and keep track of site usage for the site's analytics report. The cookies store information anonymously and assign a randomly generated number to identify unique visitors.
This cookie is installed by Google Analytics. The cookie is used to store information of how visitors use a website and helps in creating an analytics report of how the website is doing. The data collected including the number visitors, the source where they have come from, and the pages visted in an anonymous form.
Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.
1 year 24 days
Used by Google DoubleClick and stores information about how the user uses the website and any other advertisement before visiting the website. This is used to present users with ads that are relevant to them according to the user profile.
This cookie is set by doubleclick.net. The purpose of the cookie is to determine if the user's browser supports cookies.
5 months 27 days
This cookie is set by Youtube. Used to track the information of the embedded YouTube videos on a website.
Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
This cookies is set by Youtube and is used to track the views of embedded videos.
This is a pattern type cookie set by Google Analytics, where the pattern element on the name contains the unique identity number of the account or website it relates to. It appears to be a variation of the _gat cookie which is used to limit the amount of data recorded by Google on high traffic volume websites.