Storing and retrieving such data is one thing, presenting it is an other. If you want to present such tests in a browser, you need a format that is easy to render. You might think of storing those formulas/equations/etc... in image format. Works great, but it is quite complicated to keep the images associated with the rest of the content in a relational database.
If you don't want to edit them semantically, you can simply store the whole test as XHTLM (
nvarchar(max)
in the SQL Server database table). Why, because you have
inline SVG[
^], which is perfect for such things. You can simply author images with tools like InkScape, CorelDraw, or dedicated editors if you like, paste into the html code, and store the test with all that it needs. Still, inline SVG is not cross-browser (see table on the link above). If you need you can also use inline image (using
data UI scheme[
^]) in some cases (or both) - this is also not complerely supported by all browsers.
So your test will be self-contained in a single field of a single table row - if you can afford the supprt limitations of these methods.