General Advise on application

Hi ,
One small doubt want to ask .
When the application is not cluster specific & when its used on cluster
(limited to connection only) .
What the applicaion has todo to get the cluster awareness thereby it won't
loose the connectivity .
Thanks
Ajay RengunthwarHi
If a client application uses the services of a clustered SQL Server, the
application needs to be able to re-connect ot the SQL Server virtual server
name after the failover occurs, and re-submit any batches that had not
completed at the time of the failover.
Very short running transaction are even more critical in this scenario.
Running a batch that takes 30 minutes is not ideal.
Regards
Mike
"Aju" wrote:
> Hi ,
> One small doubt want to ask .
> When the application is not cluster specific & when its used on cluster
> (limited to connection only) .
> What the applicaion has todo to get the cluster awareness thereby it won't
> loose the connectivity .
> Thanks
> Ajay Rengunthwar
>
>|||You need the application to trap and handle its errors. For a Clustered SQL
Server installation, if a Failover occurs, there will be a momentary,
perhaps up to 5 or 10 minutes, as the service on one machine is brought down
and then the services on the other node are brought online. It is automated
and responsive, but there is still an outage.
Your application should get connectivity errors. Look for them, pause, and
try to reconnect. Have some logic in there to attempt a few times before
giving up.
Sincerely,
Anthony Thomas
"Aju" <ajuonline@.yahoo.com> wrote in message
news:OkCDPMq3EHA.4092@.TK2MSFTNGP14.phx.gbl...
Hi ,
One small doubt want to ask .
When the application is not cluster specific & when its used on cluster
(limited to connection only) .
What the applicaion has todo to get the cluster awareness thereby it won't
loose the connectivity .
Thanks
Ajay Rengunthwarsql

General Advise on application

Hi ,
One small doubt want to ask .
When the application is not cluster specific & when its used on cluster
(limited to connection only) .
What the applicaion has todo to get the cluster awareness thereby it won't
loose the connectivity .
Thanks
Ajay Rengunthwar
Hi
If a client application uses the services of a clustered SQL Server, the
application needs to be able to re-connect ot the SQL Server virtual server
name after the failover occurs, and re-submit any batches that had not
completed at the time of the failover.
Very short running transaction are even more critical in this scenario.
Running a batch that takes 30 minutes is not ideal.
Regards
Mike
"Aju" wrote:

> Hi ,
> One small doubt want to ask .
> When the application is not cluster specific & when its used on cluster
> (limited to connection only) .
> What the applicaion has todo to get the cluster awareness thereby it won't
> loose the connectivity .
> Thanks
> Ajay Rengunthwar
>
>
|||You need the application to trap and handle its errors. For a Clustered SQL
Server installation, if a Failover occurs, there will be a momentary,
perhaps up to 5 or 10 minutes, as the service on one machine is brought down
and then the services on the other node are brought online. It is automated
and responsive, but there is still an outage.
Your application should get connectivity errors. Look for them, pause, and
try to reconnect. Have some logic in there to attempt a few times before
giving up.
Sincerely,
Anthony Thomas

"Aju" <ajuonline@.yahoo.com> wrote in message
news:OkCDPMq3EHA.4092@.TK2MSFTNGP14.phx.gbl...
Hi ,
One small doubt want to ask .
When the application is not cluster specific & when its used on cluster
(limited to connection only) .
What the applicaion has todo to get the cluster awareness thereby it won't
loose the connectivity .
Thanks
Ajay Rengunthwar

Function is 10 times slower than SP

Hi all,

In order to return a table for a specific input parameter, I am using Function, but the performance is just awful! After I have tried same code as SP, the whole thing is running under 1 sec (like 0.5 sec), while the function is about 10 times slow (4-6 sec). I know in SQL 2000 function is slower than SP, but that cannot be as bad as 10 times slower.

Now, in order to use that table from SP, I have to create a temp table, then insert result into that temp table, before I can direct use any "select" sentence. Any explanation here? Or how to "select" from a SP directly?

Thanks,

Ning

It is very difficult for us to attempt to help you with being able to see the code.

You may wish to consider posting the procedure code and maybe someone here will help create an efficient TVF (table valued function.)

|||

As you said you have to insert the sp output to temp table to use in select statement ... you can not use sp in select statement... you are rightly mentioned that function used to be more or less slower than sp... also check whether all the parameters used in sp are used in function also...

Madhu

function call acting odd

We upgraded to SP4 last night. Prior to that upgrade, a specific function
worked fine (since 2003 as a matter of fact). Now, if I create a view using
Enterprise Manager and call this function, I get an erroneous error message
about needing to convert a data type. If I write the same query in query
analzyer, however, it works as expected. Prior views and stored procedures
that call this function continue to work as expected. Any suggestions on
what is going on here? Is this SP4 related or something else?> create a view using Enterprise Manager
I strongly recommend sticking with Query Analyzer for this kind of task. EM
is fine for look-see and administrative type tasks, but I do not think it is
the optimal tool for script or data management.
A|||Aaron,
Query Analyzer may be the better choice but the point is that EM no longer
works as it did in the past, which tells me there is a problem somewhere.
Thanks anyway.
"Aaron Bertrand [SQL Server MVP]" wrote:

