No I'm talking about the code of your procs.

EDITED

N/m I just reread your code and if the layout is like this then you shouldn't be getting the error message. ...

You're supposed to get the warning only in the first create of my script. This shows why you get the error (a needs b and b is no created...

Prasad already gave you the answer. Just create the called procs first and then the master one last and you'll be fine.

run this script to recreate your situation

create proc...

Here's a nice variation that is set based :

CREATE PROCEDURE [dbo].[SPNVisitesEffacerOrdreAffichage] @FkTech as smallint, @Items as varchar(7998)

AS

SET NOCOUNT ON

DELETE FROM dbo.VisitesClientsOrdreAffichageParTech

WHERE FkTech = @FkTech

--delete all items all...

I agree with everyone's comment about GOTO. I never use GOTO unless I need to have an common exit because of err handling. You just don't need a...

it means you can't put a trigger on that table (on any system table for that matter).

You'll have to do snapshots of the table an extract the data from there.

In my test case I was searching for the word "test" hence the criteria "te*". The only solution I see for this problem would be to chop the last...

I guess I'm not understanding your requirements because I don't see how this could not work for you. Can you send me some sample data from the data, the...

Just use it like this :

Declare @search as varchar(50)

set @search = '"te*"'

Select *

FROM dbo.Problemes

WHERE CONTAINS(TitreProbleme, @search)

Tell your users that * is the wildcard (can't be used on the front...

The only other possibility I can think of is that you have one connection from earlier runs of the page and that wasn't closed then... Maybe you could try...

Just to complete, it is used to encrypt data. I think sql uses it mostly to encrypt the passwords, but we can use it as well.

Maybe it's just a carriage return. Can you post the whole query so we can check it out?

I'm no expert in permission so if I'm wrong please jump in and save my ass .

I think he must be the owner of...

This syntaxe seems to accomplish what you ar trying to do :

Select *

FROM dbo.Problemes

WHERE CONTAINS(TitreProbleme, ' "te*" ')

I'm shooting in the dark here... but have you tried destroying the connection object before running sp_who2?

Maybe that the connection is still there, but simply sleeping untill you actually run...