Connection Management

Hi:

I have a Point-of-sale application that uses SQL Server2000 for the backend.
Basically, the users perform various functions boiling down to login (check
password from a table) and data entry (insert a food entry). Previously, I
would open a new ADO 2.7 connection to the database each time one of these
types of database accessing functions needed to be performed - but I noticed
that sometimes the DB would freeze the application for 20 seconds or so - or
even cause a timeout error.

To fix this, I open a DB connection when the application first starts,
keeping it open for the life of the application - each time a function needs
to access the DB, it just uses the applications (global) connection that is
constantly open and connected.

This seems to have fixed the problem, however, I am curious, is this an OK
way to handle the connections - keeping in mind that there are four separate
stations - each running the application - at the same time. Therefore, I
have 4 constantly open connections at the same time.

Thanks and regards,

Ryan Kennedy"Ryan P. Kennedy" <ryanp.kennedy@.verizon.net> wrote in message
news:lYnBb.4549$UM4.1037@.nwrdny01.gnilink.net...
> Hi:
> I have a Point-of-sale application that uses SQL Server2000 for the
backend.
> Basically, the users perform various functions boiling down to login
(check
> password from a table) and data entry (insert a food entry). Previously,
I
> would open a new ADO 2.7 connection to the database each time one of these
> types of database accessing functions needed to be performed - but I
noticed
> that sometimes the DB would freeze the application for 20 seconds or so -
or
> even cause a timeout error.
> To fix this, I open a DB connection when the application first starts,
> keeping it open for the life of the application - each time a function
needs
> to access the DB, it just uses the applications (global) connection that
is
> constantly open and connected.
> This seems to have fixed the problem, however, I am curious, is this an OK
> way to handle the connections - keeping in mind that there are four
separate
> stations - each running the application - at the same time. Therefore, I
> have 4 constantly open connections at the same time.
>
> Thanks and regards,
> Ryan Kennedy

I don't know much about ADO, but it sounds like you're describing a form of
connection pooling, which is certainly a very common way to manage
connections from multiple clients.

Simon|||"Ryan P. Kennedy" <ryanp.kennedy@.verizon.net> wrote in message
news:lYnBb.4549$UM4.1037@.nwrdny01.gnilink.net...
> Hi:
> I have a Point-of-sale application that uses SQL Server2000 for the
backend.
> Basically, the users perform various functions boiling down to login
(check
> password from a table) and data entry (insert a food entry). Previously,
I
> would open a new ADO 2.7 connection to the database each time one of these
> types of database accessing functions needed to be performed - but I
noticed
> that sometimes the DB would freeze the application for 20 seconds or so -
or
> even cause a timeout error.
> To fix this, I open a DB connection when the application first starts,
> keeping it open for the life of the application - each time a function
needs
> to access the DB, it just uses the applications (global) connection that
is
> constantly open and connected.
> This seems to have fixed the problem, however, I am curious, is this an OK
> way to handle the connections - keeping in mind that there are four
separate
> stations - each running the application - at the same time. Therefore, I
> have 4 constantly open connections at the same time.

Connection pooling, the sharing of a single connection among components of
an application, is very common and a good design principle. It is
particularly great for web based/ASP applications, in order to conserve
resource. Persistant connections, keeping a connection open even when not in
use, is something I shy away from in my client server and my web based app
designs. I prefer to create a connection, pool it, and then open and close
it as needed.

It sounds like you are looking for a solution to a symptom, and not your
problem. If I were you, I would investigate the reason your app is timing
out and solve that.

--
BV.
WebPorgmaster - www.IHeartMyPond.com
Work at Home, Save the Environment - www.amothersdream.com

connection from windows mobile 5.0

