Showing posts with label process. Show all posts
Showing posts with label process. Show all posts

Friday, March 30, 2012

MultiUser Testing Tool

Hello,
We are in process of rolling out our SQL Server version of our product.
During our beta testing phase we have started receiving problems in
scalability from some clients. The database starts doing a lot of blocks in
multi-user environment. This is not always very easy to replicate in-house.
We are now looking for a testing tool that will automate multi-user testing
while also providing useful information such lock chains and analysis of bad
locks (such as holding exclusive table/page locks for too long), etc when
there are blocks. Is there any testing tool that people here have used
before ? Any experiences or comments will be very useful.
Thanx, Amol.
Hi
You may want to look at the dbhammer program that comes with the resource
kit and using profiler to caputure the information. Loadrunner is a more
costly alternative. You can also use profiler to script the functions you
may want to do, if these are segmented then you can chain them together to
produce specific activities.
John
"Amol Kasbekar" <apk@.nospam.com> wrote in message
news:edbWB%23%23eEHA.3100@.TK2MSFTNGP10.phx.gbl...
> Hello,
> We are in process of rolling out our SQL Server version of our
product.
> During our beta testing phase we have started receiving problems in
> scalability from some clients. The database starts doing a lot of blocks
in
> multi-user environment. This is not always very easy to replicate
in-house.
> We are now looking for a testing tool that will automate multi-user
testing
> while also providing useful information such lock chains and analysis of
bad
> locks (such as holding exclusive table/page locks for too long), etc when
> there are blocks. Is there any testing tool that people here have used
> before ? Any experiences or comments will be very useful.
> Thanx, Amol.
>
>

MultiUser Testing Tool

Hello,
We are in process of rolling out our SQL Server version of our product.
During our beta testing phase we have started receiving problems in
scalability from some clients. The database starts doing a lot of blocks in
multi-user environment. This is not always very easy to replicate in-house.
We are now looking for a testing tool that will automate multi-user testing
while also providing useful information such lock chains and analysis of bad
locks (such as holding exclusive table/page locks for too long), etc when
there are blocks. Is there any testing tool that people here have used
before ? Any experiences or comments will be very useful.
Thanx, Amol.Hi
You may want to look at the dbhammer program that comes with the resource
kit and using profiler to caputure the information. Loadrunner is a more
costly alternative. You can also use profiler to script the functions you
may want to do, if these are segmented then you can chain them together to
produce specific activities.
John
"Amol Kasbekar" <apk@.nospam.com> wrote in message
news:edbWB%23%23eEHA.3100@.TK2MSFTNGP10.phx.gbl...
> Hello,
> We are in process of rolling out our SQL Server version of our
product.
> During our beta testing phase we have started receiving problems in
> scalability from some clients. The database starts doing a lot of blocks
in
> multi-user environment. This is not always very easy to replicate
in-house.
> We are now looking for a testing tool that will automate multi-user
testing
> while also providing useful information such lock chains and analysis of
bad
> locks (such as holding exclusive table/page locks for too long), etc when
> there are blocks. Is there any testing tool that people here have used
> before ? Any experiences or comments will be very useful.
> Thanx, Amol.
>
>

MultiUser Testing Tool

Hello,
We are in process of rolling out our SQL Server version of our product.
During our beta testing phase we have started receiving problems in
scalability from some clients. The database starts doing a lot of blocks in
multi-user environment. This is not always very easy to replicate in-house.
We are now looking for a testing tool that will automate multi-user testing
while also providing useful information such lock chains and analysis of bad
locks (such as holding exclusive table/page locks for too long), etc when
there are blocks. Is there any testing tool that people here have used
before ? Any experiences or comments will be very useful.
Thanx, Amol.Hi
You may want to look at the dbhammer program that comes with the resource
kit and using profiler to caputure the information. Loadrunner is a more
costly alternative. You can also use profiler to script the functions you
may want to do, if these are segmented then you can chain them together to
produce specific activities.
John
"Amol Kasbekar" <apk@.nospam.com> wrote in message
news:edbWB%23%23eEHA.3100@.TK2MSFTNGP10.phx.gbl...
> Hello,
> We are in process of rolling out our SQL Server version of our
product.
> During our beta testing phase we have started receiving problems in
> scalability from some clients. The database starts doing a lot of blocks
in
> multi-user environment. This is not always very easy to replicate
in-house.
> We are now looking for a testing tool that will automate multi-user
testing
> while also providing useful information such lock chains and analysis of
bad
> locks (such as holding exclusive table/page locks for too long), etc when
> there are blocks. Is there any testing tool that people here have used
> before ? Any experiences or comments will be very useful.
> Thanx, Amol.
>
>

Monday, March 19, 2012

multiple updates to table

Hello all,

I have a parallel process updating a single table from various sources using update table statements using a key column.

I'm afraid the process will fail when an update will occur to a record with the same key simultaneously.

Does anyone have a suggestion how to accomplish this? Is there a way timing the updates in queue?

Thanks.

There is no concurrent update in SQL Server, DML statement are queued and executed one by one (if they are not in a transaction). There are sure scenarios which would lead to concurrency conflicts, but this has to be handled by your frontedn application.

HTH, Jens Suessmeyer.'

http://www.sqlserver2005.de

|||

I assume you have multiple clients pumping data into a single table, right?

The next question is what you mean by key? Like an identity key? If so, that won't happen. SQL Server single threads identity key generation so that no two rows will get the same key.

Friday, March 9, 2012

Multiple SuccessValues for ExecuteProcess task?

I have an execute process task to run Red-Gate's SqlDataCompare synchronization. The normal exit code is 0 indicating successful synchronization. However, if the tables are already identical and require no synchronization the process exit code is 63 and the task fails. I do not want the task to fail if the tables are identical, but it seems I can only specify a single value in the task's SuccessValue property. I tried separating values with a comma, e.g. 0,63. Any suggestions?

You could use the ForceExecutionResult property to ensure the task succeeds.

Donald

|||Thanks Donald. I was avoiding having to force the result since I want the task to fail if the exit code is other than 0 or 63. Do you think in a future version we might be able to specify multiple success values? (I entered it in connect.microsoft.com/SQLServer/Feedback).