Keeping a Database Server Healthy

wizardzz

Rate me:

0.00/5 (No votes)

5 Apr 2011CPOL

5.1K

I would definitely include some security measures in here as they can compromise the data being stored. Though the system may remain up after a breach, it will be too late to prevent damage once it's done:16. By all means necessary, take measures against SQL injections. This is probably a...

I would definitely include some security measures in here as they can compromise the data being stored. Though the system may remain up after a breach, it will be too late to prevent damage once it's done:

16. By all means necessary, take measures against SQL injections. This is probably a topic of an entire article.
17. Never, never store passwords as plain text, hash them with salt.

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Written By

wizardzz

Chief Technology Officer

United States

What I get paid or have been paid to do:
Sports data (NBA, NCAA)
Restaurant data - menus, locations, sales history, foot traffic, dwell time.
IOT - logistics and mining
Trading software and protocols (QuickFIX, Onix, etc).
Price feed development.
Trader simulation tools.
Back office, end of day reporting, NFA compliance.
Performance testing, optimization, and analysis.
Large scale data management, analysis, and visualization.
Worked with most major banks, some electronic exchanges, many data providors, and a few counter-parties:
MISO, PJM, NYISO, NEISO, CAISO, AESO, ERCOT, BOE, CME, CBOE, Eurex, ICE, Morgan Stanley, J.P. Morgan, RBS, EBS, Credit Suisse, Nomura, Barclays, Deutsche Bank, Citibank, UBS, Goldman Sachs, Bear Stearns (defunct), Triaina, Bloomberg
Experience in FX, energies, futures.

Keeping a Database Server Healthy

License

Comments and Discussions