September 9, 2007 at 1:54 pm
Hello
Soon i would need to set up a production server. I am currently handling our internal SQL Server database and somewhat familiar with backup and recovery of the user and system dbs. The next one is for one of our customers and i am sure i would need to be more alert on it. I have only about a month of experience with Sql Server and am a oracel dba primarily, handed down the responsibility of SQL Server. I donot want to let my manager / organization down. That is why i am seeking help from you experts. In the light of this i have the following questions.
1. Are there any db parameters for configuring # of processes for the db, simultaneous sessions per user, idle_time for a session etc.
2. I am learning to configure devices for backup and have done it for disk. For Legato how do i interface. Has anyone done this previously and if so would appreciate for feedback if any.
3. Is there a way for me to set upper limit for the memory consumption (like the SGA in oracle) so that the i know in advance if the peak load increases.
4. Does setting up replication require any special care to be taken note of?
5. Is the equivalent of standby database of oracle available on SQL Server?
6. For 4 & 5 , how do i catch any errors that might appear in error log and page me.
As in any other case, i am googling as well. But to get detail from someone who has hands on experience would be more reliable.
Thanks in Advance.
September 11, 2007 at 9:15 am
Would appreciate if someone can answer my questions. Thanks
September 11, 2007 at 2:29 pm
Hello
1. Are there any db parameters for configuring # of processes for the db, simultaneous sessions per user, idle_time for a session etc.
->So far I know this is a global setting, not per user.
3. Is there a way for me to set upper limit for the memory consumption (like the SGA in oracle) so that the i know in advance if the peak load increases.
You can set the maximum memory of the server and are required to if you plan to use more than 3gb. See AWE configuration
4. Does setting up replication require any special care to be taken note of?
It is quite simple to set up. Replicated tables require a primary key. I had issues with a timeout (reducing batchsize helped) and with schema-modifications. Not quite an expert in replication.
5. Is the equivalent of standby database of oracle available on SQL Server?
The easiest standby configuration is with logshipping. There is also SQL Clustering (quite difficult?). Since sql 2005 there is datamirroring.
6. For 4 & 5 , how do i catch any errors that might appear in error log and page me.
If you open up enterprise manager and start sql server agent, you can set up alerts (email,paging,net send), operators and scheduled jobs.
The books online that come with sql server are a great help.
September 12, 2007 at 8:00 am
4. I depends on the type of replication you are going to use. There are 3 types:
Snapshot
Merge
Transactional
Each have requirements you must consider when considering what will work best.
If you just want to refresh everything each time a few times a day and don't have a lot of data then snapshot will generally work.
If you need to support multiple servers joining the data together at a central server then Merge will be a good choice, this will require the adding of a guid column to each table in most cases. Or you could possibly use transactional as long as you have some other mechanism to manage conflicts in key data coming from each server.
Transactional replication requires the table to have a primary key define in order to publish and can puh as close to realtime as possible.
And of course you can also do a combination of any of the three as your needs determine.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply