Tuesday, March 20, 2012
3 global variables 3 sql server connections?
I've 3 sql server connections in the DTS package. They are:
conn1
conn2
conn3
Using dynamic properties task, I set up three global variables (gv1, gv2
and gv3).
For conn1 - I am getting server value from @.@.servername. (I am running
this pkg under a sql server job). see the pkg execution code:
declare @.dtsrun varchar(300)
set @.dtsrun = 'dtsrun /F d:\DTS\Mydts.dts /N Mydts /Agv1:8=' +
@.@.servername
exec master.dbo.xp_cmdshell @.dtsrun
for conn2 and conn3, I am using ActiveX script inside the DTS pkg to get
the server values (which are stored in a table in the db).
I am getting server values for 'gv2' and 'gv3'. My question is how would
I pass "gv2" value in "conn2" and "gv3" value in "conn3"?
thanks for your help!
*** Sent via Developersdex http://www.examnotes.net ***why don't have such values into global variables? It seems the most reliable
and safe way
--
Current location: Alicante (ES)
"Test Test" wrote:
> Hello!
> I've 3 sql server connections in the DTS package. They are:
> conn1
> conn2
> conn3
> Using dynamic properties task, I set up three global variables (gv1, gv2
> and gv3).
> For conn1 - I am getting server value from @.@.servername. (I am running
> this pkg under a sql server job). see the pkg execution code:
> declare @.dtsrun varchar(300)
> set @.dtsrun = 'dtsrun /F d:\DTS\Mydts.dts /N Mydts /Agv1:8=' +
> @.@.servername
> exec master.dbo.xp_cmdshell @.dtsrun
> for conn2 and conn3, I am using ActiveX script inside the DTS pkg to get
> the server values (which are stored in a table in the db).
> I am getting server values for 'gv2' and 'gv3'. My question is how would
> I pass "gv2" value in "conn2" and "gv3" value in "conn3"?
> thanks for your help!
>
>
>
>
>
> *** Sent via Developersdex http://www.examnotes.net ***
>
Sunday, February 19, 2012
2005 Management Studio sa default 'arabic' language
As it appears you have found an issue with the management dialog or an underlying component. I have filed a bug for this so it can be followed up in a service pack (pending the team's decision to fix this).
In reality the default language is not Arabic but it is likely to be English (depending on your version of SQL Server 2005). So the dialog misrepresents this. So you don't need to learn yet another language ;-)
If I recall correctly, you can actually force it to English, and from there on it will display English as your default language. But that would be a workaround...
|||
Thanks. It seems to be more prevalent when SA has master as the default database.
2005 Management Studio sa default 'arabic' language
As it appears you have found an issue with the management dialog or an underlying component. I have filed a bug for this so it can be followed up in a service pack (pending the team's decision to fix this).
In reality the default language is not Arabic but it is likely to be English (depending on your version of SQL Server 2005). So the dialog misrepresents this. So you don't need to learn yet another language ;-)
If I recall correctly, you can actually force it to English, and from there on it will display English as your default language. But that would be a workaround...
|||
Thanks. It seems to be more prevalent when SA has master as the default database.