changing an activatin stored procedure

Hello,

After I changed the activation stored procedure of a queue, the old activation stored procedure keeps being launched by the service associated with the queue. I turned the queue off and on, but to no avail. I also checked the dynamic view sys.service_queues to make sure the proper stored procedure exists in the field activation_procedure. Do you have any idea about what might have gone wrong?

Thanks

Mugur,

Changing the associated procedure does not shut down any running instance of the previous procedure. So if an instance or the procedure is running it will continue to run until it will exit on its own. One common problem is a logic defect in the procedure that causes it to never exit, in this case you must shut it down forcibly (i.e. using KILL, see http://msdn2.microsoft.com/en-us/library/ms173730.aspx)

HTH,
~ Remus

|||Thanks a lot Remus.

changing a stored proc dataset w/parameters

Hi, I changed a report to point to another dataset. Both the old and new
data sets are stored procs with parameters. The issue I'm getting is when I
try to preview the report it is still wants the old parameters. I changed
the dataset value in the table properties and hit refreshed in the data pane.
Any suggestions.Query parameters and report parameters are two different things. When you
are creating or modifying the dataset query parameters (or in your case
stored procedure) parameters are detected and report parameters are created.
The report parameters stick around unless you delete them. In layout view,
Report Menu->Report Parameters. Click on the parameter and delete it.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Lisa" <Lisa@.discussions.microsoft.com> wrote in message
news:799D404D-0742-4B2D-B708-49F566AFA9D9@.microsoft.com...
> Hi, I changed a report to point to another dataset. Both the old and new
> data sets are stored procs with parameters. The issue I'm getting is when
> I
> try to preview the report it is still wants the old parameters. I changed
> the dataset value in the table properties and hit refreshed in the data
> pane.
> Any suggestions.

Changed Snapshot Agent Schedule, but Agent still running on old on

I recently changed my snapshot agent schedule to run 1x each night. In the
Job History (SQL Server Agent), it shows to run as scheduled. However, when
I look at the Agent History, it is recording session activity every hour.
What is going on here?
Thanks,
Buddy
Hi,
Try to stop and start SQL Agent and if doesn't work, try to create a new
profile in the Snapshot agent properties/agent profiles and click to use this
new profile avoiding the default.
Regards
"Budman" wrote:

> I recently changed my snapshot agent schedule to run 1x each night. In the
> Job History (SQL Server Agent), it shows to run as scheduled. However, when
> I look at the Agent History, it is recording session activity every hour.
> What is going on here?
> Thanks,
> Buddy

Changed (or inserted) data not transferring

We've had replication running for a while. We had some hardware
failures last week and had to restore an old database from before the
failure. Now we have some tables that are replicating correctly but
others aren't (using merge replication). We've made changes to the
data, seen the data get added or updated in msmerge_contents but when
the merge agent runs it shows no data needed to be merged.
For one table I tried sp_addtabletocontents also just to see and it
still had the same issue. We do have some row filtering on some tables
but on others we don't.
I can't say 100% yet, but for the most part it seems to be that data
from the remote server wont' replicate down to us but in some cases it
will replicate our changes up to them.
Any ideas or tips on what else to look at would be greatly appreciated.
Thanks.
Update the problem tables setting a columns' value to itself. See if this
fixes the problem.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Don" <google@.thecoles.org> wrote in message
news:1124223959.170691.79230@.o13g2000cwo.googlegro ups.com...
> We've had replication running for a while. We had some hardware
> failures last week and had to restore an old database from before the
> failure. Now we have some tables that are replicating correctly but
> others aren't (using merge replication). We've made changes to the
> data, seen the data get added or updated in msmerge_contents but when
> the merge agent runs it shows no data needed to be merged.
> For one table I tried sp_addtabletocontents also just to see and it
> still had the same issue. We do have some row filtering on some tables
> but on others we don't.
> I can't say 100% yet, but for the most part it seems to be that data
> from the remote server wont' replicate down to us but in some cases it
> will replicate our changes up to them.
> Any ideas or tips on what else to look at would be greatly appreciated.
> Thanks.
>
|||Actually we tried that earlier to no avail (that's how we did get a
couple of the tables to update but the others still didn't). We're
trying out one program so we can find the data to manually transfer and
will probably end up removing replication and starting over again. But
we're still game to any ideas for now or in the future.
Thanks.
Hilary Cotter wrote:
> Update the problem tables setting a columns' value to itself. See if this
> fixes the problem.
> --

Change W2000 Admin password, SQL serve does not authenticate

I changed myW2000 Admin password and SQL server doesn't start anymore due to
login failure. When I change it to the old password it works fine. What's
the solution? The Edit Registration Properties of my SQL server are set to
Use Windows Authentication..
Hi,
Check the SQL Server service account on Administrative Tools - Services.
If it's using administrator account that you mentioned change the password
from there as well.
(Also same for SQL Agent Service Account.)
"patrick delifer" wrote:

> I changed myW2000 Admin password and SQL server doesn't start anymore due to
> login failure. When I change it to the old password it works fine. What's
> the solution? The Edit Registration Properties of my SQL server are set to
> Use Windows Authentication..
>
>

Change W2000 Admin password, SQL serve does not authenticate

I changed myW2000 Admin password and SQL server doesn't start anymore due to
login failure. When I change it to the old password it works fine. What's
the solution? The Edit Registration Properties of my SQL server are set to
Use Windows Authentication..Hi,
Check the SQL Server service account on Administrative Tools - Services.
If it's using administrator account that you mentioned change the password
from there as well.
(Also same for SQL Agent Service Account.)
"patrick delifer" wrote:
> I changed myW2000 Admin password and SQL server doesn't start anymore due to
> login failure. When I change it to the old password it works fine. What's
> the solution? The Edit Registration Properties of my SQL server are set to
> Use Windows Authentication..
>
>

change MSDB owner

My Production's SQL2k MSDB & Model database owner is my old NT Domain
Administrator (olddomain/administrator). Can't remember how it ended that
way. Master owner is SA.
We have completed domain migration to Active Directory, if sp_changedbowner
is not going to allow me to change DB owner for MSDB & Model, does that mean
I got to keep my PDC (NT Domain) forever ?
Surely there must be a work-around for this.
Warning !!!
The following script is not a standard procedure:
[script]
use master
go
exec sp_configure 'allow updates', 1
reconfigure with override
go
update sysdatabases
set sid = 0x01
where name = 'model'
go
sp_configure 'allow updates', 0
reconfigure with override
[/script]
Cristian Lefter, SQL Server MVP
"pohkeat" <pohkeat@.hotmail.com> wrote in message
news:OYIkV$$HFHA.720@.TK2MSFTNGP10.phx.gbl...
> My Production's SQL2k MSDB & Model database owner is my old NT Domain
> Administrator (olddomain/administrator). Can't remember how it ended that
> way. Master owner is SA.
> We have completed domain migration to Active Directory, if
> sp_changedbowner
> is not going to allow me to change DB owner for MSDB & Model, does that
> mean
> I got to keep my PDC (NT Domain) forever ?
> Surely there must be a work-around for this.
>

change MSDB owner

My Production's SQL2k MSDB & Model database owner is my old NT Domain
Administrator (olddomain/administrator). Can't remember how it ended that
way. Master owner is SA.
We have completed domain migration to Active Directory, if sp_changedbowner
is not going to allow me to change DB owner for MSDB & Model, does that mean
I got to keep my PDC (NT Domain) forever ?
Surely there must be a work-around for this.Warning !!!
The following script is not a standard procedure:
[script]
use master
go
exec sp_configure 'allow updates', 1
reconfigure with override
go
update sysdatabases
set sid = 0x01
where name = 'model'
go
sp_configure 'allow updates', 0
reconfigure with override
[/script]
Cristian Lefter, SQL Server MVP
"pohkeat" <pohkeat@.hotmail.com> wrote in message
news:OYIkV$$HFHA.720@.TK2MSFTNGP10.phx.gbl...
> My Production's SQL2k MSDB & Model database owner is my old NT Domain
> Administrator (olddomain/administrator). Can't remember how it ended that
> way. Master owner is SA.
> We have completed domain migration to Active Directory, if
> sp_changedbowner
> is not going to allow me to change DB owner for MSDB & Model, does that
> mean
> I got to keep my PDC (NT Domain) forever ?
> Surely there must be a work-around for this.
>

change MSDB owner

My Production's SQL2k MSDB & Model database owner is my old NT Domain
Administrator (olddomain/administrator). Can't remember how it ended that
way. Master owner is SA.
We have completed domain migration to Active Directory, if sp_changedbowner
is not going to allow me to change DB owner for MSDB & Model, does that mean
I got to keep my PDC (NT Domain) forever ?
Surely there must be a work-around for this.Warning !!!
The following script is not a standard procedure:
[script]
use master
go
exec sp_configure 'allow updates', 1
reconfigure with override
go
update sysdatabases
set sid = 0x01
where name = 'model'
go
sp_configure 'allow updates', 0
reconfigure with override
[/script]
Cristian Lefter, SQL Server MVP
"pohkeat" <pohkeat@.hotmail.com> wrote in message
news:OYIkV$$HFHA.720@.TK2MSFTNGP10.phx.gbl...
> My Production's SQL2k MSDB & Model database owner is my old NT Domain
> Administrator (olddomain/administrator). Can't remember how it ended that
> way. Master owner is SA.
> We have completed domain migration to Active Directory, if
> sp_changedbowner
> is not going to allow me to change DB owner for MSDB & Model, does that
> mean
> I got to keep my PDC (NT Domain) forever ?
> Surely there must be a work-around for this.
>