PackageVariable setting does not work in another environment

hi

I have this variable setting in C# in my self developement project works fine.

but when i implement it in actual project does not work.

/Set \\package.Variables[User::ArchiveExcelFileConnectSt].Properties[Value];\"" + xlspath + "\"

when i test it in SQl query analyzer i need to replace // with / and works fine. but when i implement in c# it does not in my actual project. both have different Database.

Do i need to turn on some thing in my Actual Databas that my project points too or is there some thing else.

Thanks,

Jasmien

Take a look at this thread...

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=660132&SiteID=1

Are you trying to do this in a SQL statement? Or are you using the Microsoft.SQLServer.ManagedDTS library?

|||

i fixed that problem . I was basically my production was pointing to one database and in part of my code i was trying to over write with my local database so it was conflicting.

sql

P2P reindexing

I was looking at setting up multiple SQL Server 2005 Standard edition
servers using Peer-to-Peer Replication with the goal being able to
reindex one server at a time so as not to have any downtime (via locked
tables). Would this work?
Also, I know log-shipping to a standby server only requires 1 CPU
license which is attractive as CPU licenses are pricey. Still, if I
use P2P only for this reindex purpose (including three nodes for
voting) with only one server being used by customers/users, is a 1 CPU
license good enough?
Thanks!
MichaelI can't seem to find an answer anywhere for these questions:
Can I run ALTER INDEX REBUILD seperately between a live SQL 2005 server
and the hot-standby server? This way, if the live table is locked
during this operation, the hot-standby server would take over the CRUD
statements.
Is it allowed to have a single CPU license for two SQL 2005 server if
one is a hot-standby-only server and the standby-only server is only
used for failover purposes. Note that when tables are locked during
ALTER INDEX REBUILD, I assume the failover would kick in. Is that
possible?
The goal is to have no downtime for executing ALTER INDEX REBUILD.
Thank you,
Michael

P2P reindexing

I was looking at setting up multiple SQL Server 2005 Standard edition
servers using Peer-to-Peer Replication with the goal being able to
reindex one server at a time so as not to have any downtime (via locked
tables). Would this work?
Also, I know log-shipping to a standby server only requires 1 CPU
license which is attractive as CPU licenses are pricey. Still, if I
use P2P only for this reindex purpose (including three nodes for
voting) with only one server being used by customers/users, is a 1 CPU
license good enough?
Thanks!
MichaelI can't seem to find an answer anywhere for these questions:
Can I run ALTER INDEX REBUILD seperately between a live SQL 2005 server
and the hot-standby server? This way, if the live table is locked
during this operation, the hot-standby server would take over the CRUD
statements.
Is it allowed to have a single CPU license for two SQL 2005 server if
one is a hot-standby-only server and the standby-only server is only
used for failover purposes. Note that when tables are locked during
ALTER INDEX REBUILD, I assume the failover would kick in. Is that
possible?
The goal is to have no downtime for executing ALTER INDEX REBUILD.
Thank you,
Michael

P2P reindexing

I was looking at setting up multiple SQL Server 2005 Standard edition
servers using Peer-to-Peer Replication with the goal being able to
reindex one server at a time so as not to have any downtime (via locked
tables). Would this work?
Also, I know log-shipping to a standby server only requires 1 CPU
license which is attractive as CPU licenses are pricey. Still, if I
use P2P only for this reindex purpose (including three nodes for
voting) with only one server being used by customers/users, is a 1 CPU
license good enough?
Thanks!
MichaelI can't seem to find an answer anywhere for these questions:
Can I run ALTER INDEX REBUILD seperately between a live SQL 2005 server
and the hot-standby server? This way, if the live table is locked
during this operation, the hot-standby server would take over the CRUD
statements.
Is it allowed to have a single CPU license for two SQL 2005 server if
one is a hot-standby-only server and the standby-only server is only
used for failover purposes. Note that when tables are locked during
ALTER INDEX REBUILD, I assume the failover would kick in. Is that
possible?
The goal is to have no downtime for executing ALTER INDEX REBUILD.
Thank you,
Michael