> I strongly recommend sticking with Query Analyzer for this kind of task.
EM
> is fine for look-see and administrative type tasks, but I do not think it
is
> the optimal tool for script or data management.
> A
>
>|||> Query Analyzer may be the better choice but the point is that EM no longer
> works as it did in the past, which tells me there is a problem somewhere.
And if you service your Yugo, its behavior may change also. Doesn't mean
you should have ever had a Yugo in the first place. :-)

function

Hello
I use ms sql2000
If i would like to do a function
that gives me a value of "*"
if a specific field is empty
how will i do please helpThis is how it looks

two tables
Activity
Actparttime

i try whith this function

CREATE FUNCTION dbo.Actact (@.ID AS int)
RETURNS varchar(1)
AS
BEGIN
DECLARE @.Aact AS varchar(1)
SELECT DISTINCT @.Aact = "*" WHERE (SELECT dbo.Activity.ID
FROM dbo.Activity INNER JOIN
dbo.Actparttime ON dbo.Activity.ID = dbo.Actparttime.Actid
WHERE (dbo.Actparttime.Actpartend IS NULL) AND (dbo.Activity.ID = @.ID)) >""


RETURN @.Aact
END

and a view

SELECT ID, ActStart, ActEnd, Activity, dbo.Actact(ID) AS Aact
FROM dbo.Activity

i get that subquery returned more than 1 reply

please help|||another way to check:

CREATE FUNCTION dbo.IsEmpty ( @.COL sql_variant )
RETURNS varchar(1)
AS
BEGIN
DECLARE @.Ret AS varchar(1)
SELECT @.Ret = case when convert(varchar,IsNull(@.COL,''))='' then '*' else '' end
RETURN @.Ret
END
go

select dbo.sEmpty( <ColumnName> ), ...|||Thanks

But how do i do when i will have
it sorted on activity table
If there is more than one field i get an error for
many rows|||Originally posted by u31115057
Thanks

But how do i do when i will have
it sorted on activity table
If there is more than one field i get an error for
many rows

something like this ?

CREATE FUNCTION dbo.IsEmpty (
@.COL1 sql_variant ,
@.COL2 sql_variant ,
@.COL3 sql_variant ,
@.COL4 sql_variant ,
@.COL5 sql_variant
) RETURNS varchar(1)
AS BEGIN
DECLARE @.Ret AS varchar(1)
SELECT @.Ret = case when
convert(varchar,IsNull(@.COL1,''))+
convert(varchar,IsNull(@.COL2,''))+
convert(varchar,IsNull(@.COL3,''))+
convert(varchar,IsNull(@.COL4,''))+
convert(varchar,IsNull(@.COL5,''))
='' then '*' else '' end
RETURN @.Ret
END
go

AND

select dbo.IsEmpty( <colname1>, <colname2>, null, null, null ), ...

Full-Text Population Fails for Specific Table

I have a SQL Server 2000 database with the latest service pack (3?). For some time, I've had full-text indexing working. Eventually, one of my full-text catalogs failed to populate. After a rebuild, I still couldn't populate it. I dropped it and recreated several catalogs. Eventually, I was able to get all of the original tables into a full-text catalog that populates except one. The offending table has less than 4000 rows in it. It is now in its own catalog which refuses to populate. I can't find any errors in the Application Log that correspond to this catalog population failing.

I expect that since the catalog used to populate, but will no longer populate, this must have something to do with the data added to the table recently.

Do these symptoms match any known issues? What should I do to debug this issue? I'm stuck.

Please help. Thank you.

Dave McCall? Do the gatherer logs reveal anything? -- Hilary CotterDirector of Text Mining and Database StrategyRelevantNOISE.Com - Dedicated to mining blogs for business intelligence. This posting is my own and doesn't necessarily represent RelevantNoise's positions, strategies or opinions. Looking for a SQL Server replication book?http://www.nwsu.com/0974973602.html Looking for a FAQ on Indexing Services/SQL FTShttp://www.indexserverfaq.com <Dave McCall@.discussions.microsoft.com> wrote in message news:b6cf47d2-6c0a-4c82-a9f9-42f1d2b71454@.discussions.microsoft.com...I have a SQL Server 2000 database with the latest service pack (3?). For some time, I've had full-text indexing working. Eventually, one of my full-text catalogs failed to populate. After a rebuild, I still couldn't populate it. I dropped it and recreated several catalogs. Eventually, I was able to get all of the original tables into a full-text catalog that populates except one. The offending table has less than 4000 rows in it. It is now in its own catalog which refuses to populate. I can't find any errors in the Application Log that correspond to this catalog population failing.I expect that since the catalog used to populate, but will no longer populate, this must have something to do with the data added to the table recently.Do these symptoms match any known issues? What should I do to debug this issue? I'm stuck.Please help. Thank you.Dave McCall