Hi,
I have written some software for a windows mobile 5.0 device that
connects to a sql server directly and performs various operations
against a database.
Under sql server 2000 and XP, I had no problems doing this using
ActiveSync and/or via wireless tcp connections with a vpn connection
to the desktop.
However, since I switched to MS Vista and SQL Server 2005 (Developers
Edition), I can only connect while using Mobile Device Center
(ActiveSync).
What's confusing to me is that when I am connected wirelessly using a
VPN connection to the Vista machine, I'm on the same subnet as the
desktop/SQL Server. While using ActiveSync (MDC), I'm on a completely
different subnet. SQL Server connections function fine through
ActiveSync, but not over the VPN.
How do I configure SQL Server to allow these wireless/vpn connections?
Is this even a SQL Server setting?
Thanks for any and all help.
Charlie
Ok. I figured it out. My device is not resolving the host name
correctly. I configured the connection string to use the IP address
and it connects fine.
Thanks,
Charlie

connection from windows mobile 5.0

Hi,
I have written some software for a windows mobile 5.0 device that
connects to a sql server directly and performs various operations
against a database.
Under sql server 2000 and XP, I had no problems doing this using
ActiveSync and/or via wireless tcp connections with a vpn connection
to the desktop.
However, since I switched to MS Vista and SQL Server 2005 (Developers
Edition), I can only connect while using Mobile Device Center
(ActiveSync).
What's confusing to me is that when I am connected wirelessly using a
VPN connection to the Vista machine, I'm on the same subnet as the
desktop/SQL Server. While using ActiveSync (MDC), I'm on a completely
different subnet. SQL Server connections function fine through
ActiveSync, but not over the VPN.
How do I configure SQL Server to allow these wireless/vpn connections?
Is this even a SQL Server setting?
Thanks for any and all help.
CharlieOk. I figured it out. My device is not resolving the host name
correctly. I configured the connection string to use the IP address
and it connects fine.
Thanks,
Charlie

Connection fails SQL 2000

