Microsoft SQL Server Database Administration (DBA) services to keep your data protected and recoverable in the event of a disaster. We regularly perform query tuning and analysis to keep our client's SQL Servers in tune. Our specialty is companies large enough to run their business on SQL Server, but not big enough to justify a full time DBA. Our certified team will provide only the fraction of a DBA that is needed, lowering your cost. Since we also have large clients, you can be sure that we will find the needs of a smaller company very easy.We enjoy helping small companies who do not have a SQL Server DBA and depend on the general network engineer or a developer to take care of the SQL Server. When they suffer an unfortunate data catastrophe because the backups were not restore-tested regularly and data gets lost, then we kick into action to attempt to recover whatever data from whatever backups they may still have. Most importantly, we setup a disaster recovery strategy that is much more 'industrial strength' before walking out.Also, when a SQL Server grows slower and slower, we enjoy tuning the system to increase its speed and resource usage. Tuning is not a simple 'wave of the wand'. It is an ongoing process. Typically, it starts with a detailed analysis using some of our proprietary tools and some 3rd party tools (see http://www.sqlwatchmen.com for more details) to assess what the biggest bottleneck is on the system. Once we identify if it is CPU, memory, disk IO, poor SQL code, etc., then we can make adjustments to relieve the bottleneck. But many of these adjustments can not be applied during business hours with users pounding the system. So we schedule these changes for the evening, and monitor closely.Once that bottleneck is out of the way, we need to start the process all over again. As the performance increases, so does the user load. So tuning really is a continual process.

We're always looking for investments which are passive in nature. Businesses, Real Estate, Paper Assets, etc.

Our developers create custom software solutions using C#, MVC, Bootstrap, SQL Server and other technologies.

Reviewed security footprint, both externally (forward/public facing) and internally (attacks from employees). Used various tools to perform full security analysis and report to management the exposure, as well as assist and direct the IT network staff to implement the necessary changes.Also performed penetration tests by 'hacking' in, but acting as a competitor to attempt to collect the source code of the core bread-n-butter solutions, as well as acting as a typical developer and using a developers account and knowledge of the network, to escalate privileges to become a domain administrator. Both were successful and performed over one weekend and I provided full reports and discussed the details with executive level management as to how it was performed.Provided education as to the principle of least privilege, the development team not using the 'sa' SQL Server account (or even knowing the password), and especially to not deploy applications which use the 'sa' SQL account. Helped formulate other security policies as well.Also performed many development tasks, created code (.asp) and COM objects written in VB6, stored procedures, triggers, SQL Functions, Views, etc. Using SQL Server 7.0 and 2000. Company didn't have any DBA staff, so I encouraged executives to open a position and explained importance of this role. Instead, they had me cover the basics (backups, dbcc checkdb, reindex, restats, email notifications, etc.)

Test Engineer II. Traded my management title for a dark room, candy bars and soda. Spent my days and nights writing SQL 6.0 code and Borland Delphi/CBuilder projects. The job itself was writing software systems to operate the tests/burn-in process that all computers underwent on the production line. At the time, PBNEC was #1 in sales, beating out Dell, HP, etc. As I got deeper into SQL Server, I had to justify why my code wasn't running very fast in production even though 'it works on my computer'. This lead me to accidentally learn about SQL DBA and performance tuning in SQL 6.0. Then I was move involved in DBA with SQL 6.5.Software Engineering Manager leading 13 employees. Wrote software utilities in Pascal 7.0.2 and other versions. Worked with SQL Server 6.0 and discovered what a 'set based operation' was. Became very excited about SQL Server and transferred to the Test Engineering department where there was an opening doing SQL/Delphi development.MIS Help Desk Supervisor.Gazed my eyes upon a coworker's CRT who was running SQL Server 4.2 on SQLNT (not OS/2). This was in 1993. He was excited about his SELECT statement and I was unimpressed since I failed to grasp what a 'set' was. I figured SQL had to go row by row, just like in DBASE III+, Paradox, Clipper, etc. I'm glad he was excited since it wasn't until the mid/late 90's that I revisited SQL Server once again when it was in version 6.0 and I fell in love. This is when I told my wife that I was "going to take over the world with databases - one database at a time."Started in Technical Support department as a lead support rep (a support rep who answered advanced questions from the front-line technicians). Also worked as an escalation tech for irate customers or when the technical nature of the issue was too involved to be brokered by a front-line technician. Also wrote software in DBASE, Alpha III and other similar technologies.