Enterprise Manager

We have inherited a system with a Sybase DB and have been
asked to move it to SQL 7. We have converted the data and
the database with expected datatype problems and it seems
to be working. The application is a PowerBuilder 7
program that was using and ODBC and is now using OLE DB
for the SQL. In a one man environment it is great, move
it to the production machine and tell all 47 folks to sign
on, the Enterprise Manager quits responding, tables lock
all over the place and no one can do updates or inserts.
The tables have PK and FK with clustered indexes pretty
thoroughly placed. The machine is a NT 4.0 with 1GB of
RAM with a raid drive 20GB.
Any suggestions on what to do to increase performance on
this one?
TIA,
camiHello Cami !
First of all you must find out who is holding locks and what objects,
respectiv what actions are holding locks on the tables.
Jens Süßmeyer.
"Cami" <clawson@.informs.com> schrieb im Newsbeitrag
news:029801c36688$a4567220$a401280a@.phx.gbl...
> We have inherited a system with a Sybase DB and have been
> asked to move it to SQL 7. We have converted the data and
> the database with expected datatype problems and it seems
> to be working. The application is a PowerBuilder 7
> program that was using and ODBC and is now using OLE DB
> for the SQL. In a one man environment it is great, move
> it to the production machine and tell all 47 folks to sign
> on, the Enterprise Manager quits responding, tables lock
> all over the place and no one can do updates or inserts.
> The tables have PK and FK with clustered indexes pretty
> thoroughly placed. The machine is a NT 4.0 with 1GB of
> RAM with a raid drive 20GB.
> Any suggestions on what to do to increase performance on
> this one?
> TIA,
> cami
>|||Jens,
We have located the tables but it happens randomly on different tables and the most frustrating thing is the Enterprise Manager just dying while I'm trying to watch who is doing what and what is locking. I can do all of that in the QueryAnalyzer but what is locking up the EM?
tia,
cami
>--Original Message--
>Hello Cami !
>First of all you must find out who is holding locks and what objects,
>respectiv what actions are holding locks on the tables.
>Jens S=FC=DFmeyer.
>
>"Cami" <clawson@.informs.com> schrieb im Newsbeitrag
>news:029801c36688$a4567220$a401280a@.phx.gbl...
>> We have inherited a system with a Sybase DB and have been
>> asked to move it to SQL 7. We have converted the data and
>> the database with expected datatype problems and it seems
>> to be working. The application is a PowerBuilder 7
>> program that was using and ODBC and is now using OLE DB
>> for the SQL. In a one man environment it is great, move
>> it to the production machine and tell all 47 folks to sign
>> on, the Enterprise Manager quits responding, tables lock
>> all over the place and no one can do updates or inserts.
>> The tables have PK and FK with clustered indexes pretty
>> thoroughly placed. The machine is a NT 4.0 with 1GB of
>> RAM with a raid drive 20GB.
>> Any suggestions on what to do to increase performance on
>> this one?
>> TIA,
>> cami
>
>.
>|||I foresee running SQL profiler in your future. You will want to see if you
are having deadlocks and who/what is blocking who/what.
Here are a couple useful links
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/acdata/ac_8_con_7a_3xrf.asp -
Detecting and Ending Deadlocks
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_mon_perf_00mr.asp -
Monitoring Server Performance and Activity
http://www.microsoft.com/technet/treeview/default.asp?url=/technet/itcommunity/chats/trans/sql/sql1023.asp -
Performance Monitoring for the SQL Server Professional Chat
HTH
--
Ray Higdon MCSE, MCDBA, CCNA
--
"Cami" <clawson@.informs.com> wrote in message
news:029801c36688$a4567220$a401280a@.phx.gbl...
> We have inherited a system with a Sybase DB and have been
> asked to move it to SQL 7. We have converted the data and
> the database with expected datatype problems and it seems
> to be working. The application is a PowerBuilder 7
> program that was using and ODBC and is now using OLE DB
> for the SQL. In a one man environment it is great, move
> it to the production machine and tell all 47 folks to sign
> on, the Enterprise Manager quits responding, tables lock
> all over the place and no one can do updates or inserts.
> The tables have PK and FK with clustered indexes pretty
> thoroughly placed. The machine is a NT 4.0 with 1GB of
> RAM with a raid drive 20GB.
> Any suggestions on what to do to increase performance on
> this one?
> TIA,
> cami
>