reset toolbox doesn't delete my components

Hi,

I am in the process of developing a custom component. During that time I went through many versions of my custom component, including various DLL names and signatures, different code etc.

The problem is that now I have old versions of my custom components stuck in the default settings of the toolbox. When I reset the toolbox, even if I manually deleted the old items, it appears again.

I tried to delete all the DLLs I previously copied to the SQL Server directories, and also uninstalled all the DLLs from GAC.

The result was that the new components didn't appear, and I don't have the option to choose them in the "choose items" menu, but they still appear on the toolbox.

It is not something I can't live with, but it's really annoying seeing old and irrelevant versions right in your face...

Please help :-)

I believe the toolbox enumeration is driven off the %ProgramFiles%\DTS\<ComponentType> folder, so if you delete the old versions from there and reset they should be removed from the toolbox.|||I don't have that folder... I tried deleting everything from the relevant sql server folder, but it didn't help.|||Sorry, what I meant was %ProgramFiles%\Microsoft SQL Server\90\DTS\<Component>. So to remove any Data Flow components, clean up C:\Program Files\Microsoft SQL Server\90\DTS\PipelineComponents. For Tasks, clean up C:\Program Files\Microsoft SQL Server\90\DTS\Tasks etc.|||That's what I did to begin with... it still didn't help.

Re-set identity field

Hi:

I created a small SQL Express database/ASP.net/C# application and in the learning process. Before I implement it I would like to re-set autonumber / identity field back to 1. Also, I need to start with the blank database. I am not sure how to approach that?

Can you assist?

Thanks

http://www.mssqlcity.com/FAQ/Devel/reset_identity_column.htm

Republishing a subscribed database

In a merge replication application with 100 subcribers the merge process is
generating large numbers of locks on the published db and causing
performance problems.
One suggestion was that we subscribe all external (VPN on ADSL) merge
subscribers to a subscribed copy of the database created explicitly for this
purpose, thereby reducing load on the primary db. Any comments? or has
anyone implemented a similar scheme and found it beneficial?
This is a good approach. You should try to identify where the locking is
coming from. For instance if you try to modify/manage your publications
using EM this can cause a large amount of locking. So use the procs if
possible.
Also use pull if you can. Then stagger your agents to run non-continuously
at different times.
"Tony Toker" <xyzzy@.identic.co.uk> wrote in message
news:cqbln8$dp4$1$8302bc10@.news.demon.co.uk...
> In a merge replication application with 100 subcribers the merge process
is
> generating large numbers of locks on the published db and causing
> performance problems.
> One suggestion was that we subscribe all external (VPN on ADSL) merge
> subscribers to a subscribed copy of the database created explicitly for
this
> purpose, thereby reducing load on the primary db. Any comments? or has
> anyone implemented a similar scheme and found it beneficial?
>
>

Re-Post - Process Information

Dear All,
Under Managment/Current Activity/Process Info you can see
all the users with connections to the system.
Here is the problem. A couple of users seem to have
multiple (10 or more) process ID's, all of them sleeping.
After a chat with them they said they were not in the
application, but the process was still being displayed.
My questions are then, should I be concerned, and why
aren't they closing automatically ?
Thanks
Peter> Dear All,
> Under Managment/Current Activity/Process Info you can see
> all the users with connections to the system.
> Here is the problem. A couple of users seem to have
> multiple (10 or more) process ID's, all of them sleeping.
> After a chat with them they said they were not in the
> application, but the process was still being displayed.
> My questions are then, should I be concerned, and why
> aren't they closing automatically ?
> Thanks
> Peter
--
Hi Peter,
It is possible that they are orphaned processes. Checkout this article:
INF: How to Troubleshoot Orphaned Connections in SQL Server
http://support.microsoft.com/?id=137983
Hope this helps,
Eric Crdenas
SQL Server senior support professional

Re-Post - Process Information

Dear All,
Under Managment/Current Activity/Process Info you can see
all the users with connections to the system.
Here is the problem. A couple of users seem to have
multiple (10 or more) process ID's, all of them sleeping.
After a chat with them they said they were not in the
application, but the process was still being displayed.
My questions are then, should I be concerned, and why
aren't they closing automatically ?
Thanks
Peter
> Dear All,
> Under Managment/Current Activity/Process Info you can see
> all the users with connections to the system.
> Here is the problem. A couple of users seem to have
> multiple (10 or more) process ID's, all of them sleeping.
> After a chat with them they said they were not in the
> application, but the process was still being displayed.
> My questions are then, should I be concerned, and why
> aren't they closing automatically ?
> Thanks
> Peter
Hi Peter,
It is possible that they are orphaned processes. Checkout this article:
INF: How to Troubleshoot Orphaned Connections in SQL Server
http://support.microsoft.com/?id=137983
Hope this helps,
Eric Crdenas
SQL Server senior support professional

Re-Post - Process Information

Dear All,
Under Managment/Current Activity/Process Info you can see
all the users with connections to the system.
Here is the problem. A couple of users seem to have
multiple (10 or more) process ID's, all of them sleeping.
After a chat with them they said they were not in the
application, but the process was still being displayed.
My questions are then, should I be concerned, and why
aren't they closing automatically ?
Thanks
Peter> Dear All,
> Under Managment/Current Activity/Process Info you can see
> all the users with connections to the system.
> Here is the problem. A couple of users seem to have
> multiple (10 or more) process ID's, all of them sleeping.
> After a chat with them they said they were not in the
> application, but the process was still being displayed.
> My questions are then, should I be concerned, and why
> aren't they closing automatically ?
> Thanks
> Peter
--
Hi Peter,
It is possible that they are orphaned processes. Checkout this article:
INF: How to Troubleshoot Orphaned Connections in SQL Server
http://support.microsoft.com/?id=137983
Hope this helps,
--
Eric Cárdenas
SQL Server senior support professional