Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
cjsteury2
Starting Member
14 Posts |
 Posted - 2009-09-16 : 19:56:42
|
| Where do I start?I am not a SQL admin, but am a developer of an online trading system.My SQL Database manages an ASP 2.0 web site with security authorization and transaction and tickers data using Verio Web hosting shared windows servers.Right now there are about 350 ticker symbols with 2 years of data (750 or so rows of OHLC data).The Tickers are all in 1 table with date, open, high, low and thetransactions are in another table date, exit, enter, etc.We are doing a soft launch with a dozen or two users and full scale launch in a couple weeks.(1000+?) Needless to say, I am worried for many reasons...and most of them are because I am a Novice, beginner etc. Several questions.1. I have just figured out how to run a backup and a restore process (it'sgreat).2. I run a few processes several time during the day continuously to update tickers. How do I monitor process? I have tried to setup an AJAX window that shows data as it's updated but not finished. I am using VERIO but have SQLStudio and Visual Studio 2005. (using SQL 2005)...3. How can I benchmark / test performance? I am using a shared SQL server - it makes me nervous.4. Is there a way for me to setup redundant SQL servers - whereas I can update or delete data on one and then it will synchronize itself either after I am done or in a way that both insures uptime and will allow me to conduct maintenance without effecting users (deleting or updating data)...5. How do I automate backup routines? Right now I just do a full back up every night my db is only 30 - 40 MB with 60+ in transaction logs (100 MB total or so).6. What maintenance routines do I need to be aware of?7. Help!CSPS - if you don't want me to ask you any questions, or be involved in advice,you should probably not answer any of these questions. |
|
|
GilaMonster
Master Smack Fu Yak Hacker
4507 Posts |
Posted - 2009-09-17 : 03:57:31
|
| 4) Depends. Are you looking for a setup where if one server fails another takes over or are you looking to have multiple servers that can be read from at the same time? What edition of SQL are you running and what's the budget for additional hardware and licences?5) SQL Agent jobs or SQL Agent maintenance plans. Start by reading up on both in SQL's Books online (press F1 while in Management Studio)6) Index rebuilds, backups (database and maybe log, depending on recovery model), statistics updates, database consistency checks. You also need to monitor growth and ensure that the DB isn't going to run out of space, check that jobs and backups succeed, check that backups are restorable, check the error log for any errors that may be showing upYou're running an online trading system with thousands of users and, I'm guessing, a very low downtime tolerance and you have no experienced DBA there? That's walking on thin ice. I would strongly recommend that you speak to the boss (or whoever's in charge) to hire someone with experience who knows how to fix stuff if it breaks--Gail ShawSQL Server MVP |
 |
|
|
Lumbago
Norsk Yak Master
3271 Posts |
Posted - 2009-09-17 : 04:33:45
|
| 1. Backup and restore are the single most important thing you do as a database administrator and I don't care how good your trading system is; if you're hacked or something goes wrong you'll be 100% screwed if you don't have proper backup/restore routines. Take full backups at least once a day and translog backups at least every 30 mins, and make sure to copy the backup files *to another server*. Your backups are no good on the local filesystem if your disks are fried. And make sure that you know how to do a restore!2. Impossible to say...we don't know how this update tickers process works. 3. Huuuge question...but you're right that using a shared sql server should make you nervous. You're at the mercy of every other customer on that server. Monitoring performance on a shared server hardly makes any sense, it's impossible to get any reliable results anyway. 4. This shared server really limits what you can do. 5. Does this shared server allow you access to the SQL Server Agent? If so set up jobs that do the backup for you...check out Tara's script for backup: http://weblogs.sqlteam.com/tarad/archive/2009/09/08/Backup-SQL-Server-2005-and-2008-Databases.aspx6. Follow Gilas advice... And check out Taras scripts for index reorganize/rebuild: http://weblogs.sqlteam.com/tarad/archive/2009/08/31/DefragmentingRebuilding-Indexes-in-SQL-server-2005-and-2008.aspx- Lumbago |
|
|
|
|
|
|
|
|
Help ! Take it easy on me....