One of our customers has SQl server 2000 installed
This has been working perfectly untill last Friday.
At this point various databases began to return errors
when querries were run on the data.
There appeasr to be no pattern to which databases still
work as I have two backup copies of the main databse they
use. The main one and one of the backups produce errors
yet the other backup, taken on the same day does not.
Looking at the error log (attached) there seems to be a
lot of "corrupt" entires.
Any suggestions
Date Source Message
---
--
---
--...
004 DC771 Module(sqlservr+000DC771) (ExecuteSql
(class CParamExchange *,class CXVariant *,
004 A9DE2 Module(sqlservr+000A9DE2)
(CXteHashMatch::ExecCompile(class CExecCompContext *)
004 A9E93 Module(sqlservr+000A9E93)
(CXteHashMatch::ExecCompile(class CExecCompContext *)
004 A70B6 Module(sqlservr+000A70B6)
(CXteHashMatch::IntermediateCompile(class IMemObj *,c
004 A8B35 Module(sqlservr+000A8B35)
(CXteHashMatch::CreateBailoutPlan(class CRemapContext
0041 F796 Module(sqlservr+0001F796)
(CSQLObject::FTransform(class CParamExchange *)+00000
0041 FDDD Module(sqlservr+0001FDDD)
(CSQLObject::FTransform2(class CSQLComment *,class CP
00415080 Module(sqlservr+00015080)
(CSQLSource::FTransform(class CParamExchange *)
+0000037C)
0041534 F Module(sqlservr+0001534F)
(CSQLSource::Execute(class CParamExchange *)+00000176
00415410 Module(sqlservr+00015410)
(CSQLSource::Execute(class CParamExchange *)
+00000343)
00415765 Module(sqlservr+00015765)
(CMsqlExecContext::Execute(class CCompPlan *,class
CParamExchange *)+000001C7)
004160 DB Module(sqlservr+000160DB)
(CMsqlExecContext::ExecuteStmts(class ExecutionContex
0041767 E Module(sqlservr+0001767E) (process_commands
(struct srv_proc *)+000001E7)
0043 B7EF Module(sqlservr+0003B7EF) (execute_rpc
(struct srv_proc *)+00000019)
00447078 Module(sqlservr+00047078)
(CCompPlan::FCompileStep(class CAlgStmt *,class
CStatement * *)+00000AE7)
004510 FE Module(sqlservr+000510FE)
(CProchdr::FCompile(class CCompPlan *,class CParamExc
0049 CB9F Module(sqlservr+0009CB9F)
(CStmtExec::XretExecute(class CMsqlExecContext *)cons
0049 CD0A Module(sqlservr+0009CD0A)
(CStmtExec::XretLocalExec(class CMsqlExecContext *,un
0049 C6F4 Module(sqlservr+0009C6F4)
(CSQLObject::FGetFromDisk(class CParamExchange *)+000
0049 DA48 Module(sqlservr+0009DA48)
(CStmtSelect::Init(class CAlgStmt *,class CCompPlan *
00563 F78 Module(sqlservr+00163F78)
(CStmtQuery::InitQuery(class CAlgStmt *,class CCompPl
00564019 Module(sqlservr+00164019)
(BuildQueryFromTree(class TREE *,class IMemObj
*,class IMemObj *,class IQueryOb
005642 CD Module(sqlservr+001642CD)
(CCvtTree::PqryFromTree(class TREE *,class IMemObj *,
0056701 F Module(sqlservr+0016701F)
(CBndOutputs::RemapValrefs(class CRemapContext *,int)
00567536 Module(sqlservr+00167536)
(CXte::ExecCompile(class CExecCompContext *)
+000000B7)
00567536 Module(sqlservr+00167536)
(CXte::ExecCompile(class CExecCompContext *)
+000000B7)
005688 A4 Module(sqlservr+001688A4) (CQuery::Prepare
(void)+00000116)
0061 DDB6 Module(sqlservr+0021DDB6)
(CSpecProc::Execute(class CParamExchange *)+00000092)
0061 DA3E Module(sqlservr+0021DA3E)
(CSpecProc::ExecuteSpecial(class CParamExchange *,uns
0063 C71D Module(sqlservr+0023C71D) (execrpc(struct
srv_proc *)+000004A8)
00703 A1C Module(sqlservr+00303A1C)
(CXteHashMatch::CreateInputScan(class IMemObj *,class
2003-11-05 12:36:10.29 server Microsoft SQL Server
2000 - 8.00.194 (Intel X86) ...
2003-11-05 12:36:10.54 server Logging SQL Server
messages in file 'd:\Program Files\Microsoft SQL
Server\MSSQ
2003-11-05 12:36:10.54 server Server Process ID is 1700.
2003-11-05 12:36:10.54 server All rights reserved.
2003-11-05 12:36:10.54 server Copyright (C) 1988-2000
Microsoft Corporation.
2003-11-05 12:36:10.99 server SQL Server is starting at
priority class 'normal'(4 CPUs detected).
2003-11-05 12:36:13.00 server SQL Server configured for
thread mode processing.
2003-11-05 12:36:13.23 server Using dynamic lock
allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks.
2003-11-05 12:36:13.62 server Attempting to initialize
Distributed Transaction Coordinator.
2003-11-05 12:36:19.92 spid2 Starting up
database 'master'.
2003-11-05 12:36:27.70 spid5 Starting up
database 'model'.
2003-11-05 12:36:27.70 server Using 'SSNETLIB.DLL'
version '8.0.194'.
2003-11-05 12:36:27.73 spid2 Server name is 'WRLW2S002'.
2003-11-05 12:36:27.79 spid12 Starting up
database 'powerway'.
2003-11-05 12:36:27.79 spid11 Starting up
database 'dbWheelset_Live'.
2003-11-05 12:36:27.79 spid10 Starting up
database 'Northwind'.
2003-11-05 12:36:27.79 spid9 Starting up
database 'pubs'.
2003-11-05 12:36:27.79 spid8 Starting up
database 'msdb'.
2003-11-05 12:36:27.81 spid14 Starting up
database 'dbWheelSets_LIVE'.
2003-11-05 12:36:27.81 spid13 Starting up
database 'dbWheelSets_TEST'.
2003-11-05 12:36:27.89 spid16 Starting up
database 'dbWheelsets_ARCH_TEST'.
2003-11-05 12:36:27.89 spid15 Starting up
database 'dbWheelsets_BACKUP'.
2003-11-05 12:36:27.98 spid17 Starting up
database 'dbWheelsets_DATA_TEST'.
2003-11-05 12:36:28.43 spid5 Clearing tempdb database.
2003-11-05 12:36:28.51 spid11 Analysis of
database 'dbWheelset_Live' (7) is 100% complete
(approximately 0 mo
2003-11-05 12:36:28.65 spid12 Analysis of
database 'powerway' (8) is 100% complete (approximately 0
more seco
2003-11-05 12:36:28.87 server SQL Server is ready for
client connections
2003-11-05 12:36:28.87 server SQL server listening on
172.20.120.23:1433, 127.0.0.1:1433.
2003-11-05 12:36:28.87 server SQL server listening on
TCP, Shared Memory, Named Pipes.
2003-11-05 12:36:29.76 spid13 Analysis of
database 'dbWheelSets_TEST' (9) is 100% complete
(approximately 0 m
2003-11-05 12:36:38.67 spid5 Starting up
database 'tempdb'.
2003-11-05 12:36:41.85 spid2 Recovery complete.
2003-11-05 12:36:49.51 spid51 Using 'xpsqlbot.dll'
version '2000.80.194' to execute extended stored procedure
2003-11-05 12:36:51.96 spid51 Using 'xpstar.dll'
version '2000.80.194' to execute extended stored
procedure '
2003-11-05 13:15:27.45 spid55 Using 'sqlimage.dll'
version '4.0.5'...
2003-11-05 13:15:27.46 spid55 SqlDumpExceptionHandler:
Process 55 generated fatal exception c0000005 EXCEPTIO
2003-11-05 13:15:27.46 spid55 Error: 0, Severity: 19,
State: 0
410735 D0 Module(UMS+000035D0) (ProcessWorkRequests
(class UmsWorkQueue *)+00000264)
4107382 C Module(UMS+0000382C) (ThreadStartRoutine
(void *)+000000BC)
7 C57B382 Module(KERNEL32+0000B382)
(lstrcmpiW+000000B7)
78008454 Module(MSVCRT+00008454)
(_endthread+000000C1)Have you tried running DBCC CHECKDB
--
HTH
Ryan Waight, MCDBA, MCSE
"john kinghorn" <anonymous@.discussions.microsoft.com> wrote in message
news:076a01c3a787$7e28ea20$a401280a@.phx.gbl...
> One of our customers has SQl server 2000 installed
> This has been working perfectly untill last Friday.
> At this point various databases began to return errors
> when querries were run on the data.
> There appeasr to be no pattern to which databases still
> work as I have two backup copies of the main databse they
> use. The main one and one of the backups produce errors
> yet the other backup, taken on the same day does not.
> Looking at the error log (attached) there seems to be a
> lot of "corrupt" entires.
> Any suggestions
>
> Date Source Message
> ---
> --
> ---
> --...
> 004 DC771 Module(sqlservr+000DC771) (ExecuteSql
> (class CParamExchange *,class CXVariant *,
> 004 A9DE2 Module(sqlservr+000A9DE2)
> (CXteHashMatch::ExecCompile(class CExecCompContext *)
> 004 A9E93 Module(sqlservr+000A9E93)
> (CXteHashMatch::ExecCompile(class CExecCompContext *)
> 004 A70B6 Module(sqlservr+000A70B6)
> (CXteHashMatch::IntermediateCompile(class IMemObj *,c
> 004 A8B35 Module(sqlservr+000A8B35)
> (CXteHashMatch::CreateBailoutPlan(class CRemapContext
> 0041 F796 Module(sqlservr+0001F796)
> (CSQLObject::FTransform(class CParamExchange *)+00000
> 0041 FDDD Module(sqlservr+0001FDDD)
> (CSQLObject::FTransform2(class CSQLComment *,class CP
> 00415080 Module(sqlservr+00015080)
> (CSQLSource::FTransform(class CParamExchange *)
> +0000037C)
> 0041534 F Module(sqlservr+0001534F)
> (CSQLSource::Execute(class CParamExchange *)+00000176
> 00415410 Module(sqlservr+00015410)
> (CSQLSource::Execute(class CParamExchange *)
> +00000343)
> 00415765 Module(sqlservr+00015765)
> (CMsqlExecContext::Execute(class CCompPlan *,class
> CParamExchange *)+000001C7)
> 004160 DB Module(sqlservr+000160DB)
> (CMsqlExecContext::ExecuteStmts(class ExecutionContex
> 0041767 E Module(sqlservr+0001767E) (process_commands
> (struct srv_proc *)+000001E7)
> 0043 B7EF Module(sqlservr+0003B7EF) (execute_rpc
> (struct srv_proc *)+00000019)
> 00447078 Module(sqlservr+00047078)
> (CCompPlan::FCompileStep(class CAlgStmt *,class
> CStatement * *)+00000AE7)
> 004510 FE Module(sqlservr+000510FE)
> (CProchdr::FCompile(class CCompPlan *,class CParamExc
> 0049 CB9F Module(sqlservr+0009CB9F)
> (CStmtExec::XretExecute(class CMsqlExecContext *)cons
> 0049 CD0A Module(sqlservr+0009CD0A)
> (CStmtExec::XretLocalExec(class CMsqlExecContext *,un
> 0049 C6F4 Module(sqlservr+0009C6F4)
> (CSQLObject::FGetFromDisk(class CParamExchange *)+000
> 0049 DA48 Module(sqlservr+0009DA48)
> (CStmtSelect::Init(class CAlgStmt *,class CCompPlan *
> 00563 F78 Module(sqlservr+00163F78)
> (CStmtQuery::InitQuery(class CAlgStmt *,class CCompPl
> 00564019 Module(sqlservr+00164019)
> (BuildQueryFromTree(class TREE *,class IMemObj
> *,class IMemObj *,class IQueryOb
> 005642 CD Module(sqlservr+001642CD)
> (CCvtTree::PqryFromTree(class TREE *,class IMemObj *,
> 0056701 F Module(sqlservr+0016701F)
> (CBndOutputs::RemapValrefs(class CRemapContext *,int)
> 00567536 Module(sqlservr+00167536)
> (CXte::ExecCompile(class CExecCompContext *)
> +000000B7)
> 00567536 Module(sqlservr+00167536)
> (CXte::ExecCompile(class CExecCompContext *)
> +000000B7)
> 005688 A4 Module(sqlservr+001688A4) (CQuery::Prepare
> (void)+00000116)
> 0061 DDB6 Module(sqlservr+0021DDB6)
> (CSpecProc::Execute(class CParamExchange *)+00000092)
> 0061 DA3E Module(sqlservr+0021DA3E)
> (CSpecProc::ExecuteSpecial(class CParamExchange *,uns
> 0063 C71D Module(sqlservr+0023C71D) (execrpc(struct
> srv_proc *)+000004A8)
> 00703 A1C Module(sqlservr+00303A1C)
> (CXteHashMatch::CreateInputScan(class IMemObj *,class
> 2003-11-05 12:36:10.29 server Microsoft SQL Server
> 2000 - 8.00.194 (Intel X86) ...
> 2003-11-05 12:36:10.54 server Logging SQL Server
> messages in file 'd:\Program Files\Microsoft SQL
> Server\MSSQ
> 2003-11-05 12:36:10.54 server Server Process ID is 1700.
> 2003-11-05 12:36:10.54 server All rights reserved.
> 2003-11-05 12:36:10.54 server Copyright (C) 1988-2000
> Microsoft Corporation.
> 2003-11-05 12:36:10.99 server SQL Server is starting at
> priority class 'normal'(4 CPUs detected).
> 2003-11-05 12:36:13.00 server SQL Server configured for
> thread mode processing.
> 2003-11-05 12:36:13.23 server Using dynamic lock
> allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks.
> 2003-11-05 12:36:13.62 server Attempting to initialize
> Distributed Transaction Coordinator.
> 2003-11-05 12:36:19.92 spid2 Starting up
> database 'master'.
> 2003-11-05 12:36:27.70 spid5 Starting up
> database 'model'.
> 2003-11-05 12:36:27.70 server Using 'SSNETLIB.DLL'
> version '8.0.194'.
> 2003-11-05 12:36:27.73 spid2 Server name is 'WRLW2S002'.
> 2003-11-05 12:36:27.79 spid12 Starting up
> database 'powerway'.
> 2003-11-05 12:36:27.79 spid11 Starting up
> database 'dbWheelset_Live'.
> 2003-11-05 12:36:27.79 spid10 Starting up
> database 'Northwind'.
> 2003-11-05 12:36:27.79 spid9 Starting up
> database 'pubs'.
> 2003-11-05 12:36:27.79 spid8 Starting up
> database 'msdb'.
> 2003-11-05 12:36:27.81 spid14 Starting up
> database 'dbWheelSets_LIVE'.
> 2003-11-05 12:36:27.81 spid13 Starting up
> database 'dbWheelSets_TEST'.
> 2003-11-05 12:36:27.89 spid16 Starting up
> database 'dbWheelsets_ARCH_TEST'.
> 2003-11-05 12:36:27.89 spid15 Starting up
> database 'dbWheelsets_BACKUP'.
> 2003-11-05 12:36:27.98 spid17 Starting up
> database 'dbWheelsets_DATA_TEST'.
> 2003-11-05 12:36:28.43 spid5 Clearing tempdb database.
> 2003-11-05 12:36:28.51 spid11 Analysis of
> database 'dbWheelset_Live' (7) is 100% complete
> (approximately 0 mo
> 2003-11-05 12:36:28.65 spid12 Analysis of
> database 'powerway' (8) is 100% complete (approximately 0
> more seco
> 2003-11-05 12:36:28.87 server SQL Server is ready for
> client connections
> 2003-11-05 12:36:28.87 server SQL server listening on
> 172.20.120.23:1433, 127.0.0.1:1433.
> 2003-11-05 12:36:28.87 server SQL server listening on
> TCP, Shared Memory, Named Pipes.
> 2003-11-05 12:36:29.76 spid13 Analysis of
> database 'dbWheelSets_TEST' (9) is 100% complete
> (approximately 0 m
> 2003-11-05 12:36:38.67 spid5 Starting up
> database 'tempdb'.
> 2003-11-05 12:36:41.85 spid2 Recovery complete.
> 2003-11-05 12:36:49.51 spid51 Using 'xpsqlbot.dll'
> version '2000.80.194' to execute extended stored procedure
> 2003-11-05 12:36:51.96 spid51 Using 'xpstar.dll'
> version '2000.80.194' to execute extended stored
> procedure '
> 2003-11-05 13:15:27.45 spid55 Using 'sqlimage.dll'
> version '4.0.5'...
> 2003-11-05 13:15:27.46 spid55 SqlDumpExceptionHandler:
> Process 55 generated fatal exception c0000005 EXCEPTIO
> 2003-11-05 13:15:27.46 spid55 Error: 0, Severity: 19,
> State: 0
> 410735 D0 Module(UMS+000035D0) (ProcessWorkRequests
> (class UmsWorkQueue *)+00000264)
> 4107382 C Module(UMS+0000382C) (ThreadStartRoutine
> (void *)+000000BC)
> 7 C57B382 Module(KERNEL32+0000B382)
> (lstrcmpiW+000000B7)
> 78008454 Module(MSVCRT+00008454)
> (_endthread+000000C1)
>

Connection fails and currupt log

One of our customers has SQL server 2000 installed
This has been working perfectly for over a year
Now various databases have started to return errors when queries are
run on the data from VB or Query Analyser.
A typical error is:
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData
(CheckForData()).
Server: Msg 11, Level 16, State 1, Line 0
General Network Error. Check your network documentation
Connection broken
Not all the database produce errors but there appears to be no pattern
to which databases still work.
I have two backup copies of the main database they use. The main
database its self and one of the backups produce errors yet the other
backup, taken on the same day does not.
Looking at the error log (attached) there seems to be a lot of
"corrupt" entires.
Any suggestions* If you see corruption, then --
1. Check system and app event logs for details on any hardware corruption.
2. contact your hardware vendors to run some tests, diagnostics, etc and
also check for firmware upgrades.
3. Only then, RESTORE from your last healthy SQL Backup.
4. If you dont have a backup, then you could try to "Repair" the database
using "dbcc checkdb".
Thanks,
Vikram
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.

Connection faileed Package abort

Hello,

I am connecting with various sqlservers in a package to get the information. If connection failed with any sqlserver, package failed after 3 tries.

I would like that if connection failed with any sqlserver, package should not end rather move ahead and connecto next sqlserver.

I already tried to increase the number of error from 3 to 1000 but still package failed as soon sqlserver connection failed.

Any help is appreciated.

Thanks.

--

Farhan

There's quite a numbers of options for "on error resume next" style execution in SSIS. Consider precedence constraints,

the System::Propagate OnError event handler variable, and the

MaximumErrorCount and ForceExecutionResult properties.

One way to continue execution despite failure is to use Completion or Failure precedence constraints rather than Success constraints. When using Completion style precedence, execution will continue, and the package will fail by default due its max error count having been exceeded.

Another way to continue despite task errors is by setting ForcedExecutionResult of the tasks. Here again, execution will continue post failure, and the package will exit with a failure status due to the default max failure count (unless you set ForceExecutionResult on the package itself). This is effectively completition style precedence, except different events are fired. The OnTaskFailed event is not fired here, since the task "did not fail".

Another option is non-bubbling errors via System::Propogate in an OnError event handler. This approach will keep the error(s) from bubbling up the container

hierarchy, excepting validation errors. The task may fail, but the

package will succeed, because the task's execution errors never bubbled

up.

To use non-bubbling errors, create an error event handler on the failing task(s), and set the System::Propagate variable to false. Use this option in combination with completion based constraints when you want a package result of success despite failed tasks and want the failed tasks logged as such. Also, using the non-propagating error tactic, the OnTaskFailed event is fired, so you can hook that for logging purposes if need be.|||

Many thanks, I will give it a try.

You are the only who have replied, glad someone out there who knows and wants to help.

Connecting to SQL Server with an alias

We have a soon-to-be legacy Sql Server called X. We have several queries on
various other servers configured to talk to X thru a linked server that go
something like:
SELECT [columnName] FROM [X].[DBName].[dbo].[TableName]
X will now be hosted on a new machine called Y.
So my question is, is there a way of aliasing our new server called "Y" so
that it can be refered to as "X"?
TIA//I believe that you can do this using sp_addlinkedserver. Check out Books Online
(sp_addlinkedserver), the second example in the table. This suggests that you can specify some other
name for the linked server than the network name.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Chris Newby" <Chris.Newby@.Rockcreekglobal.com> wrote in message
news:%23LXjZH6FGHA.1676@.TK2MSFTNGP09.phx.gbl...
> We have a soon-to-be legacy Sql Server called X. We have several queries on various other servers
> configured to talk to X thru a linked server that go something like:
> SELECT [columnName] FROM [X].[DBName].[dbo].[TableName]
> X will now be hosted on a new machine called Y.
> So my question is, is there a way of aliasing our new server called "Y" so that it can be refered
> to as "X"?
> TIA//
>|||So you are using a linked server to achive the connection to the server
X. Defining a server alias within the network client tool should do the
trick.
HTH, jens Suessmeyer.