|
|
You're in the
sql server dts
group:Global Variables
sql server dts:
Hi,
1) in your execute sql task have the sql statement be something like exec myStoredProc ?, ?, ? where each "?" is a global variable you want to pass as a parameter to the stored procedure myStoredProc. Then click the parameters button and set each parameter (each of the "?") to the global variables. (the first "?" in the statement is the first parameter to set, the 2nd "?" the 2nd parameter, etc.) 2) I believe: When you right click and execute a dts package, the package is running in the Windows security context that you are logged in as and locally on the machine you are running Enterprise Manager and right clicking on. When you run it as a job it is running on the server and with whatever permissions the sql server agent has on the operating system. So if the sql server agent doesn't have permissions to read the file system on the server, the package will fail since you are trying to read the file system. So, be sure the user that the sql server agent runs under has Windows permissions to access the file system (I am not positive on how to do this without spending the time to set it up myself, but hopefully it will point you in the right direction). Perhaps this is what is causing your problem? HTH, Justin [quoted text, click to view] "Jonesgj" <g@btinternet.com> wrote in message news:c3ifug$k6$1@sparta.btinternet.com... > Two almost related items: > > 1. I have found how to set the values for these dynamically using VBscript, > but how can I use these in a Execute SQL Task. For example (from a previous > post) I want to collect the sizes of particular drives folders and files for > capacity management. I use VBscript FileSystemObject to do this. I can > update the database directly, but what about storing the values in a global > variable and then using a SQL Task, T-SQL to insert the values. > How do you do this? > > 2. I have encountered a problem with my VBscript (above) in that it works > fine by right clicking and executing the package manually, but I find it > does not always update the database when run in a scheduled job - I don't > know why. First look it seems to insert some of the records not all but what > ever causes the error, causes the job to fail - I am going to investigate, > but has anyone else had this problem before?? > > Thanks > > JonesG > >
Two almost related items:
1. I have found how to set the values for these dynamically using VBscript, but how can I use these in a Execute SQL Task. For example (from a previous post) I want to collect the sizes of particular drives folders and files for capacity management. I use VBscript FileSystemObject to do this. I can update the database directly, but what about storing the values in a global variable and then using a SQL Task, T-SQL to insert the values. How do you do this? 2. I have encountered a problem with my VBscript (above) in that it works fine by right clicking and executing the package manually, but I find it does not always update the database when run in a scheduled job - I don't know why. First look it seems to insert some of the records not all but what ever causes the error, causes the job to fail - I am going to investigate, but has anyone else had this problem before?? Thanks JonesG
Thanks Justin
1) I'll give it a go. 2) I have remote access so I thought I was running it in the correct context (ie I am not using my client Enterprise Manager, but the one actually on the remote box) However, are you saying there could be a difference between the permission EM has and the Agent? I'll check this on Monday - thanks JonesG [quoted text, click to view] "Justin Engelman" <GlobNews@adelphia.net> wrote in message news:v9idnaHVms4OrsDdRVn-jw@adelphia.com... > Hi, > 1) in your execute sql task have the sql statement be something like exec > myStoredProc ?, ?, ? where each "?" is a global variable you want to pass as > a parameter to the stored procedure myStoredProc. Then click the parameters > button and set each parameter (each of the "?") to the global variables. > (the first "?" in the statement is the first parameter to set, the 2nd "?" > the 2nd parameter, etc.) > > 2) I believe: When you right click and execute a dts package, the package is > running in the Windows security context that you are logged in as and > locally on the machine you are running Enterprise Manager and right clicking > on. When you run it as a job it is running on the server and with whatever > permissions the sql server agent has on the operating system. So if the sql > server agent doesn't have permissions to read the file system on the server, > the package will fail since you are trying to read the file system. So, be > sure the user that the sql server agent runs under has Windows permissions > to access the file system (I am not positive on how to do this without > spending the time to set it up myself, but hopefully it will point you in > the right direction). Perhaps this is what is causing your problem? > > HTH, > Justin > > > "Jonesgj" <g@btinternet.com> wrote in message > news:c3ifug$k6$1@sparta.btinternet.com... > > Two almost related items: > > > > 1. I have found how to set the values for these dynamically using > VBscript, > > but how can I use these in a Execute SQL Task. For example (from a > previous > > post) I want to collect the sizes of particular drives folders and files > for > > capacity management. I use VBscript FileSystemObject to do this. I can > > update the database directly, but what about storing the values in a > global > > variable and then using a SQL Task, T-SQL to insert the values. > > How do you do this? > > > > 2. I have encountered a problem with my VBscript (above) in that it works > > fine by right clicking and executing the package manually, but I find it > > does not always update the database when run in a scheduled job - I don't > > know why. First look it seems to insert some of the records not all but > what > > ever causes the error, causes the job to fail - I am going to investigate, > > but has anyone else had this problem before?? > > > > Thanks > > > > JonesG > > > > > >
#1
Assign the values to Global Variables in the Active Script task so DTSGlobalVariables("MyVar").Value = Use in the ExecuteSQL task like this INSERT TABLE(col list) VALUES(?,?,?) Using the parameters button you can then assign the Global Variables to the correct ? #2 Invariably the "Works interactively but fails when scheduled" problem can be resolved by this article http://support.microsoft.com/?kbid=269074 -- Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP) www.SQLDTS.com - The site for all your DTS needs. I support PASS - the definitive, global community for SQL Server professionals - http://www.sqlpass.org [quoted text, click to view] "Jonesgj" <g@btinternet.com> wrote in message news:c3ifug$k6$1@sparta.btinternet.com... > Two almost related items: > > 1. I have found how to set the values for these dynamically using VBscript, > but how can I use these in a Execute SQL Task. For example (from a previous > post) I want to collect the sizes of particular drives folders and files for > capacity management. I use VBscript FileSystemObject to do this. I can > update the database directly, but what about storing the values in a global > variable and then using a SQL Task, T-SQL to insert the values. > How do you do this? > > 2. I have encountered a problem with my VBscript (above) in that it works > fine by right clicking and executing the package manually, but I find it > does not always update the database when run in a scheduled job - I don't > know why. First look it seems to insert some of the records not all but what > ever causes the error, causes the job to fail - I am going to investigate, > but has anyone else had this problem before?? > > Thanks > > JonesG > >
For #2, the link Allan posted explains it better than I can. But, the
permission EM has is based on the login you are using (not sure, perhaps someone else can answer this - is it the Windows login you are under, or the SQL Server login set up for the registered server in EM if you are not using Win authentication to connect?). When run through a job for sql 2k: "The security context in which the job is run is determined by the owner of the job. If the job is owned by a login that is not a member of the Sysadmin server role, then the package is run under the context of the account setup as the SQL Agent Proxy Account, and has the rights and permissions of that account." HTH, Justin [quoted text, click to view] "Jonesgj" <g@btinternet.com> wrote in message news:c3jjk9$bu5$1@sparta.btinternet.com... > Thanks Justin > > 1) I'll give it a go. > 2) I have remote access so I thought I was running it in the correct context > (ie I am not using my client Enterprise Manager, but the one actually on the > remote box) However, are you saying there could be a difference between the > permission EM has and the Agent? I'll check this on Monday - thanks > > JonesG >
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |