Results 1 to 5 of 5

Thread: Critical Problem SQL Server 7.0 - Database Engine

  1. #1
    Govind Chavan, DGM Systems Guest

    Critical Problem SQL Server 7.0 - Database Engine

    We are a National Level Institutional Stock Broker in India providing trading platform to our Brokers to trade on Exchange nation-wide. We are using Compaq Proliant 8500 Serires computers in clusterd mode having RAM of 1.5 GB on each machine. We are using the Computer-To-Computer-Link (CTCL) solution / application for routing orders of brokers to the Stock Exchange. This application uses the SQL server 7.0 in clustered mode as back-end database on Windows NT Ver 4.0. On daily basis around 20,000 transactions are processed in the database.

    Following are the Database Details
    ----------------------------------
    1. Dat Size : 1890 MB
    2. Log Size : 838 MB
    ------------------
    Total Size: 2728 MB

    3. File growth options: Automated file growth, By percent : 10
    4. Maximum File Size : Unrestricted file growth

    On April 25, 2001, we found that application was not getting initialize, we (technical team) checked all the procedures, which are getting triggered at that particular time and found all of them were ok, but application did not started.

    We also suspected that one of the procedure might have been corrupted, so we re-compiled all procedures which get triggered before starting the application. After havind done so, the application was still not getting initalized / started.

    We also executed following commands:

    1. DBCC CHECKDB to check inconsistancy, if any but found none (log is available)
    2. DUMP TRAN with no_log (To clear transation logs)

    We also executed procedures one after the other sequentially, which were being executed before the application starts after binding once again.

    After having done this, we also suspected that the problem might have been with "SQL Server 7.0 database engine" and therefore decided to re-start the computers, after which we found that the applicatio started without any hindrance / errors.

    This has raised some issues as follows:

    1. Has the database corrupted ? If yes, weather it is possible to run DBCC CHECKDB, SQL queries on a corrupted database ?
    2. Was there any systems environment failure ?
    If so, is it possible to run DBCC CHECKDB, SQL queries on a corrupted
    database?
    3. Is there any possiblity of Database Engine failure?
    What can be the consequeces on Database Engine failure ?
    4. Is it possible that Database Engine Failure is the cause for our case ?

    Our some of the engineers are of the opinion that the SQL server need to be shutdown and re-started periodically.
    1. Will this in any way avoid such re-currance in the future?
    2. If this is true, we would like to have your technical feedback as to why this is necessary?

    Should you require any further clarification, I shall be glad to furnish it to you in this regard.

    I request you to give your techical feed back on an urgent basis as our applications are CRITICAL and needs UTMOST CARE, hence needs consistancy of database.

    I shall be glad to receive your feedback at
    my e-mail: gchavan@iseindia.com or (+91)(022-781 2389).

    Govind Chavan, Mumbai, INDIA

  2. #2
    Ray Miao Guest

    Critical Problem SQL Server 7.0 - Database Engine (reply)

    Database seems ok from your message. One way to test is run some queries under the db in query analyzer. Check your connection and apps.


    ------------
    Govind Chavan, DGM Systems at 4/28/01 9:38:05 AM

    We are a National Level Institutional Stock Broker in India providing trading platform to our Brokers to trade on Exchange nation-wide. We are using Compaq Proliant 8500 Serires computers in clusterd mode having RAM of 1.5 GB on each machine. We are using the Computer-To-Computer-Link (CTCL) solution / application for routing orders of brokers to the Stock Exchange. This application uses the SQL server 7.0 in clustered mode as back-end database on Windows NT Ver 4.0. On daily basis around 20,000 transactions are processed in the database.

    Following are the Database Details
    ----------------------------------
    1. Dat Size : 1890 MB
    2. Log Size : 838 MB
    ------------------
    Total Size: 2728 MB

    3. File growth options: Automated file growth, By percent : 10
    4. Maximum File Size : Unrestricted file growth

    On April 25, 2001, we found that application was not getting initialize, we (technical team) checked all the procedures, which are getting triggered at that particular time and found all of them were ok, but application did not started.

    We also suspected that one of the procedure might have been corrupted, so we re-compiled all procedures which get triggered before starting the application. After havind done so, the application was still not getting initalized / started.

    We also executed following commands:

    1. DBCC CHECKDB to check inconsistancy, if any but found none (log is available)
    2. DUMP TRAN with no_log (To clear transation logs)

    We also executed procedures one after the other sequentially, which were being executed before the application starts after binding once again.

    After having done this, we also suspected that the problem might have been with "SQL Server 7.0 database engine" and therefore decided to re-start the computers, after which we found that the applicatio started without any hindrance / errors.

    This has raised some issues as follows:

    1. Has the database corrupted ? If yes, weather it is possible to run DBCC CHECKDB, SQL queries on a corrupted database ?
    2. Was there any systems environment failure ?
    If so, is it possible to run DBCC CHECKDB, SQL queries on a corrupted
    database?
    3. Is there any possiblity of Database Engine failure?
    What can be the consequeces on Database Engine failure ?
    4. Is it possible that Database Engine Failure is the cause for our case ?

    Our some of the engineers are of the opinion that the SQL server need to be shutdown and re-started periodically.
    1. Will this in any way avoid such re-currance in the future?
    2. If this is true, we would like to have your technical feedback as to why this is necessary?

    Should you require any further clarification, I shall be glad to furnish it to you in this regard.

    I request you to give your techical feed back on an urgent basis as our applications are CRITICAL and needs UTMOST CARE, hence needs consistancy of database.

    I shall be glad to receive your feedback at
    my e-mail: gchavan@iseindia.com or (+91)(022-781 2389).

    Govind Chavan, Mumbai, INDIA

  3. #3
    MAK Guest

    Critical Problem SQL Server 7.0 - Database Engine (reply)

    Take backup of database and then run DBCC check.
    If that shows no error, then u r safe.

    There are lot of tasks that a DBA should do in order to
    ensure the data integrity and consistency. Follow the links
    in SWYNK for "Performance tuning", "Query optimization".

    restarting the server is obvious to cleanup the tempdb, and pagefile.sys

    by the way what service pack u r using (NT/SQL).

    Basically a DBA is needed!!!!!

    -MAK



    ------------
    Govind Chavan, DGM Systems at 4/28/01 9:38:05 AM

    We are a National Level Institutional Stock Broker in India providing trading platform to our Brokers to trade on Exchange nation-wide. We are using Compaq Proliant 8500 Serires computers in clusterd mode having RAM of 1.5 GB on each machine. We are using the Computer-To-Computer-Link (CTCL) solution / application for routing orders of brokers to the Stock Exchange. This application uses the SQL server 7.0 in clustered mode as back-end database on Windows NT Ver 4.0. On daily basis around 20,000 transactions are processed in the database.

    Following are the Database Details
    ----------------------------------
    1. Dat Size : 1890 MB
    2. Log Size : 838 MB
    ------------------
    Total Size: 2728 MB

    3. File growth options: Automated file growth, By percent : 10
    4. Maximum File Size : Unrestricted file growth

    On April 25, 2001, we found that application was not getting initialize, we (technical team) checked all the procedures, which are getting triggered at that particular time and found all of them were ok, but application did not started.

    We also suspected that one of the procedure might have been corrupted, so we re-compiled all procedures which get triggered before starting the application. After havind done so, the application was still not getting initalized / started.

    We also executed following commands:

    1. DBCC CHECKDB to check inconsistancy, if any but found none (log is available)
    2. DUMP TRAN with no_log (To clear transation logs)

    We also executed procedures one after the other sequentially, which were being executed before the application starts after binding once again.

    After having done this, we also suspected that the problem might have been with "SQL Server 7.0 database engine" and therefore decided to re-start the computers, after which we found that the applicatio started without any hindrance / errors.

    This has raised some issues as follows:

    1. Has the database corrupted ? If yes, weather it is possible to run DBCC CHECKDB, SQL queries on a corrupted database ?
    2. Was there any systems environment failure ?
    If so, is it possible to run DBCC CHECKDB, SQL queries on a corrupted
    database?
    3. Is there any possiblity of Database Engine failure?
    What can be the consequeces on Database Engine failure ?
    4. Is it possible that Database Engine Failure is the cause for our case ?

    Our some of the engineers are of the opinion that the SQL server need to be shutdown and re-started periodically.
    1. Will this in any way avoid such re-currance in the future?
    2. If this is true, we would like to have your technical feedback as to why this is necessary?

    Should you require any further clarification, I shall be glad to furnish it to you in this regard.

    I request you to give your techical feed back on an urgent basis as our applications are CRITICAL and needs UTMOST CARE, hence needs consistancy of database.

    I shall be glad to receive your feedback at
    my e-mail: gchavan@iseindia.com or (+91)(022-781 2389).

    Govind Chavan, Mumbai, INDIA

  4. #4
    Moorthy Guest

    Critical Problem SQL Server 7.0 - Database Engine (reply)

    This problem is purely from your application side, not on SQL Server Side.

    Our some of the engineers are of the opinion that the SQL server need to be shutdown and re-started periodically.
    @No Shutdown or Restart is required on SQL Server Side for any unknown reason.

    1. Will this in any way avoid such re-currance in the future?
    @You have to discuss with your application support group in order to finalize the issue. I personally feel this is not SQL Server Issue at all.

    2. If this is true, we would like to have your technical feedback as to why this is necessary?
    @Have a regular Backup Plan, Maintain SQL Server periodically will help SQL Server to be online. Please come to SQL Server Issue at last point in order to see any problem. which means SQL Server nevers raises any issues like the issue happened to you.

    ------------
    Govind Chavan, DGM Systems at 4/28/01 9:38:05 AM

    We are a National Level Institutional Stock Broker in India providing trading platform to our Brokers to trade on Exchange nation-wide. We are using Compaq Proliant 8500 Serires computers in clusterd mode having RAM of 1.5 GB on each machine. We are using the Computer-To-Computer-Link (CTCL) solution / application for routing orders of brokers to the Stock Exchange. This application uses the SQL server 7.0 in clustered mode as back-end database on Windows NT Ver 4.0. On daily basis around 20,000 transactions are processed in the database.

    Following are the Database Details
    ----------------------------------
    1. Dat Size : 1890 MB
    2. Log Size : 838 MB
    ------------------
    Total Size: 2728 MB

    3. File growth options: Automated file growth, By percent : 10
    4. Maximum File Size : Unrestricted file growth

    On April 25, 2001, we found that application was not getting initialize, we (technical team) checked all the procedures, which are getting triggered at that particular time and found all of them were ok, but application did not started.

    We also suspected that one of the procedure might have been corrupted, so we re-compiled all procedures which get triggered before starting the application. After havind done so, the application was still not getting initalized / started.

    We also executed following commands:

    1. DBCC CHECKDB to check inconsistancy, if any but found none (log is available)
    2. DUMP TRAN with no_log (To clear transation logs)

    We also executed procedures one after the other sequentially, which were being executed before the application starts after binding once again.

    After having done this, we also suspected that the problem might have been with "SQL Server 7.0 database engine" and therefore decided to re-start the computers, after which we found that the applicatio started without any hindrance / errors.

    This has raised some issues as follows:

    1. Has the database corrupted ? If yes, weather it is possible to run DBCC CHECKDB, SQL queries on a corrupted database ?
    2. Was there any systems environment failure ?
    If so, is it possible to run DBCC CHECKDB, SQL queries on a corrupted
    database?
    3. Is there any possiblity of Database Engine failure?
    What can be the consequeces on Database Engine failure ?
    4. Is it possible that Database Engine Failure is the cause for our case ?

    Our some of the engineers are of the opinion that the SQL server need to be shutdown and re-started periodically.
    1. Will this in any way avoid such re-currance in the future?
    2. If this is true, we would like to have your technical feedback as to why this is necessary?

    Should you require any further clarification, I shall be glad to furnish it to you in this regard.

    I request you to give your techical feed back on an urgent basis as our applications are CRITICAL and needs UTMOST CARE, hence needs consistancy of database.

    I shall be glad to receive your feedback at
    my e-mail: gchavan@iseindia.com or (+91)(022-781 2389).

    Govind Chavan, Mumbai, INDIA

  5. #5
    DAVE Guest

    Critical Problem SQL Server 7.0 - Database Engine (reply)

    I think your engineers need to give a fresh look at the application design and the way it access the database. Does it leave any kind of connections orphaned such as connection structures, login structure etc., and if so only immediate solution would be to recycle the SQL Server service and NT Hosts periodically to free up server resources to avoid starved resources.

    Good luck and let me know any questions.

    Dave


    ------------
    Moorthy at 4/29/01 3:32:53 AM

    This problem is purely from your application side, not on SQL Server Side.

    Our some of the engineers are of the opinion that the SQL server need to be shutdown and re-started periodically.
    @No Shutdown or Restart is required on SQL Server Side for any unknown reason.

    1. Will this in any way avoid such re-currance in the future?
    @You have to discuss with your application support group in order to finalize the issue. I personally feel this is not SQL Server Issue at all.

    2. If this is true, we would like to have your technical feedback as to why this is necessary?
    @Have a regular Backup Plan, Maintain SQL Server periodically will help SQL Server to be online. Please come to SQL Server Issue at last point in order to see any problem. which means SQL Server nevers raises any issues like the issue happened to you.

    ------------
    Govind Chavan, DGM Systems at 4/28/01 9:38:05 AM

    We are a National Level Institutional Stock Broker in India providing trading platform to our Brokers to trade on Exchange nation-wide. We are using Compaq Proliant 8500 Serires computers in clusterd mode having RAM of 1.5 GB on each machine. We are using the Computer-To-Computer-Link (CTCL) solution / application for routing orders of brokers to the Stock Exchange. This application uses the SQL server 7.0 in clustered mode as back-end database on Windows NT Ver 4.0. On daily basis around 20,000 transactions are processed in the database.

    Following are the Database Details
    ----------------------------------
    1. Dat Size : 1890 MB
    2. Log Size : 838 MB
    ------------------
    Total Size: 2728 MB

    3. File growth options: Automated file growth, By percent : 10
    4. Maximum File Size : Unrestricted file growth

    On April 25, 2001, we found that application was not getting initialize, we (technical team) checked all the procedures, which are getting triggered at that particular time and found all of them were ok, but application did not started.

    We also suspected that one of the procedure might have been corrupted, so we re-compiled all procedures which get triggered before starting the application. After havind done so, the application was still not getting initalized / started.

    We also executed following commands:

    1. DBCC CHECKDB to check inconsistancy, if any but found none (log is available)
    2. DUMP TRAN with no_log (To clear transation logs)

    We also executed procedures one after the other sequentially, which were being executed before the application starts after binding once again.

    After having done this, we also suspected that the problem might have been with "SQL Server 7.0 database engine" and therefore decided to re-start the computers, after which we found that the applicatio started without any hindrance / errors.

    This has raised some issues as follows:

    1. Has the database corrupted ? If yes, weather it is possible to run DBCC CHECKDB, SQL queries on a corrupted database ?
    2. Was there any systems environment failure ?
    If so, is it possible to run DBCC CHECKDB, SQL queries on a corrupted
    database?
    3. Is there any possiblity of Database Engine failure?
    What can be the consequeces on Database Engine failure ?
    4. Is it possible that Database Engine Failure is the cause for our case ?

    Our some of the engineers are of the opinion that the SQL server need to be shutdown and re-started periodically.
    1. Will this in any way avoid such re-currance in the future?
    2. If this is true, we would like to have your technical feedback as to why this is necessary?

    Should you require any further clarification, I shall be glad to furnish it to you in this regard.

    I request you to give your techical feed back on an urgent basis as our applications are CRITICAL and needs UTMOST CARE, hence needs consistancy of database.

    I shall be glad to receive your feedback at
    my e-mail: gchavan@iseindia.com or (+91)(022-781 2389).

    Govind Chavan, Mumbai, INDIA

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •