I need to run an application that sends out automatic emails based on
specific conditions. I need to schedule this to run every evening, could it
be scheduled as one of the SQL server agent jobs, using sql2000 or is there
another way to schedule it? Thanks.
Paul G
Software engineer.
That sounds like a strainghtforward job for SQLAgent.
Linchi
"Paul" wrote:
> I need to run an application that sends out automatic emails based on
> specific conditions. I need to schedule this to run every evening, could it
> be scheduled as one of the SQL server agent jobs, using sql2000 or is there
> another way to schedule it? Thanks.
> --
> Paul G
> Software engineer.
|||thanks for the response. I can not use windows scheduler because of computer
restrictions but for example what command in SQL would I use to run the
executable called test.exe located at C:\?
Doesn't it have to be transact SQL to run out SQlAgent?
Paul.
Paul G
Software engineer.
"Linchi Shea" wrote:
[vbcol=seagreen]
> That sounds like a strainghtforward job for SQLAgent.
> Linchi
> "Paul" wrote:
|||Thanks for the response. I am using SQL 2000 but under the step types I only
see the following listed;
Replication Transaction-Log Reader
Replication Queue Reader
Replication Snapshot
Replication Merge
Tansact-SQL script
did not see a cmdExec type.
Paul G
Software engineer.
"Tibor Karaszi" wrote:
> A job has one or more jobsteps. There are different type of jobsteps. TSQL is for executing SQL
> commands, while CmdExec is for executing EXE files etc.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> news:4310F194-2BAB-4F52-BE75-4A6D019A3388@.microsoft.com...
>
|||Scroll up in the drop-down list, and you'll see it.
Linchi
"Paul" wrote:
[vbcol=seagreen]
> Thanks for the response. I am using SQL 2000 but under the step types I only
> see the following listed;
> Replication Transaction-Log Reader
> Replication Queue Reader
> Replication Snapshot
> Replication Merge
> Tansact-SQL script
> did not see a cmdExec type.
>
>
> --
> Paul G
> Software engineer.
>
> "Tibor Karaszi" wrote:
|||found it, thanks! so for the command I just use c:/test.exe to run the
executable called test.exe at location c:?
Paul G
Software engineer.
"Linchi Shea" wrote:
[vbcol=seagreen]
> Scroll up in the drop-down list, and you'll see it.
> Linchi
> "Paul" wrote:
|||Try it and see. Better yet, reference Books Online (for 2005 the link is
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/51352afc-a0a4-428b-8985-f9e58bb57c31.htm)
and see the explicit example there.
BOL are your friend!
Kevin G. Boles
Indicium Resources, Inc.
SQL Server MVP
kgboles a earthlink dt net
"Paul" <Paul@.discussions.microsoft.com> wrote in message
news:9FBC9A5D-3985-40F5-A268-45F2AEC68CBA@.microsoft.com...[vbcol=seagreen]
> found it, thanks! so for the command I just use c:/test.exe to run the
> executable called test.exe at location c:?
> --
> Paul G
> Software engineer.
>
> "Linchi Shea" wrote:
|||I currently have it has a windows app but I have the window closing at the
end of the program so no gui is left open.
Paul G
Software engineer.
"Tibor Karaszi" wrote:
> Yep. Just make sure that the program is a console program (no GUI element), since it is started by a
> service...
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> news:9FBC9A5D-3985-40F5-A268-45F2AEC68CBA@.microsoft.com...
>
|||yep the books on line are quite helpful although sometimes I have difficulty
comming up with the correct search string. thanks.
Paul G
Software engineer.
"TheSQLGuru" wrote:
> Try it and see. Better yet, reference Books Online (for 2005 the link is
> ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/51352afc-a0a4-428b-8985-f9e58bb57c31.htm)
> and see the explicit example there.
> BOL are your friend!
> --
> Kevin G. Boles
> Indicium Resources, Inc.
> SQL Server MVP
> kgboles a earthlink dt net
>
> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> news:9FBC9A5D-3985-40F5-A268-45F2AEC68CBA@.microsoft.com...
>
>
|||ok thanks I will try it, just wondering if it will work, I can just as easily
create a new console application with vs.net as well.
Paul G
Software engineer.
"Tibor Karaszi" wrote:
> That will probably not work, since a service has no window context at all. I.e., the windows API
> calls will make the program fail. But you could give it a go and see what happens.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> news:F605C191-3233-42B2-BB7A-41D9A6D1D9E5@.microsoft.com...
>
Showing posts with label based. Show all posts
Showing posts with label based. Show all posts
Friday, March 30, 2012
running application
I need to run an application that sends out automatic emails based on
specific conditions. I need to schedule this to run every evening, could it
be scheduled as one of the SQL server agent jobs, using sql2000 or is there
another way to schedule it? Thanks.
--
Paul G
Software engineer.That sounds like a strainghtforward job for SQLAgent.
Linchi
"Paul" wrote:
> I need to run an application that sends out automatic emails based on
> specific conditions. I need to schedule this to run every evening, could it
> be scheduled as one of the SQL server agent jobs, using sql2000 or is there
> another way to schedule it? Thanks.
> --
> Paul G
> Software engineer.|||thanks for the response. I can not use windows scheduler because of computer
restrictions but for example what command in SQL would I use to run the
executable called test.exe located at C:\?
Doesn't it have to be transact SQL to run out SQlAgent?
Paul.
--
Paul G
Software engineer.
"Linchi Shea" wrote:
> That sounds like a strainghtforward job for SQLAgent.
> Linchi
> "Paul" wrote:
> > I need to run an application that sends out automatic emails based on
> > specific conditions. I need to schedule this to run every evening, could it
> > be scheduled as one of the SQL server agent jobs, using sql2000 or is there
> > another way to schedule it? Thanks.
> > --
> > Paul G
> > Software engineer.|||A job has one or more jobsteps. There are different type of jobsteps. TSQL is for executing SQL
commands, while CmdExec is for executing EXE files etc.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Paul" <Paul@.discussions.microsoft.com> wrote in message
news:4310F194-2BAB-4F52-BE75-4A6D019A3388@.microsoft.com...
> thanks for the response. I can not use windows scheduler because of computer
> restrictions but for example what command in SQL would I use to run the
> executable called test.exe located at C:\?
> Doesn't it have to be transact SQL to run out SQlAgent?
> Paul.
> --
> Paul G
> Software engineer.
>
> "Linchi Shea" wrote:
>> That sounds like a strainghtforward job for SQLAgent.
>> Linchi
>> "Paul" wrote:
>> > I need to run an application that sends out automatic emails based on
>> > specific conditions. I need to schedule this to run every evening, could it
>> > be scheduled as one of the SQL server agent jobs, using sql2000 or is there
>> > another way to schedule it? Thanks.
>> > --
>> > Paul G
>> > Software engineer.|||Thanks for the response. I am using SQL 2000 but under the step types I only
see the following listed;
Replication Transaction-Log Reader
Replication Queue Reader
Replication Snapshot
Replication Merge
Tansact-SQL script
did not see a cmdExec type.
Paul G
Software engineer.
"Tibor Karaszi" wrote:
> A job has one or more jobsteps. There are different type of jobsteps. TSQL is for executing SQL
> commands, while CmdExec is for executing EXE files etc.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> news:4310F194-2BAB-4F52-BE75-4A6D019A3388@.microsoft.com...
> > thanks for the response. I can not use windows scheduler because of computer
> > restrictions but for example what command in SQL would I use to run the
> > executable called test.exe located at C:\?
> > Doesn't it have to be transact SQL to run out SQlAgent?
> >
> > Paul.
> > --
> > Paul G
> > Software engineer.
> >
> >
> > "Linchi Shea" wrote:
> >
> >> That sounds like a strainghtforward job for SQLAgent.
> >>
> >> Linchi
> >>
> >> "Paul" wrote:
> >>
> >> > I need to run an application that sends out automatic emails based on
> >> > specific conditions. I need to schedule this to run every evening, could it
> >> > be scheduled as one of the SQL server agent jobs, using sql2000 or is there
> >> > another way to schedule it? Thanks.
> >> > --
> >> > Paul G
> >> > Software engineer.
>|||Scroll up in the drop-down list, and you'll see it.
Linchi
"Paul" wrote:
> Thanks for the response. I am using SQL 2000 but under the step types I only
> see the following listed;
> Replication Transaction-Log Reader
> Replication Queue Reader
> Replication Snapshot
> Replication Merge
> Tansact-SQL script
> did not see a cmdExec type.
>
>
> --
> Paul G
> Software engineer.
>
> "Tibor Karaszi" wrote:
> > A job has one or more jobsteps. There are different type of jobsteps. TSQL is for executing SQL
> > commands, while CmdExec is for executing EXE files etc.
> >
> > --
> > Tibor Karaszi, SQL Server MVP
> > http://www.karaszi.com/sqlserver/default.asp
> > http://sqlblog.com/blogs/tibor_karaszi
> >
> >
> > "Paul" <Paul@.discussions.microsoft.com> wrote in message
> > news:4310F194-2BAB-4F52-BE75-4A6D019A3388@.microsoft.com...
> > > thanks for the response. I can not use windows scheduler because of computer
> > > restrictions but for example what command in SQL would I use to run the
> > > executable called test.exe located at C:\?
> > > Doesn't it have to be transact SQL to run out SQlAgent?
> > >
> > > Paul.
> > > --
> > > Paul G
> > > Software engineer.
> > >
> > >
> > > "Linchi Shea" wrote:
> > >
> > >> That sounds like a strainghtforward job for SQLAgent.
> > >>
> > >> Linchi
> > >>
> > >> "Paul" wrote:
> > >>
> > >> > I need to run an application that sends out automatic emails based on
> > >> > specific conditions. I need to schedule this to run every evening, could it
> > >> > be scheduled as one of the SQL server agent jobs, using sql2000 or is there
> > >> > another way to schedule it? Thanks.
> > >> > --
> > >> > Paul G
> > >> > Software engineer.
> >|||found it, thanks! so for the command I just use c:/test.exe to run the
executable called test.exe at location c:?
--
Paul G
Software engineer.
"Linchi Shea" wrote:
> Scroll up in the drop-down list, and you'll see it.
> Linchi
> "Paul" wrote:
> > Thanks for the response. I am using SQL 2000 but under the step types I only
> > see the following listed;
> > Replication Transaction-Log Reader
> > Replication Queue Reader
> > Replication Snapshot
> > Replication Merge
> > Tansact-SQL script
> > did not see a cmdExec type.
> >
> >
> >
> >
> >
> > --
> > Paul G
> > Software engineer.
> >
> >
> > "Tibor Karaszi" wrote:
> >
> > > A job has one or more jobsteps. There are different type of jobsteps. TSQL is for executing SQL
> > > commands, while CmdExec is for executing EXE files etc.
> > >
> > > --
> > > Tibor Karaszi, SQL Server MVP
> > > http://www.karaszi.com/sqlserver/default.asp
> > > http://sqlblog.com/blogs/tibor_karaszi
> > >
> > >
> > > "Paul" <Paul@.discussions.microsoft.com> wrote in message
> > > news:4310F194-2BAB-4F52-BE75-4A6D019A3388@.microsoft.com...
> > > > thanks for the response. I can not use windows scheduler because of computer
> > > > restrictions but for example what command in SQL would I use to run the
> > > > executable called test.exe located at C:\?
> > > > Doesn't it have to be transact SQL to run out SQlAgent?
> > > >
> > > > Paul.
> > > > --
> > > > Paul G
> > > > Software engineer.
> > > >
> > > >
> > > > "Linchi Shea" wrote:
> > > >
> > > >> That sounds like a strainghtforward job for SQLAgent.
> > > >>
> > > >> Linchi
> > > >>
> > > >> "Paul" wrote:
> > > >>
> > > >> > I need to run an application that sends out automatic emails based on
> > > >> > specific conditions. I need to schedule this to run every evening, could it
> > > >> > be scheduled as one of the SQL server agent jobs, using sql2000 or is there
> > > >> > another way to schedule it? Thanks.
> > > >> > --
> > > >> > Paul G
> > > >> > Software engineer.
> > >|||Yep. Just make sure that the program is a console program (no GUI element), since it is started by a
service...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Paul" <Paul@.discussions.microsoft.com> wrote in message
news:9FBC9A5D-3985-40F5-A268-45F2AEC68CBA@.microsoft.com...
> found it, thanks! so for the command I just use c:/test.exe to run the
> executable called test.exe at location c:?
> --
> Paul G
> Software engineer.
>
> "Linchi Shea" wrote:
>> Scroll up in the drop-down list, and you'll see it.
>> Linchi
>> "Paul" wrote:
>> > Thanks for the response. I am using SQL 2000 but under the step types I only
>> > see the following listed;
>> > Replication Transaction-Log Reader
>> > Replication Queue Reader
>> > Replication Snapshot
>> > Replication Merge
>> > Tansact-SQL script
>> > did not see a cmdExec type.
>> >
>> >
>> >
>> >
>> >
>> > --
>> > Paul G
>> > Software engineer.
>> >
>> >
>> > "Tibor Karaszi" wrote:
>> >
>> > > A job has one or more jobsteps. There are different type of jobsteps. TSQL is for executing
>> > > SQL
>> > > commands, while CmdExec is for executing EXE files etc.
>> > >
>> > > --
>> > > Tibor Karaszi, SQL Server MVP
>> > > http://www.karaszi.com/sqlserver/default.asp
>> > > http://sqlblog.com/blogs/tibor_karaszi
>> > >
>> > >
>> > > "Paul" <Paul@.discussions.microsoft.com> wrote in message
>> > > news:4310F194-2BAB-4F52-BE75-4A6D019A3388@.microsoft.com...
>> > > > thanks for the response. I can not use windows scheduler because of computer
>> > > > restrictions but for example what command in SQL would I use to run the
>> > > > executable called test.exe located at C:\?
>> > > > Doesn't it have to be transact SQL to run out SQlAgent?
>> > > >
>> > > > Paul.
>> > > > --
>> > > > Paul G
>> > > > Software engineer.
>> > > >
>> > > >
>> > > > "Linchi Shea" wrote:
>> > > >
>> > > >> That sounds like a strainghtforward job for SQLAgent.
>> > > >>
>> > > >> Linchi
>> > > >>
>> > > >> "Paul" wrote:
>> > > >>
>> > > >> > I need to run an application that sends out automatic emails based on
>> > > >> > specific conditions. I need to schedule this to run every evening, could it
>> > > >> > be scheduled as one of the SQL server agent jobs, using sql2000 or is there
>> > > >> > another way to schedule it? Thanks.
>> > > >> > --
>> > > >> > Paul G
>> > > >> > Software engineer.
>> > >|||Try it and see. Better yet, reference Books Online (for 2005 the link is
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/51352afc-a0a4-428b-8985-f9e58bb57c31.htm)
and see the explicit example there.
BOL are your friend!
--
Kevin G. Boles
Indicium Resources, Inc.
SQL Server MVP
kgboles a earthlink dt net
"Paul" <Paul@.discussions.microsoft.com> wrote in message
news:9FBC9A5D-3985-40F5-A268-45F2AEC68CBA@.microsoft.com...
> found it, thanks! so for the command I just use c:/test.exe to run the
> executable called test.exe at location c:?
> --
> Paul G
> Software engineer.
>
> "Linchi Shea" wrote:
>> Scroll up in the drop-down list, and you'll see it.
>> Linchi
>> "Paul" wrote:
>> > Thanks for the response. I am using SQL 2000 but under the step types
>> > I only
>> > see the following listed;
>> > Replication Transaction-Log Reader
>> > Replication Queue Reader
>> > Replication Snapshot
>> > Replication Merge
>> > Tansact-SQL script
>> > did not see a cmdExec type.
>> >
>> >
>> >
>> >
>> >
>> > --
>> > Paul G
>> > Software engineer.
>> >
>> >
>> > "Tibor Karaszi" wrote:
>> >
>> > > A job has one or more jobsteps. There are different type of jobsteps.
>> > > TSQL is for executing SQL
>> > > commands, while CmdExec is for executing EXE files etc.
>> > >
>> > > --
>> > > Tibor Karaszi, SQL Server MVP
>> > > http://www.karaszi.com/sqlserver/default.asp
>> > > http://sqlblog.com/blogs/tibor_karaszi
>> > >
>> > >
>> > > "Paul" <Paul@.discussions.microsoft.com> wrote in message
>> > > news:4310F194-2BAB-4F52-BE75-4A6D019A3388@.microsoft.com...
>> > > > thanks for the response. I can not use windows scheduler because
>> > > > of computer
>> > > > restrictions but for example what command in SQL would I use to run
>> > > > the
>> > > > executable called test.exe located at C:\?
>> > > > Doesn't it have to be transact SQL to run out SQlAgent?
>> > > >
>> > > > Paul.
>> > > > --
>> > > > Paul G
>> > > > Software engineer.
>> > > >
>> > > >
>> > > > "Linchi Shea" wrote:
>> > > >
>> > > >> That sounds like a strainghtforward job for SQLAgent.
>> > > >>
>> > > >> Linchi
>> > > >>
>> > > >> "Paul" wrote:
>> > > >>
>> > > >> > I need to run an application that sends out automatic emails
>> > > >> > based on
>> > > >> > specific conditions. I need to schedule this to run every
>> > > >> > evening, could it
>> > > >> > be scheduled as one of the SQL server agent jobs, using sql2000
>> > > >> > or is there
>> > > >> > another way to schedule it? Thanks.
>> > > >> > --
>> > > >> > Paul G
>> > > >> > Software engineer.
>> > >|||I currently have it has a windows app but I have the window closing at the
end of the program so no gui is left open.
--
Paul G
Software engineer.
"Tibor Karaszi" wrote:
> Yep. Just make sure that the program is a console program (no GUI element), since it is started by a
> service...
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> news:9FBC9A5D-3985-40F5-A268-45F2AEC68CBA@.microsoft.com...
> > found it, thanks! so for the command I just use c:/test.exe to run the
> > executable called test.exe at location c:?
> > --
> > Paul G
> > Software engineer.
> >
> >
> > "Linchi Shea" wrote:
> >
> >> Scroll up in the drop-down list, and you'll see it.
> >>
> >> Linchi
> >>
> >> "Paul" wrote:
> >>
> >> > Thanks for the response. I am using SQL 2000 but under the step types I only
> >> > see the following listed;
> >> > Replication Transaction-Log Reader
> >> > Replication Queue Reader
> >> > Replication Snapshot
> >> > Replication Merge
> >> > Tansact-SQL script
> >> > did not see a cmdExec type.
> >> >
> >> >
> >> >
> >> >
> >> >
> >> > --
> >> > Paul G
> >> > Software engineer.
> >> >
> >> >
> >> > "Tibor Karaszi" wrote:
> >> >
> >> > > A job has one or more jobsteps. There are different type of jobsteps. TSQL is for executing
> >> > > SQL
> >> > > commands, while CmdExec is for executing EXE files etc.
> >> > >
> >> > > --
> >> > > Tibor Karaszi, SQL Server MVP
> >> > > http://www.karaszi.com/sqlserver/default.asp
> >> > > http://sqlblog.com/blogs/tibor_karaszi
> >> > >
> >> > >
> >> > > "Paul" <Paul@.discussions.microsoft.com> wrote in message
> >> > > news:4310F194-2BAB-4F52-BE75-4A6D019A3388@.microsoft.com...
> >> > > > thanks for the response. I can not use windows scheduler because of computer
> >> > > > restrictions but for example what command in SQL would I use to run the
> >> > > > executable called test.exe located at C:\?
> >> > > > Doesn't it have to be transact SQL to run out SQlAgent?
> >> > > >
> >> > > > Paul.
> >> > > > --
> >> > > > Paul G
> >> > > > Software engineer.
> >> > > >
> >> > > >
> >> > > > "Linchi Shea" wrote:
> >> > > >
> >> > > >> That sounds like a strainghtforward job for SQLAgent.
> >> > > >>
> >> > > >> Linchi
> >> > > >>
> >> > > >> "Paul" wrote:
> >> > > >>
> >> > > >> > I need to run an application that sends out automatic emails based on
> >> > > >> > specific conditions. I need to schedule this to run every evening, could it
> >> > > >> > be scheduled as one of the SQL server agent jobs, using sql2000 or is there
> >> > > >> > another way to schedule it? Thanks.
> >> > > >> > --
> >> > > >> > Paul G
> >> > > >> > Software engineer.
> >> > >
>|||yep the books on line are quite helpful although sometimes I have difficulty
comming up with the correct search string. thanks.
--
Paul G
Software engineer.
"TheSQLGuru" wrote:
> Try it and see. Better yet, reference Books Online (for 2005 the link is
> ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/51352afc-a0a4-428b-8985-f9e58bb57c31.htm)
> and see the explicit example there.
> BOL are your friend!
> --
> Kevin G. Boles
> Indicium Resources, Inc.
> SQL Server MVP
> kgboles a earthlink dt net
>
> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> news:9FBC9A5D-3985-40F5-A268-45F2AEC68CBA@.microsoft.com...
> > found it, thanks! so for the command I just use c:/test.exe to run the
> > executable called test.exe at location c:?
> > --
> > Paul G
> > Software engineer.
> >
> >
> > "Linchi Shea" wrote:
> >
> >> Scroll up in the drop-down list, and you'll see it.
> >>
> >> Linchi
> >>
> >> "Paul" wrote:
> >>
> >> > Thanks for the response. I am using SQL 2000 but under the step types
> >> > I only
> >> > see the following listed;
> >> > Replication Transaction-Log Reader
> >> > Replication Queue Reader
> >> > Replication Snapshot
> >> > Replication Merge
> >> > Tansact-SQL script
> >> > did not see a cmdExec type.
> >> >
> >> >
> >> >
> >> >
> >> >
> >> > --
> >> > Paul G
> >> > Software engineer.
> >> >
> >> >
> >> > "Tibor Karaszi" wrote:
> >> >
> >> > > A job has one or more jobsteps. There are different type of jobsteps.
> >> > > TSQL is for executing SQL
> >> > > commands, while CmdExec is for executing EXE files etc.
> >> > >
> >> > > --
> >> > > Tibor Karaszi, SQL Server MVP
> >> > > http://www.karaszi.com/sqlserver/default.asp
> >> > > http://sqlblog.com/blogs/tibor_karaszi
> >> > >
> >> > >
> >> > > "Paul" <Paul@.discussions.microsoft.com> wrote in message
> >> > > news:4310F194-2BAB-4F52-BE75-4A6D019A3388@.microsoft.com...
> >> > > > thanks for the response. I can not use windows scheduler because
> >> > > > of computer
> >> > > > restrictions but for example what command in SQL would I use to run
> >> > > > the
> >> > > > executable called test.exe located at C:\?
> >> > > > Doesn't it have to be transact SQL to run out SQlAgent?
> >> > > >
> >> > > > Paul.
> >> > > > --
> >> > > > Paul G
> >> > > > Software engineer.
> >> > > >
> >> > > >
> >> > > > "Linchi Shea" wrote:
> >> > > >
> >> > > >> That sounds like a strainghtforward job for SQLAgent.
> >> > > >>
> >> > > >> Linchi
> >> > > >>
> >> > > >> "Paul" wrote:
> >> > > >>
> >> > > >> > I need to run an application that sends out automatic emails
> >> > > >> > based on
> >> > > >> > specific conditions. I need to schedule this to run every
> >> > > >> > evening, could it
> >> > > >> > be scheduled as one of the SQL server agent jobs, using sql2000
> >> > > >> > or is there
> >> > > >> > another way to schedule it? Thanks.
> >> > > >> > --
> >> > > >> > Paul G
> >> > > >> > Software engineer.
> >> > >
>
>|||That will probably not work, since a service has no window context at all. I.e., the windows API
calls will make the program fail. But you could give it a go and see what happens.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Paul" <Paul@.discussions.microsoft.com> wrote in message
news:F605C191-3233-42B2-BB7A-41D9A6D1D9E5@.microsoft.com...
>I currently have it has a windows app but I have the window closing at the
> end of the program so no gui is left open.
> --
> Paul G
> Software engineer.
>
> "Tibor Karaszi" wrote:
>> Yep. Just make sure that the program is a console program (no GUI element), since it is started
>> by a
>> service...
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Paul" <Paul@.discussions.microsoft.com> wrote in message
>> news:9FBC9A5D-3985-40F5-A268-45F2AEC68CBA@.microsoft.com...
>> > found it, thanks! so for the command I just use c:/test.exe to run the
>> > executable called test.exe at location c:?
>> > --
>> > Paul G
>> > Software engineer.
>> >
>> >
>> > "Linchi Shea" wrote:
>> >
>> >> Scroll up in the drop-down list, and you'll see it.
>> >>
>> >> Linchi
>> >>
>> >> "Paul" wrote:
>> >>
>> >> > Thanks for the response. I am using SQL 2000 but under the step types I only
>> >> > see the following listed;
>> >> > Replication Transaction-Log Reader
>> >> > Replication Queue Reader
>> >> > Replication Snapshot
>> >> > Replication Merge
>> >> > Tansact-SQL script
>> >> > did not see a cmdExec type.
>> >> >
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > Paul G
>> >> > Software engineer.
>> >> >
>> >> >
>> >> > "Tibor Karaszi" wrote:
>> >> >
>> >> > > A job has one or more jobsteps. There are different type of jobsteps. TSQL is for
>> >> > > executing
>> >> > > SQL
>> >> > > commands, while CmdExec is for executing EXE files etc.
>> >> > >
>> >> > > --
>> >> > > Tibor Karaszi, SQL Server MVP
>> >> > > http://www.karaszi.com/sqlserver/default.asp
>> >> > > http://sqlblog.com/blogs/tibor_karaszi
>> >> > >
>> >> > >
>> >> > > "Paul" <Paul@.discussions.microsoft.com> wrote in message
>> >> > > news:4310F194-2BAB-4F52-BE75-4A6D019A3388@.microsoft.com...
>> >> > > > thanks for the response. I can not use windows scheduler because of computer
>> >> > > > restrictions but for example what command in SQL would I use to run the
>> >> > > > executable called test.exe located at C:\?
>> >> > > > Doesn't it have to be transact SQL to run out SQlAgent?
>> >> > > >
>> >> > > > Paul.
>> >> > > > --
>> >> > > > Paul G
>> >> > > > Software engineer.
>> >> > > >
>> >> > > >
>> >> > > > "Linchi Shea" wrote:
>> >> > > >
>> >> > > >> That sounds like a strainghtforward job for SQLAgent.
>> >> > > >>
>> >> > > >> Linchi
>> >> > > >>
>> >> > > >> "Paul" wrote:
>> >> > > >>
>> >> > > >> > I need to run an application that sends out automatic emails based on
>> >> > > >> > specific conditions. I need to schedule this to run every evening, could it
>> >> > > >> > be scheduled as one of the SQL server agent jobs, using sql2000 or is there
>> >> > > >> > another way to schedule it? Thanks.
>> >> > > >> > --
>> >> > > >> > Paul G
>> >> > > >> > Software engineer.
>> >> > >|||ok thanks I will try it, just wondering if it will work, I can just as easily
create a new console application with vs.net as well.
--
Paul G
Software engineer.
"Tibor Karaszi" wrote:
> That will probably not work, since a service has no window context at all. I.e., the windows API
> calls will make the program fail. But you could give it a go and see what happens.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> news:F605C191-3233-42B2-BB7A-41D9A6D1D9E5@.microsoft.com...
> >I currently have it has a windows app but I have the window closing at the
> > end of the program so no gui is left open.
> > --
> > Paul G
> > Software engineer.
> >
> >
> > "Tibor Karaszi" wrote:
> >
> >> Yep. Just make sure that the program is a console program (no GUI element), since it is started
> >> by a
> >> service...
> >>
> >> --
> >> Tibor Karaszi, SQL Server MVP
> >> http://www.karaszi.com/sqlserver/default.asp
> >> http://sqlblog.com/blogs/tibor_karaszi
> >>
> >>
> >> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> >> news:9FBC9A5D-3985-40F5-A268-45F2AEC68CBA@.microsoft.com...
> >> > found it, thanks! so for the command I just use c:/test.exe to run the
> >> > executable called test.exe at location c:?
> >> > --
> >> > Paul G
> >> > Software engineer.
> >> >
> >> >
> >> > "Linchi Shea" wrote:
> >> >
> >> >> Scroll up in the drop-down list, and you'll see it.
> >> >>
> >> >> Linchi
> >> >>
> >> >> "Paul" wrote:
> >> >>
> >> >> > Thanks for the response. I am using SQL 2000 but under the step types I only
> >> >> > see the following listed;
> >> >> > Replication Transaction-Log Reader
> >> >> > Replication Queue Reader
> >> >> > Replication Snapshot
> >> >> > Replication Merge
> >> >> > Tansact-SQL script
> >> >> > did not see a cmdExec type.
> >> >> >
> >> >> >
> >> >> >
> >> >> >
> >> >> >
> >> >> > --
> >> >> > Paul G
> >> >> > Software engineer.
> >> >> >
> >> >> >
> >> >> > "Tibor Karaszi" wrote:
> >> >> >
> >> >> > > A job has one or more jobsteps. There are different type of jobsteps. TSQL is for
> >> >> > > executing
> >> >> > > SQL
> >> >> > > commands, while CmdExec is for executing EXE files etc.
> >> >> > >
> >> >> > > --
> >> >> > > Tibor Karaszi, SQL Server MVP
> >> >> > > http://www.karaszi.com/sqlserver/default.asp
> >> >> > > http://sqlblog.com/blogs/tibor_karaszi
> >> >> > >
> >> >> > >
> >> >> > > "Paul" <Paul@.discussions.microsoft.com> wrote in message
> >> >> > > news:4310F194-2BAB-4F52-BE75-4A6D019A3388@.microsoft.com...
> >> >> > > > thanks for the response. I can not use windows scheduler because of computer
> >> >> > > > restrictions but for example what command in SQL would I use to run the
> >> >> > > > executable called test.exe located at C:\?
> >> >> > > > Doesn't it have to be transact SQL to run out SQlAgent?
> >> >> > > >
> >> >> > > > Paul.
> >> >> > > > --
> >> >> > > > Paul G
> >> >> > > > Software engineer.
> >> >> > > >
> >> >> > > >
> >> >> > > > "Linchi Shea" wrote:
> >> >> > > >
> >> >> > > >> That sounds like a strainghtforward job for SQLAgent.
> >> >> > > >>
> >> >> > > >> Linchi
> >> >> > > >>
> >> >> > > >> "Paul" wrote:
> >> >> > > >>
> >> >> > > >> > I need to run an application that sends out automatic emails based on
> >> >> > > >> > specific conditions. I need to schedule this to run every evening, could it
> >> >> > > >> > be scheduled as one of the SQL server agent jobs, using sql2000 or is there
> >> >> > > >> > another way to schedule it? Thanks.
> >> >> > > >> > --
> >> >> > > >> > Paul G
> >> >> > > >> > Software engineer.
> >> >> > >
> >>
>|||I can't say 1005 it won't work, but I do know that we often see problems with the mere fact that a
program does GUI interaction. There might be some dependencies on OS version and/or SQL Server
version as well. So, I'd watch it carefully and since you do have an option to make it console app,
don't hesitate to do so in case it starts behaving fishy.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Paul" <Paul@.discussions.microsoft.com> wrote in message
news:2DAD30AB-1FFF-4751-A060-7C6A357F47E5@.microsoft.com...
> ok thanks I will try it, just wondering if it will work, I can just as easily
> create a new console application with vs.net as well.
> --
> Paul G
> Software engineer.
>
> "Tibor Karaszi" wrote:
>> That will probably not work, since a service has no window context at all. I.e., the windows API
>> calls will make the program fail. But you could give it a go and see what happens.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Paul" <Paul@.discussions.microsoft.com> wrote in message
>> news:F605C191-3233-42B2-BB7A-41D9A6D1D9E5@.microsoft.com...
>> >I currently have it has a windows app but I have the window closing at the
>> > end of the program so no gui is left open.
>> > --
>> > Paul G
>> > Software engineer.
>> >
>> >
>> > "Tibor Karaszi" wrote:
>> >
>> >> Yep. Just make sure that the program is a console program (no GUI element), since it is
>> >> started
>> >> by a
>> >> service...
>> >>
>> >> --
>> >> Tibor Karaszi, SQL Server MVP
>> >> http://www.karaszi.com/sqlserver/default.asp
>> >> http://sqlblog.com/blogs/tibor_karaszi
>> >>
>> >>
>> >> "Paul" <Paul@.discussions.microsoft.com> wrote in message
>> >> news:9FBC9A5D-3985-40F5-A268-45F2AEC68CBA@.microsoft.com...
>> >> > found it, thanks! so for the command I just use c:/test.exe to run the
>> >> > executable called test.exe at location c:?
>> >> > --
>> >> > Paul G
>> >> > Software engineer.
>> >> >
>> >> >
>> >> > "Linchi Shea" wrote:
>> >> >
>> >> >> Scroll up in the drop-down list, and you'll see it.
>> >> >>
>> >> >> Linchi
>> >> >>
>> >> >> "Paul" wrote:
>> >> >>
>> >> >> > Thanks for the response. I am using SQL 2000 but under the step types I only
>> >> >> > see the following listed;
>> >> >> > Replication Transaction-Log Reader
>> >> >> > Replication Queue Reader
>> >> >> > Replication Snapshot
>> >> >> > Replication Merge
>> >> >> > Tansact-SQL script
>> >> >> > did not see a cmdExec type.
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > --
>> >> >> > Paul G
>> >> >> > Software engineer.
>> >> >> >
>> >> >> >
>> >> >> > "Tibor Karaszi" wrote:
>> >> >> >
>> >> >> > > A job has one or more jobsteps. There are different type of jobsteps. TSQL is for
>> >> >> > > executing
>> >> >> > > SQL
>> >> >> > > commands, while CmdExec is for executing EXE files etc.
>> >> >> > >
>> >> >> > > --
>> >> >> > > Tibor Karaszi, SQL Server MVP
>> >> >> > > http://www.karaszi.com/sqlserver/default.asp
>> >> >> > > http://sqlblog.com/blogs/tibor_karaszi
>> >> >> > >
>> >> >> > >
>> >> >> > > "Paul" <Paul@.discussions.microsoft.com> wrote in message
>> >> >> > > news:4310F194-2BAB-4F52-BE75-4A6D019A3388@.microsoft.com...
>> >> >> > > > thanks for the response. I can not use windows scheduler because of computer
>> >> >> > > > restrictions but for example what command in SQL would I use to run the
>> >> >> > > > executable called test.exe located at C:\?
>> >> >> > > > Doesn't it have to be transact SQL to run out SQlAgent?
>> >> >> > > >
>> >> >> > > > Paul.
>> >> >> > > > --
>> >> >> > > > Paul G
>> >> >> > > > Software engineer.
>> >> >> > > >
>> >> >> > > >
>> >> >> > > > "Linchi Shea" wrote:
>> >> >> > > >
>> >> >> > > >> That sounds like a strainghtforward job for SQLAgent.
>> >> >> > > >>
>> >> >> > > >> Linchi
>> >> >> > > >>
>> >> >> > > >> "Paul" wrote:
>> >> >> > > >>
>> >> >> > > >> > I need to run an application that sends out automatic emails based on
>> >> >> > > >> > specific conditions. I need to schedule this to run every evening, could it
>> >> >> > > >> > be scheduled as one of the SQL server agent jobs, using sql2000 or is there
>> >> >> > > >> > another way to schedule it? Thanks.
>> >> >> > > >> > --
>> >> >> > > >> > Paul G
>> >> >> > > >> > Software engineer.
>> >> >> > >
>> >>|||It looks like it worked, this was just for test so when I build the real
application I will make it into a console app.
--
Paul G
Software engineer.
"Tibor Karaszi" wrote:
> I can't say 1005 it won't work, but I do know that we often see problems with the mere fact that a
> program does GUI interaction. There might be some dependencies on OS version and/or SQL Server
> version as well. So, I'd watch it carefully and since you do have an option to make it console app,
> don't hesitate to do so in case it starts behaving fishy.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> news:2DAD30AB-1FFF-4751-A060-7C6A357F47E5@.microsoft.com...
> > ok thanks I will try it, just wondering if it will work, I can just as easily
> > create a new console application with vs.net as well.
> > --
> > Paul G
> > Software engineer.
> >
> >
> > "Tibor Karaszi" wrote:
> >
> >> That will probably not work, since a service has no window context at all. I.e., the windows API
> >> calls will make the program fail. But you could give it a go and see what happens.
> >>
> >> --
> >> Tibor Karaszi, SQL Server MVP
> >> http://www.karaszi.com/sqlserver/default.asp
> >> http://sqlblog.com/blogs/tibor_karaszi
> >>
> >>
> >> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> >> news:F605C191-3233-42B2-BB7A-41D9A6D1D9E5@.microsoft.com...
> >> >I currently have it has a windows app but I have the window closing at the
> >> > end of the program so no gui is left open.
> >> > --
> >> > Paul G
> >> > Software engineer.
> >> >
> >> >
> >> > "Tibor Karaszi" wrote:
> >> >
> >> >> Yep. Just make sure that the program is a console program (no GUI element), since it is
> >> >> started
> >> >> by a
> >> >> service...
> >> >>
> >> >> --
> >> >> Tibor Karaszi, SQL Server MVP
> >> >> http://www.karaszi.com/sqlserver/default.asp
> >> >> http://sqlblog.com/blogs/tibor_karaszi
> >> >>
> >> >>
> >> >> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> >> >> news:9FBC9A5D-3985-40F5-A268-45F2AEC68CBA@.microsoft.com...
> >> >> > found it, thanks! so for the command I just use c:/test.exe to run the
> >> >> > executable called test.exe at location c:?
> >> >> > --
> >> >> > Paul G
> >> >> > Software engineer.
> >> >> >
> >> >> >
> >> >> > "Linchi Shea" wrote:
> >> >> >
> >> >> >> Scroll up in the drop-down list, and you'll see it.
> >> >> >>
> >> >> >> Linchi
> >> >> >>
> >> >> >> "Paul" wrote:
> >> >> >>
> >> >> >> > Thanks for the response. I am using SQL 2000 but under the step types I only
> >> >> >> > see the following listed;
> >> >> >> > Replication Transaction-Log Reader
> >> >> >> > Replication Queue Reader
> >> >> >> > Replication Snapshot
> >> >> >> > Replication Merge
> >> >> >> > Tansact-SQL script
> >> >> >> > did not see a cmdExec type.
> >> >> >> >
> >> >> >> >
> >> >> >> >
> >> >> >> >
> >> >> >> >
> >> >> >> > --
> >> >> >> > Paul G
> >> >> >> > Software engineer.
> >> >> >> >
> >> >> >> >
> >> >> >> > "Tibor Karaszi" wrote:
> >> >> >> >
> >> >> >> > > A job has one or more jobsteps. There are different type of jobsteps. TSQL is for
> >> >> >> > > executing
> >> >> >> > > SQL
> >> >> >> > > commands, while CmdExec is for executing EXE files etc.
> >> >> >> > >
> >> >> >> > > --
> >> >> >> > > Tibor Karaszi, SQL Server MVP
> >> >> >> > > http://www.karaszi.com/sqlserver/default.asp
> >> >> >> > > http://sqlblog.com/blogs/tibor_karaszi
> >> >> >> > >
> >> >> >> > >
> >> >> >> > > "Paul" <Paul@.discussions.microsoft.com> wrote in message
> >> >> >> > > news:4310F194-2BAB-4F52-BE75-4A6D019A3388@.microsoft.com...
> >> >> >> > > > thanks for the response. I can not use windows scheduler because of computer
> >> >> >> > > > restrictions but for example what command in SQL would I use to run the
> >> >> >> > > > executable called test.exe located at C:\?
> >> >> >> > > > Doesn't it have to be transact SQL to run out SQlAgent?
> >> >> >> > > >
> >> >> >> > > > Paul.
> >> >> >> > > > --
> >> >> >> > > > Paul G
> >> >> >> > > > Software engineer.
> >> >> >> > > >
> >> >> >> > > >
> >> >> >> > > > "Linchi Shea" wrote:
> >> >> >> > > >
> >> >> >> > > >> That sounds like a strainghtforward job for SQLAgent.
> >> >> >> > > >>
> >> >> >> > > >> Linchi
> >> >> >> > > >>
> >> >> >> > > >> "Paul" wrote:
> >> >> >> > > >>
> >> >> >> > > >> > I need to run an application that sends out automatic emails based on
> >> >> >> > > >> > specific conditions. I need to schedule this to run every evening, could it
> >> >> >> > > >> > be scheduled as one of the SQL server agent jobs, using sql2000 or is there
> >> >> >> > > >> > another way to schedule it? Thanks.
> >> >> >> > > >> > --
> >> >> >> > > >> > Paul G
> >> >> >> > > >> > Software engineer.
> >> >> >> > >
> >> >>
> >>
>
specific conditions. I need to schedule this to run every evening, could it
be scheduled as one of the SQL server agent jobs, using sql2000 or is there
another way to schedule it? Thanks.
--
Paul G
Software engineer.That sounds like a strainghtforward job for SQLAgent.
Linchi
"Paul" wrote:
> I need to run an application that sends out automatic emails based on
> specific conditions. I need to schedule this to run every evening, could it
> be scheduled as one of the SQL server agent jobs, using sql2000 or is there
> another way to schedule it? Thanks.
> --
> Paul G
> Software engineer.|||thanks for the response. I can not use windows scheduler because of computer
restrictions but for example what command in SQL would I use to run the
executable called test.exe located at C:\?
Doesn't it have to be transact SQL to run out SQlAgent?
Paul.
--
Paul G
Software engineer.
"Linchi Shea" wrote:
> That sounds like a strainghtforward job for SQLAgent.
> Linchi
> "Paul" wrote:
> > I need to run an application that sends out automatic emails based on
> > specific conditions. I need to schedule this to run every evening, could it
> > be scheduled as one of the SQL server agent jobs, using sql2000 or is there
> > another way to schedule it? Thanks.
> > --
> > Paul G
> > Software engineer.|||A job has one or more jobsteps. There are different type of jobsteps. TSQL is for executing SQL
commands, while CmdExec is for executing EXE files etc.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Paul" <Paul@.discussions.microsoft.com> wrote in message
news:4310F194-2BAB-4F52-BE75-4A6D019A3388@.microsoft.com...
> thanks for the response. I can not use windows scheduler because of computer
> restrictions but for example what command in SQL would I use to run the
> executable called test.exe located at C:\?
> Doesn't it have to be transact SQL to run out SQlAgent?
> Paul.
> --
> Paul G
> Software engineer.
>
> "Linchi Shea" wrote:
>> That sounds like a strainghtforward job for SQLAgent.
>> Linchi
>> "Paul" wrote:
>> > I need to run an application that sends out automatic emails based on
>> > specific conditions. I need to schedule this to run every evening, could it
>> > be scheduled as one of the SQL server agent jobs, using sql2000 or is there
>> > another way to schedule it? Thanks.
>> > --
>> > Paul G
>> > Software engineer.|||Thanks for the response. I am using SQL 2000 but under the step types I only
see the following listed;
Replication Transaction-Log Reader
Replication Queue Reader
Replication Snapshot
Replication Merge
Tansact-SQL script
did not see a cmdExec type.
Paul G
Software engineer.
"Tibor Karaszi" wrote:
> A job has one or more jobsteps. There are different type of jobsteps. TSQL is for executing SQL
> commands, while CmdExec is for executing EXE files etc.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> news:4310F194-2BAB-4F52-BE75-4A6D019A3388@.microsoft.com...
> > thanks for the response. I can not use windows scheduler because of computer
> > restrictions but for example what command in SQL would I use to run the
> > executable called test.exe located at C:\?
> > Doesn't it have to be transact SQL to run out SQlAgent?
> >
> > Paul.
> > --
> > Paul G
> > Software engineer.
> >
> >
> > "Linchi Shea" wrote:
> >
> >> That sounds like a strainghtforward job for SQLAgent.
> >>
> >> Linchi
> >>
> >> "Paul" wrote:
> >>
> >> > I need to run an application that sends out automatic emails based on
> >> > specific conditions. I need to schedule this to run every evening, could it
> >> > be scheduled as one of the SQL server agent jobs, using sql2000 or is there
> >> > another way to schedule it? Thanks.
> >> > --
> >> > Paul G
> >> > Software engineer.
>|||Scroll up in the drop-down list, and you'll see it.
Linchi
"Paul" wrote:
> Thanks for the response. I am using SQL 2000 but under the step types I only
> see the following listed;
> Replication Transaction-Log Reader
> Replication Queue Reader
> Replication Snapshot
> Replication Merge
> Tansact-SQL script
> did not see a cmdExec type.
>
>
> --
> Paul G
> Software engineer.
>
> "Tibor Karaszi" wrote:
> > A job has one or more jobsteps. There are different type of jobsteps. TSQL is for executing SQL
> > commands, while CmdExec is for executing EXE files etc.
> >
> > --
> > Tibor Karaszi, SQL Server MVP
> > http://www.karaszi.com/sqlserver/default.asp
> > http://sqlblog.com/blogs/tibor_karaszi
> >
> >
> > "Paul" <Paul@.discussions.microsoft.com> wrote in message
> > news:4310F194-2BAB-4F52-BE75-4A6D019A3388@.microsoft.com...
> > > thanks for the response. I can not use windows scheduler because of computer
> > > restrictions but for example what command in SQL would I use to run the
> > > executable called test.exe located at C:\?
> > > Doesn't it have to be transact SQL to run out SQlAgent?
> > >
> > > Paul.
> > > --
> > > Paul G
> > > Software engineer.
> > >
> > >
> > > "Linchi Shea" wrote:
> > >
> > >> That sounds like a strainghtforward job for SQLAgent.
> > >>
> > >> Linchi
> > >>
> > >> "Paul" wrote:
> > >>
> > >> > I need to run an application that sends out automatic emails based on
> > >> > specific conditions. I need to schedule this to run every evening, could it
> > >> > be scheduled as one of the SQL server agent jobs, using sql2000 or is there
> > >> > another way to schedule it? Thanks.
> > >> > --
> > >> > Paul G
> > >> > Software engineer.
> >|||found it, thanks! so for the command I just use c:/test.exe to run the
executable called test.exe at location c:?
--
Paul G
Software engineer.
"Linchi Shea" wrote:
> Scroll up in the drop-down list, and you'll see it.
> Linchi
> "Paul" wrote:
> > Thanks for the response. I am using SQL 2000 but under the step types I only
> > see the following listed;
> > Replication Transaction-Log Reader
> > Replication Queue Reader
> > Replication Snapshot
> > Replication Merge
> > Tansact-SQL script
> > did not see a cmdExec type.
> >
> >
> >
> >
> >
> > --
> > Paul G
> > Software engineer.
> >
> >
> > "Tibor Karaszi" wrote:
> >
> > > A job has one or more jobsteps. There are different type of jobsteps. TSQL is for executing SQL
> > > commands, while CmdExec is for executing EXE files etc.
> > >
> > > --
> > > Tibor Karaszi, SQL Server MVP
> > > http://www.karaszi.com/sqlserver/default.asp
> > > http://sqlblog.com/blogs/tibor_karaszi
> > >
> > >
> > > "Paul" <Paul@.discussions.microsoft.com> wrote in message
> > > news:4310F194-2BAB-4F52-BE75-4A6D019A3388@.microsoft.com...
> > > > thanks for the response. I can not use windows scheduler because of computer
> > > > restrictions but for example what command in SQL would I use to run the
> > > > executable called test.exe located at C:\?
> > > > Doesn't it have to be transact SQL to run out SQlAgent?
> > > >
> > > > Paul.
> > > > --
> > > > Paul G
> > > > Software engineer.
> > > >
> > > >
> > > > "Linchi Shea" wrote:
> > > >
> > > >> That sounds like a strainghtforward job for SQLAgent.
> > > >>
> > > >> Linchi
> > > >>
> > > >> "Paul" wrote:
> > > >>
> > > >> > I need to run an application that sends out automatic emails based on
> > > >> > specific conditions. I need to schedule this to run every evening, could it
> > > >> > be scheduled as one of the SQL server agent jobs, using sql2000 or is there
> > > >> > another way to schedule it? Thanks.
> > > >> > --
> > > >> > Paul G
> > > >> > Software engineer.
> > >|||Yep. Just make sure that the program is a console program (no GUI element), since it is started by a
service...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Paul" <Paul@.discussions.microsoft.com> wrote in message
news:9FBC9A5D-3985-40F5-A268-45F2AEC68CBA@.microsoft.com...
> found it, thanks! so for the command I just use c:/test.exe to run the
> executable called test.exe at location c:?
> --
> Paul G
> Software engineer.
>
> "Linchi Shea" wrote:
>> Scroll up in the drop-down list, and you'll see it.
>> Linchi
>> "Paul" wrote:
>> > Thanks for the response. I am using SQL 2000 but under the step types I only
>> > see the following listed;
>> > Replication Transaction-Log Reader
>> > Replication Queue Reader
>> > Replication Snapshot
>> > Replication Merge
>> > Tansact-SQL script
>> > did not see a cmdExec type.
>> >
>> >
>> >
>> >
>> >
>> > --
>> > Paul G
>> > Software engineer.
>> >
>> >
>> > "Tibor Karaszi" wrote:
>> >
>> > > A job has one or more jobsteps. There are different type of jobsteps. TSQL is for executing
>> > > SQL
>> > > commands, while CmdExec is for executing EXE files etc.
>> > >
>> > > --
>> > > Tibor Karaszi, SQL Server MVP
>> > > http://www.karaszi.com/sqlserver/default.asp
>> > > http://sqlblog.com/blogs/tibor_karaszi
>> > >
>> > >
>> > > "Paul" <Paul@.discussions.microsoft.com> wrote in message
>> > > news:4310F194-2BAB-4F52-BE75-4A6D019A3388@.microsoft.com...
>> > > > thanks for the response. I can not use windows scheduler because of computer
>> > > > restrictions but for example what command in SQL would I use to run the
>> > > > executable called test.exe located at C:\?
>> > > > Doesn't it have to be transact SQL to run out SQlAgent?
>> > > >
>> > > > Paul.
>> > > > --
>> > > > Paul G
>> > > > Software engineer.
>> > > >
>> > > >
>> > > > "Linchi Shea" wrote:
>> > > >
>> > > >> That sounds like a strainghtforward job for SQLAgent.
>> > > >>
>> > > >> Linchi
>> > > >>
>> > > >> "Paul" wrote:
>> > > >>
>> > > >> > I need to run an application that sends out automatic emails based on
>> > > >> > specific conditions. I need to schedule this to run every evening, could it
>> > > >> > be scheduled as one of the SQL server agent jobs, using sql2000 or is there
>> > > >> > another way to schedule it? Thanks.
>> > > >> > --
>> > > >> > Paul G
>> > > >> > Software engineer.
>> > >|||Try it and see. Better yet, reference Books Online (for 2005 the link is
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/51352afc-a0a4-428b-8985-f9e58bb57c31.htm)
and see the explicit example there.
BOL are your friend!
--
Kevin G. Boles
Indicium Resources, Inc.
SQL Server MVP
kgboles a earthlink dt net
"Paul" <Paul@.discussions.microsoft.com> wrote in message
news:9FBC9A5D-3985-40F5-A268-45F2AEC68CBA@.microsoft.com...
> found it, thanks! so for the command I just use c:/test.exe to run the
> executable called test.exe at location c:?
> --
> Paul G
> Software engineer.
>
> "Linchi Shea" wrote:
>> Scroll up in the drop-down list, and you'll see it.
>> Linchi
>> "Paul" wrote:
>> > Thanks for the response. I am using SQL 2000 but under the step types
>> > I only
>> > see the following listed;
>> > Replication Transaction-Log Reader
>> > Replication Queue Reader
>> > Replication Snapshot
>> > Replication Merge
>> > Tansact-SQL script
>> > did not see a cmdExec type.
>> >
>> >
>> >
>> >
>> >
>> > --
>> > Paul G
>> > Software engineer.
>> >
>> >
>> > "Tibor Karaszi" wrote:
>> >
>> > > A job has one or more jobsteps. There are different type of jobsteps.
>> > > TSQL is for executing SQL
>> > > commands, while CmdExec is for executing EXE files etc.
>> > >
>> > > --
>> > > Tibor Karaszi, SQL Server MVP
>> > > http://www.karaszi.com/sqlserver/default.asp
>> > > http://sqlblog.com/blogs/tibor_karaszi
>> > >
>> > >
>> > > "Paul" <Paul@.discussions.microsoft.com> wrote in message
>> > > news:4310F194-2BAB-4F52-BE75-4A6D019A3388@.microsoft.com...
>> > > > thanks for the response. I can not use windows scheduler because
>> > > > of computer
>> > > > restrictions but for example what command in SQL would I use to run
>> > > > the
>> > > > executable called test.exe located at C:\?
>> > > > Doesn't it have to be transact SQL to run out SQlAgent?
>> > > >
>> > > > Paul.
>> > > > --
>> > > > Paul G
>> > > > Software engineer.
>> > > >
>> > > >
>> > > > "Linchi Shea" wrote:
>> > > >
>> > > >> That sounds like a strainghtforward job for SQLAgent.
>> > > >>
>> > > >> Linchi
>> > > >>
>> > > >> "Paul" wrote:
>> > > >>
>> > > >> > I need to run an application that sends out automatic emails
>> > > >> > based on
>> > > >> > specific conditions. I need to schedule this to run every
>> > > >> > evening, could it
>> > > >> > be scheduled as one of the SQL server agent jobs, using sql2000
>> > > >> > or is there
>> > > >> > another way to schedule it? Thanks.
>> > > >> > --
>> > > >> > Paul G
>> > > >> > Software engineer.
>> > >|||I currently have it has a windows app but I have the window closing at the
end of the program so no gui is left open.
--
Paul G
Software engineer.
"Tibor Karaszi" wrote:
> Yep. Just make sure that the program is a console program (no GUI element), since it is started by a
> service...
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> news:9FBC9A5D-3985-40F5-A268-45F2AEC68CBA@.microsoft.com...
> > found it, thanks! so for the command I just use c:/test.exe to run the
> > executable called test.exe at location c:?
> > --
> > Paul G
> > Software engineer.
> >
> >
> > "Linchi Shea" wrote:
> >
> >> Scroll up in the drop-down list, and you'll see it.
> >>
> >> Linchi
> >>
> >> "Paul" wrote:
> >>
> >> > Thanks for the response. I am using SQL 2000 but under the step types I only
> >> > see the following listed;
> >> > Replication Transaction-Log Reader
> >> > Replication Queue Reader
> >> > Replication Snapshot
> >> > Replication Merge
> >> > Tansact-SQL script
> >> > did not see a cmdExec type.
> >> >
> >> >
> >> >
> >> >
> >> >
> >> > --
> >> > Paul G
> >> > Software engineer.
> >> >
> >> >
> >> > "Tibor Karaszi" wrote:
> >> >
> >> > > A job has one or more jobsteps. There are different type of jobsteps. TSQL is for executing
> >> > > SQL
> >> > > commands, while CmdExec is for executing EXE files etc.
> >> > >
> >> > > --
> >> > > Tibor Karaszi, SQL Server MVP
> >> > > http://www.karaszi.com/sqlserver/default.asp
> >> > > http://sqlblog.com/blogs/tibor_karaszi
> >> > >
> >> > >
> >> > > "Paul" <Paul@.discussions.microsoft.com> wrote in message
> >> > > news:4310F194-2BAB-4F52-BE75-4A6D019A3388@.microsoft.com...
> >> > > > thanks for the response. I can not use windows scheduler because of computer
> >> > > > restrictions but for example what command in SQL would I use to run the
> >> > > > executable called test.exe located at C:\?
> >> > > > Doesn't it have to be transact SQL to run out SQlAgent?
> >> > > >
> >> > > > Paul.
> >> > > > --
> >> > > > Paul G
> >> > > > Software engineer.
> >> > > >
> >> > > >
> >> > > > "Linchi Shea" wrote:
> >> > > >
> >> > > >> That sounds like a strainghtforward job for SQLAgent.
> >> > > >>
> >> > > >> Linchi
> >> > > >>
> >> > > >> "Paul" wrote:
> >> > > >>
> >> > > >> > I need to run an application that sends out automatic emails based on
> >> > > >> > specific conditions. I need to schedule this to run every evening, could it
> >> > > >> > be scheduled as one of the SQL server agent jobs, using sql2000 or is there
> >> > > >> > another way to schedule it? Thanks.
> >> > > >> > --
> >> > > >> > Paul G
> >> > > >> > Software engineer.
> >> > >
>|||yep the books on line are quite helpful although sometimes I have difficulty
comming up with the correct search string. thanks.
--
Paul G
Software engineer.
"TheSQLGuru" wrote:
> Try it and see. Better yet, reference Books Online (for 2005 the link is
> ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/51352afc-a0a4-428b-8985-f9e58bb57c31.htm)
> and see the explicit example there.
> BOL are your friend!
> --
> Kevin G. Boles
> Indicium Resources, Inc.
> SQL Server MVP
> kgboles a earthlink dt net
>
> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> news:9FBC9A5D-3985-40F5-A268-45F2AEC68CBA@.microsoft.com...
> > found it, thanks! so for the command I just use c:/test.exe to run the
> > executable called test.exe at location c:?
> > --
> > Paul G
> > Software engineer.
> >
> >
> > "Linchi Shea" wrote:
> >
> >> Scroll up in the drop-down list, and you'll see it.
> >>
> >> Linchi
> >>
> >> "Paul" wrote:
> >>
> >> > Thanks for the response. I am using SQL 2000 but under the step types
> >> > I only
> >> > see the following listed;
> >> > Replication Transaction-Log Reader
> >> > Replication Queue Reader
> >> > Replication Snapshot
> >> > Replication Merge
> >> > Tansact-SQL script
> >> > did not see a cmdExec type.
> >> >
> >> >
> >> >
> >> >
> >> >
> >> > --
> >> > Paul G
> >> > Software engineer.
> >> >
> >> >
> >> > "Tibor Karaszi" wrote:
> >> >
> >> > > A job has one or more jobsteps. There are different type of jobsteps.
> >> > > TSQL is for executing SQL
> >> > > commands, while CmdExec is for executing EXE files etc.
> >> > >
> >> > > --
> >> > > Tibor Karaszi, SQL Server MVP
> >> > > http://www.karaszi.com/sqlserver/default.asp
> >> > > http://sqlblog.com/blogs/tibor_karaszi
> >> > >
> >> > >
> >> > > "Paul" <Paul@.discussions.microsoft.com> wrote in message
> >> > > news:4310F194-2BAB-4F52-BE75-4A6D019A3388@.microsoft.com...
> >> > > > thanks for the response. I can not use windows scheduler because
> >> > > > of computer
> >> > > > restrictions but for example what command in SQL would I use to run
> >> > > > the
> >> > > > executable called test.exe located at C:\?
> >> > > > Doesn't it have to be transact SQL to run out SQlAgent?
> >> > > >
> >> > > > Paul.
> >> > > > --
> >> > > > Paul G
> >> > > > Software engineer.
> >> > > >
> >> > > >
> >> > > > "Linchi Shea" wrote:
> >> > > >
> >> > > >> That sounds like a strainghtforward job for SQLAgent.
> >> > > >>
> >> > > >> Linchi
> >> > > >>
> >> > > >> "Paul" wrote:
> >> > > >>
> >> > > >> > I need to run an application that sends out automatic emails
> >> > > >> > based on
> >> > > >> > specific conditions. I need to schedule this to run every
> >> > > >> > evening, could it
> >> > > >> > be scheduled as one of the SQL server agent jobs, using sql2000
> >> > > >> > or is there
> >> > > >> > another way to schedule it? Thanks.
> >> > > >> > --
> >> > > >> > Paul G
> >> > > >> > Software engineer.
> >> > >
>
>|||That will probably not work, since a service has no window context at all. I.e., the windows API
calls will make the program fail. But you could give it a go and see what happens.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Paul" <Paul@.discussions.microsoft.com> wrote in message
news:F605C191-3233-42B2-BB7A-41D9A6D1D9E5@.microsoft.com...
>I currently have it has a windows app but I have the window closing at the
> end of the program so no gui is left open.
> --
> Paul G
> Software engineer.
>
> "Tibor Karaszi" wrote:
>> Yep. Just make sure that the program is a console program (no GUI element), since it is started
>> by a
>> service...
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Paul" <Paul@.discussions.microsoft.com> wrote in message
>> news:9FBC9A5D-3985-40F5-A268-45F2AEC68CBA@.microsoft.com...
>> > found it, thanks! so for the command I just use c:/test.exe to run the
>> > executable called test.exe at location c:?
>> > --
>> > Paul G
>> > Software engineer.
>> >
>> >
>> > "Linchi Shea" wrote:
>> >
>> >> Scroll up in the drop-down list, and you'll see it.
>> >>
>> >> Linchi
>> >>
>> >> "Paul" wrote:
>> >>
>> >> > Thanks for the response. I am using SQL 2000 but under the step types I only
>> >> > see the following listed;
>> >> > Replication Transaction-Log Reader
>> >> > Replication Queue Reader
>> >> > Replication Snapshot
>> >> > Replication Merge
>> >> > Tansact-SQL script
>> >> > did not see a cmdExec type.
>> >> >
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > Paul G
>> >> > Software engineer.
>> >> >
>> >> >
>> >> > "Tibor Karaszi" wrote:
>> >> >
>> >> > > A job has one or more jobsteps. There are different type of jobsteps. TSQL is for
>> >> > > executing
>> >> > > SQL
>> >> > > commands, while CmdExec is for executing EXE files etc.
>> >> > >
>> >> > > --
>> >> > > Tibor Karaszi, SQL Server MVP
>> >> > > http://www.karaszi.com/sqlserver/default.asp
>> >> > > http://sqlblog.com/blogs/tibor_karaszi
>> >> > >
>> >> > >
>> >> > > "Paul" <Paul@.discussions.microsoft.com> wrote in message
>> >> > > news:4310F194-2BAB-4F52-BE75-4A6D019A3388@.microsoft.com...
>> >> > > > thanks for the response. I can not use windows scheduler because of computer
>> >> > > > restrictions but for example what command in SQL would I use to run the
>> >> > > > executable called test.exe located at C:\?
>> >> > > > Doesn't it have to be transact SQL to run out SQlAgent?
>> >> > > >
>> >> > > > Paul.
>> >> > > > --
>> >> > > > Paul G
>> >> > > > Software engineer.
>> >> > > >
>> >> > > >
>> >> > > > "Linchi Shea" wrote:
>> >> > > >
>> >> > > >> That sounds like a strainghtforward job for SQLAgent.
>> >> > > >>
>> >> > > >> Linchi
>> >> > > >>
>> >> > > >> "Paul" wrote:
>> >> > > >>
>> >> > > >> > I need to run an application that sends out automatic emails based on
>> >> > > >> > specific conditions. I need to schedule this to run every evening, could it
>> >> > > >> > be scheduled as one of the SQL server agent jobs, using sql2000 or is there
>> >> > > >> > another way to schedule it? Thanks.
>> >> > > >> > --
>> >> > > >> > Paul G
>> >> > > >> > Software engineer.
>> >> > >|||ok thanks I will try it, just wondering if it will work, I can just as easily
create a new console application with vs.net as well.
--
Paul G
Software engineer.
"Tibor Karaszi" wrote:
> That will probably not work, since a service has no window context at all. I.e., the windows API
> calls will make the program fail. But you could give it a go and see what happens.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> news:F605C191-3233-42B2-BB7A-41D9A6D1D9E5@.microsoft.com...
> >I currently have it has a windows app but I have the window closing at the
> > end of the program so no gui is left open.
> > --
> > Paul G
> > Software engineer.
> >
> >
> > "Tibor Karaszi" wrote:
> >
> >> Yep. Just make sure that the program is a console program (no GUI element), since it is started
> >> by a
> >> service...
> >>
> >> --
> >> Tibor Karaszi, SQL Server MVP
> >> http://www.karaszi.com/sqlserver/default.asp
> >> http://sqlblog.com/blogs/tibor_karaszi
> >>
> >>
> >> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> >> news:9FBC9A5D-3985-40F5-A268-45F2AEC68CBA@.microsoft.com...
> >> > found it, thanks! so for the command I just use c:/test.exe to run the
> >> > executable called test.exe at location c:?
> >> > --
> >> > Paul G
> >> > Software engineer.
> >> >
> >> >
> >> > "Linchi Shea" wrote:
> >> >
> >> >> Scroll up in the drop-down list, and you'll see it.
> >> >>
> >> >> Linchi
> >> >>
> >> >> "Paul" wrote:
> >> >>
> >> >> > Thanks for the response. I am using SQL 2000 but under the step types I only
> >> >> > see the following listed;
> >> >> > Replication Transaction-Log Reader
> >> >> > Replication Queue Reader
> >> >> > Replication Snapshot
> >> >> > Replication Merge
> >> >> > Tansact-SQL script
> >> >> > did not see a cmdExec type.
> >> >> >
> >> >> >
> >> >> >
> >> >> >
> >> >> >
> >> >> > --
> >> >> > Paul G
> >> >> > Software engineer.
> >> >> >
> >> >> >
> >> >> > "Tibor Karaszi" wrote:
> >> >> >
> >> >> > > A job has one or more jobsteps. There are different type of jobsteps. TSQL is for
> >> >> > > executing
> >> >> > > SQL
> >> >> > > commands, while CmdExec is for executing EXE files etc.
> >> >> > >
> >> >> > > --
> >> >> > > Tibor Karaszi, SQL Server MVP
> >> >> > > http://www.karaszi.com/sqlserver/default.asp
> >> >> > > http://sqlblog.com/blogs/tibor_karaszi
> >> >> > >
> >> >> > >
> >> >> > > "Paul" <Paul@.discussions.microsoft.com> wrote in message
> >> >> > > news:4310F194-2BAB-4F52-BE75-4A6D019A3388@.microsoft.com...
> >> >> > > > thanks for the response. I can not use windows scheduler because of computer
> >> >> > > > restrictions but for example what command in SQL would I use to run the
> >> >> > > > executable called test.exe located at C:\?
> >> >> > > > Doesn't it have to be transact SQL to run out SQlAgent?
> >> >> > > >
> >> >> > > > Paul.
> >> >> > > > --
> >> >> > > > Paul G
> >> >> > > > Software engineer.
> >> >> > > >
> >> >> > > >
> >> >> > > > "Linchi Shea" wrote:
> >> >> > > >
> >> >> > > >> That sounds like a strainghtforward job for SQLAgent.
> >> >> > > >>
> >> >> > > >> Linchi
> >> >> > > >>
> >> >> > > >> "Paul" wrote:
> >> >> > > >>
> >> >> > > >> > I need to run an application that sends out automatic emails based on
> >> >> > > >> > specific conditions. I need to schedule this to run every evening, could it
> >> >> > > >> > be scheduled as one of the SQL server agent jobs, using sql2000 or is there
> >> >> > > >> > another way to schedule it? Thanks.
> >> >> > > >> > --
> >> >> > > >> > Paul G
> >> >> > > >> > Software engineer.
> >> >> > >
> >>
>|||I can't say 1005 it won't work, but I do know that we often see problems with the mere fact that a
program does GUI interaction. There might be some dependencies on OS version and/or SQL Server
version as well. So, I'd watch it carefully and since you do have an option to make it console app,
don't hesitate to do so in case it starts behaving fishy.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Paul" <Paul@.discussions.microsoft.com> wrote in message
news:2DAD30AB-1FFF-4751-A060-7C6A357F47E5@.microsoft.com...
> ok thanks I will try it, just wondering if it will work, I can just as easily
> create a new console application with vs.net as well.
> --
> Paul G
> Software engineer.
>
> "Tibor Karaszi" wrote:
>> That will probably not work, since a service has no window context at all. I.e., the windows API
>> calls will make the program fail. But you could give it a go and see what happens.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Paul" <Paul@.discussions.microsoft.com> wrote in message
>> news:F605C191-3233-42B2-BB7A-41D9A6D1D9E5@.microsoft.com...
>> >I currently have it has a windows app but I have the window closing at the
>> > end of the program so no gui is left open.
>> > --
>> > Paul G
>> > Software engineer.
>> >
>> >
>> > "Tibor Karaszi" wrote:
>> >
>> >> Yep. Just make sure that the program is a console program (no GUI element), since it is
>> >> started
>> >> by a
>> >> service...
>> >>
>> >> --
>> >> Tibor Karaszi, SQL Server MVP
>> >> http://www.karaszi.com/sqlserver/default.asp
>> >> http://sqlblog.com/blogs/tibor_karaszi
>> >>
>> >>
>> >> "Paul" <Paul@.discussions.microsoft.com> wrote in message
>> >> news:9FBC9A5D-3985-40F5-A268-45F2AEC68CBA@.microsoft.com...
>> >> > found it, thanks! so for the command I just use c:/test.exe to run the
>> >> > executable called test.exe at location c:?
>> >> > --
>> >> > Paul G
>> >> > Software engineer.
>> >> >
>> >> >
>> >> > "Linchi Shea" wrote:
>> >> >
>> >> >> Scroll up in the drop-down list, and you'll see it.
>> >> >>
>> >> >> Linchi
>> >> >>
>> >> >> "Paul" wrote:
>> >> >>
>> >> >> > Thanks for the response. I am using SQL 2000 but under the step types I only
>> >> >> > see the following listed;
>> >> >> > Replication Transaction-Log Reader
>> >> >> > Replication Queue Reader
>> >> >> > Replication Snapshot
>> >> >> > Replication Merge
>> >> >> > Tansact-SQL script
>> >> >> > did not see a cmdExec type.
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > --
>> >> >> > Paul G
>> >> >> > Software engineer.
>> >> >> >
>> >> >> >
>> >> >> > "Tibor Karaszi" wrote:
>> >> >> >
>> >> >> > > A job has one or more jobsteps. There are different type of jobsteps. TSQL is for
>> >> >> > > executing
>> >> >> > > SQL
>> >> >> > > commands, while CmdExec is for executing EXE files etc.
>> >> >> > >
>> >> >> > > --
>> >> >> > > Tibor Karaszi, SQL Server MVP
>> >> >> > > http://www.karaszi.com/sqlserver/default.asp
>> >> >> > > http://sqlblog.com/blogs/tibor_karaszi
>> >> >> > >
>> >> >> > >
>> >> >> > > "Paul" <Paul@.discussions.microsoft.com> wrote in message
>> >> >> > > news:4310F194-2BAB-4F52-BE75-4A6D019A3388@.microsoft.com...
>> >> >> > > > thanks for the response. I can not use windows scheduler because of computer
>> >> >> > > > restrictions but for example what command in SQL would I use to run the
>> >> >> > > > executable called test.exe located at C:\?
>> >> >> > > > Doesn't it have to be transact SQL to run out SQlAgent?
>> >> >> > > >
>> >> >> > > > Paul.
>> >> >> > > > --
>> >> >> > > > Paul G
>> >> >> > > > Software engineer.
>> >> >> > > >
>> >> >> > > >
>> >> >> > > > "Linchi Shea" wrote:
>> >> >> > > >
>> >> >> > > >> That sounds like a strainghtforward job for SQLAgent.
>> >> >> > > >>
>> >> >> > > >> Linchi
>> >> >> > > >>
>> >> >> > > >> "Paul" wrote:
>> >> >> > > >>
>> >> >> > > >> > I need to run an application that sends out automatic emails based on
>> >> >> > > >> > specific conditions. I need to schedule this to run every evening, could it
>> >> >> > > >> > be scheduled as one of the SQL server agent jobs, using sql2000 or is there
>> >> >> > > >> > another way to schedule it? Thanks.
>> >> >> > > >> > --
>> >> >> > > >> > Paul G
>> >> >> > > >> > Software engineer.
>> >> >> > >
>> >>|||It looks like it worked, this was just for test so when I build the real
application I will make it into a console app.
--
Paul G
Software engineer.
"Tibor Karaszi" wrote:
> I can't say 1005 it won't work, but I do know that we often see problems with the mere fact that a
> program does GUI interaction. There might be some dependencies on OS version and/or SQL Server
> version as well. So, I'd watch it carefully and since you do have an option to make it console app,
> don't hesitate to do so in case it starts behaving fishy.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> news:2DAD30AB-1FFF-4751-A060-7C6A357F47E5@.microsoft.com...
> > ok thanks I will try it, just wondering if it will work, I can just as easily
> > create a new console application with vs.net as well.
> > --
> > Paul G
> > Software engineer.
> >
> >
> > "Tibor Karaszi" wrote:
> >
> >> That will probably not work, since a service has no window context at all. I.e., the windows API
> >> calls will make the program fail. But you could give it a go and see what happens.
> >>
> >> --
> >> Tibor Karaszi, SQL Server MVP
> >> http://www.karaszi.com/sqlserver/default.asp
> >> http://sqlblog.com/blogs/tibor_karaszi
> >>
> >>
> >> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> >> news:F605C191-3233-42B2-BB7A-41D9A6D1D9E5@.microsoft.com...
> >> >I currently have it has a windows app but I have the window closing at the
> >> > end of the program so no gui is left open.
> >> > --
> >> > Paul G
> >> > Software engineer.
> >> >
> >> >
> >> > "Tibor Karaszi" wrote:
> >> >
> >> >> Yep. Just make sure that the program is a console program (no GUI element), since it is
> >> >> started
> >> >> by a
> >> >> service...
> >> >>
> >> >> --
> >> >> Tibor Karaszi, SQL Server MVP
> >> >> http://www.karaszi.com/sqlserver/default.asp
> >> >> http://sqlblog.com/blogs/tibor_karaszi
> >> >>
> >> >>
> >> >> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> >> >> news:9FBC9A5D-3985-40F5-A268-45F2AEC68CBA@.microsoft.com...
> >> >> > found it, thanks! so for the command I just use c:/test.exe to run the
> >> >> > executable called test.exe at location c:?
> >> >> > --
> >> >> > Paul G
> >> >> > Software engineer.
> >> >> >
> >> >> >
> >> >> > "Linchi Shea" wrote:
> >> >> >
> >> >> >> Scroll up in the drop-down list, and you'll see it.
> >> >> >>
> >> >> >> Linchi
> >> >> >>
> >> >> >> "Paul" wrote:
> >> >> >>
> >> >> >> > Thanks for the response. I am using SQL 2000 but under the step types I only
> >> >> >> > see the following listed;
> >> >> >> > Replication Transaction-Log Reader
> >> >> >> > Replication Queue Reader
> >> >> >> > Replication Snapshot
> >> >> >> > Replication Merge
> >> >> >> > Tansact-SQL script
> >> >> >> > did not see a cmdExec type.
> >> >> >> >
> >> >> >> >
> >> >> >> >
> >> >> >> >
> >> >> >> >
> >> >> >> > --
> >> >> >> > Paul G
> >> >> >> > Software engineer.
> >> >> >> >
> >> >> >> >
> >> >> >> > "Tibor Karaszi" wrote:
> >> >> >> >
> >> >> >> > > A job has one or more jobsteps. There are different type of jobsteps. TSQL is for
> >> >> >> > > executing
> >> >> >> > > SQL
> >> >> >> > > commands, while CmdExec is for executing EXE files etc.
> >> >> >> > >
> >> >> >> > > --
> >> >> >> > > Tibor Karaszi, SQL Server MVP
> >> >> >> > > http://www.karaszi.com/sqlserver/default.asp
> >> >> >> > > http://sqlblog.com/blogs/tibor_karaszi
> >> >> >> > >
> >> >> >> > >
> >> >> >> > > "Paul" <Paul@.discussions.microsoft.com> wrote in message
> >> >> >> > > news:4310F194-2BAB-4F52-BE75-4A6D019A3388@.microsoft.com...
> >> >> >> > > > thanks for the response. I can not use windows scheduler because of computer
> >> >> >> > > > restrictions but for example what command in SQL would I use to run the
> >> >> >> > > > executable called test.exe located at C:\?
> >> >> >> > > > Doesn't it have to be transact SQL to run out SQlAgent?
> >> >> >> > > >
> >> >> >> > > > Paul.
> >> >> >> > > > --
> >> >> >> > > > Paul G
> >> >> >> > > > Software engineer.
> >> >> >> > > >
> >> >> >> > > >
> >> >> >> > > > "Linchi Shea" wrote:
> >> >> >> > > >
> >> >> >> > > >> That sounds like a strainghtforward job for SQLAgent.
> >> >> >> > > >>
> >> >> >> > > >> Linchi
> >> >> >> > > >>
> >> >> >> > > >> "Paul" wrote:
> >> >> >> > > >>
> >> >> >> > > >> > I need to run an application that sends out automatic emails based on
> >> >> >> > > >> > specific conditions. I need to schedule this to run every evening, could it
> >> >> >> > > >> > be scheduled as one of the SQL server agent jobs, using sql2000 or is there
> >> >> >> > > >> > another way to schedule it? Thanks.
> >> >> >> > > >> > --
> >> >> >> > > >> > Paul G
> >> >> >> > > >> > Software engineer.
> >> >> >> > >
> >> >>
> >>
>
Friday, March 23, 2012
Run two stored procs in parallel
Hi
I have a simple stored proc which runs in less than a second.
This stored proc calculates different values based on parameters
passed.
For example sp_name "test 1 ' and
sp_name 'test 2 ' are totally different.
Now The issue is this stored proc is called more than 500 times in some
applications.
So these applications run for 500+ seconds . Although load on sql
server is almost negligible. Memory is also hugely available.
I need your suggestion in running these all at the same time.
In other words all 500 must be started at the same time ..there is no
need for one procedure to complete and the next to start. None of the
results are depenedent on any other results.
pls help me .
KannanIs this SQL 2000 or SQL 2005?
In 2005 is very easily accomplished using Service Broker. Instead of calling
the procedure 500 times, send 500 messages to a service that uses an
activated stored procedure. The message body would contain the arguments you
now pass in. Using the 'max_queue_readers' clause of CREATE QUEUE (see
http://msdn2.microsoft.com/en-us/library/ms190495(en-US,SQL.90).aspx) you
can control the maximum number of procedures to run in paralel.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
HTH,
~ Remus Rusanu
SQL Service Broker
http://msdn2.microsoft.com/en-us/library/ms166043(en-US,SQL.90).aspx
"Kannan" <Kannanmca@.gmail.com> wrote in message
news:1134587293.323886.256810@.z14g2000cwz.googlegroups.com...
> Hi
> I have a simple stored proc which runs in less than a second.
> This stored proc calculates different values based on parameters
> passed.
> For example sp_name "test 1 ' and
> sp_name 'test 2 ' are totally different.
>
> Now The issue is this stored proc is called more than 500 times in some
> applications.
> So these applications run for 500+ seconds . Although load on sql
> server is almost negligible. Memory is also hugely available.
> I need your suggestion in running these all at the same time.
> In other words all 500 must be started at the same time ..there is no
> need for one procedure to complete and the next to start. None of the
> results are depenedent on any other results.
>
> pls help me .
> Kannan
>|||> So these applications run for 500+ seconds . Although load on sql
> server is almost negligible. Memory is also hugely available.
Remus provided some SQL 2005 suggestions to improve throughput but I suggest
you do root cause performance analysis rather than throw parallel processing
at the problem.
Why do the procs run so long? Disk i/o? CPU? Network utilization? Do you
have SET NOCOUNT ON in your procs? If the load on SQL Server is low and you
have no resource problem, the procs should either run very fast or you
should observe high resource utilization.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Kannan" <Kannanmca@.gmail.com> wrote in message
news:1134587293.323886.256810@.z14g2000cwz.googlegroups.com...
> Hi
> I have a simple stored proc which runs in less than a second.
> This stored proc calculates different values based on parameters
> passed.
> For example sp_name "test 1 ' and
> sp_name 'test 2 ' are totally different.
>
> Now The issue is this stored proc is called more than 500 times in some
> applications.
> So these applications run for 500+ seconds . Although load on sql
> server is almost negligible. Memory is also hugely available.
> I need your suggestion in running these all at the same time.
> In other words all 500 must be started at the same time ..there is no
> need for one procedure to complete and the next to start. None of the
> results are depenedent on any other results.
>
> pls help me .
> Kannan
>|||Its SQL server 2000.
Its not a single proc that runs for 500 seconds its becuse the same
procedure is called 500 times with different parameters.
As I mentioned if you run the stored proc once it wont even run for a
second.
There are applications which take input from users and invoke my stored
procedure , The user may enter one value or 500 value.
If the user enters 500 values then the application calls my stored proc
500 times one after another.
That is what is causing a problem , So I created another proc which can
take any number of parameters and then invoke my orignal proc .
Like exec super_proc a,b,c will invoke
exec original_proc 'a'
exec original_proc 'b'
exec original_proc 'c'
Here again SQL server starts executing the next proc after it finishes
first.
I dont want sql server to execute serially but paralelly.
This explains why the load and memory are not utilized fully.
regards
Kannan|||> Its not a single proc that runs for 500 seconds its becuse the same
> procedure is called 500 times with different parameters.
> As I mentioned if you run the stored proc once it wont even run for a
> second.
Yes, I gathered this from your original post. My concern is that one second
is a *very* long time. I have seen single-threaded applications repeatedly
execute an insert stored procedure several hundred times per second. If
each of your proc executions run for a second, I would expect that you would
see high resource utilization (CPU, disk or network) for the duration of the
application run. If you don't, then something is wrong. You can certainly
throw additional threads at the problem but I suspect the performance
improvement won't be as good as you would like. For example, if you are I/O
bound, parallel processing might actually hurt performance.
> If the user enters 500 values then the application calls my stored proc
> 500 times one after another.
> That is what is causing a problem , So I created another proc which can
> take any number of parameters and then invoke my orignal proc .
This might make a miniscule difference due to reduced latency but it's
obviously not the long pole in the tent. I don't think you are addressing
the root cause of your slowness. Can you provide more details on the
calculations the proc performs. Perhaps some code and DDL would help.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Kannan" <Kannanmca@.gmail.com> wrote in message
news:1134591179.063554.66800@.g14g2000cwa.googlegroups.com...
> Its SQL server 2000.
> Its not a single proc that runs for 500 seconds its becuse the same
> procedure is called 500 times with different parameters.
> As I mentioned if you run the stored proc once it wont even run for a
> second.
> There are applications which take input from users and invoke my stored
> procedure , The user may enter one value or 500 value.
> If the user enters 500 values then the application calls my stored proc
> 500 times one after another.
> That is what is causing a problem , So I created another proc which can
> take any number of parameters and then invoke my orignal proc .
> Like exec super_proc a,b,c will invoke
> exec original_proc 'a'
> exec original_proc 'b'
> exec original_proc 'c'
> Here again SQL server starts executing the next proc after it finishes
> first.
> I dont want sql server to execute serially but paralelly.
> This explains why the load and memory are not utilized fully.
> regards
> Kannan
>|||I used one second just to illustrate my point. It actually runs in
milliseconds as u have mentioned.
I am not sure if i can post the code / Let me check on this .
will opening multiple connections from end application help ' multiple
connections will be run without any wait time right.
In other words if I run the same proc from two places at the same time
then the second proc will not wait for first one to complete right ?
This is what I want to achive using one connection !.
Kannan|||>I used one second just to illustrate my point. It actually runs in
> milliseconds as u have mentioned.
Is the 500 seconds total elapsed time accurate? Total elapsed time should
be roughly the sum the proc duration plus application processing time. So,
if you run a proc 500 times at an average of 10 ms. each, total duration
ought to be about 5 seconds.
> will opening multiple connections from end application help ' multiple
> connections will be run without any wait time right.
> In other words if I run the same proc from two places at the same time
> then the second proc will not wait for first one to complete right ?
> This is what I want to achive using one connection !.
There should be very little 'wait' time between proc executions on a single
connection. Perhaps a little latency but with only 500 executions, it
shouldn't add up to more than a few milliseconds total.
Multiple connections (multi-threaded processing) might help if you are not
resource constrained but you really need to know the cause of the problem is
before you develop a solution.
> I am not sure if i can post the code / Let me check on this .
The code might not be needed if the proc only runs in few milliseconds.
There's something else going on if the total elapsed time is high.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Kannan" <Kannanmca@.gmail.com> wrote in message
news:1134594222.338716.212980@.g43g2000cwa.googlegroups.com...
>I used one second just to illustrate my point. It actually runs in
> milliseconds as u have mentioned.
> I am not sure if i can post the code / Let me check on this .
> will opening multiple connections from end application help ' multiple
> connections will be run without any wait time right.
> In other words if I run the same proc from two places at the same time
> then the second proc will not wait for first one to complete right ?
> This is what I want to achive using one connection !.
> Kannan
>
I have a simple stored proc which runs in less than a second.
This stored proc calculates different values based on parameters
passed.
For example sp_name "test 1 ' and
sp_name 'test 2 ' are totally different.
Now The issue is this stored proc is called more than 500 times in some
applications.
So these applications run for 500+ seconds . Although load on sql
server is almost negligible. Memory is also hugely available.
I need your suggestion in running these all at the same time.
In other words all 500 must be started at the same time ..there is no
need for one procedure to complete and the next to start. None of the
results are depenedent on any other results.
pls help me .
KannanIs this SQL 2000 or SQL 2005?
In 2005 is very easily accomplished using Service Broker. Instead of calling
the procedure 500 times, send 500 messages to a service that uses an
activated stored procedure. The message body would contain the arguments you
now pass in. Using the 'max_queue_readers' clause of CREATE QUEUE (see
http://msdn2.microsoft.com/en-us/library/ms190495(en-US,SQL.90).aspx) you
can control the maximum number of procedures to run in paralel.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
HTH,
~ Remus Rusanu
SQL Service Broker
http://msdn2.microsoft.com/en-us/library/ms166043(en-US,SQL.90).aspx
"Kannan" <Kannanmca@.gmail.com> wrote in message
news:1134587293.323886.256810@.z14g2000cwz.googlegroups.com...
> Hi
> I have a simple stored proc which runs in less than a second.
> This stored proc calculates different values based on parameters
> passed.
> For example sp_name "test 1 ' and
> sp_name 'test 2 ' are totally different.
>
> Now The issue is this stored proc is called more than 500 times in some
> applications.
> So these applications run for 500+ seconds . Although load on sql
> server is almost negligible. Memory is also hugely available.
> I need your suggestion in running these all at the same time.
> In other words all 500 must be started at the same time ..there is no
> need for one procedure to complete and the next to start. None of the
> results are depenedent on any other results.
>
> pls help me .
> Kannan
>|||> So these applications run for 500+ seconds . Although load on sql
> server is almost negligible. Memory is also hugely available.
Remus provided some SQL 2005 suggestions to improve throughput but I suggest
you do root cause performance analysis rather than throw parallel processing
at the problem.
Why do the procs run so long? Disk i/o? CPU? Network utilization? Do you
have SET NOCOUNT ON in your procs? If the load on SQL Server is low and you
have no resource problem, the procs should either run very fast or you
should observe high resource utilization.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Kannan" <Kannanmca@.gmail.com> wrote in message
news:1134587293.323886.256810@.z14g2000cwz.googlegroups.com...
> Hi
> I have a simple stored proc which runs in less than a second.
> This stored proc calculates different values based on parameters
> passed.
> For example sp_name "test 1 ' and
> sp_name 'test 2 ' are totally different.
>
> Now The issue is this stored proc is called more than 500 times in some
> applications.
> So these applications run for 500+ seconds . Although load on sql
> server is almost negligible. Memory is also hugely available.
> I need your suggestion in running these all at the same time.
> In other words all 500 must be started at the same time ..there is no
> need for one procedure to complete and the next to start. None of the
> results are depenedent on any other results.
>
> pls help me .
> Kannan
>|||Its SQL server 2000.
Its not a single proc that runs for 500 seconds its becuse the same
procedure is called 500 times with different parameters.
As I mentioned if you run the stored proc once it wont even run for a
second.
There are applications which take input from users and invoke my stored
procedure , The user may enter one value or 500 value.
If the user enters 500 values then the application calls my stored proc
500 times one after another.
That is what is causing a problem , So I created another proc which can
take any number of parameters and then invoke my orignal proc .
Like exec super_proc a,b,c will invoke
exec original_proc 'a'
exec original_proc 'b'
exec original_proc 'c'
Here again SQL server starts executing the next proc after it finishes
first.
I dont want sql server to execute serially but paralelly.
This explains why the load and memory are not utilized fully.
regards
Kannan|||> Its not a single proc that runs for 500 seconds its becuse the same
> procedure is called 500 times with different parameters.
> As I mentioned if you run the stored proc once it wont even run for a
> second.
Yes, I gathered this from your original post. My concern is that one second
is a *very* long time. I have seen single-threaded applications repeatedly
execute an insert stored procedure several hundred times per second. If
each of your proc executions run for a second, I would expect that you would
see high resource utilization (CPU, disk or network) for the duration of the
application run. If you don't, then something is wrong. You can certainly
throw additional threads at the problem but I suspect the performance
improvement won't be as good as you would like. For example, if you are I/O
bound, parallel processing might actually hurt performance.
> If the user enters 500 values then the application calls my stored proc
> 500 times one after another.
> That is what is causing a problem , So I created another proc which can
> take any number of parameters and then invoke my orignal proc .
This might make a miniscule difference due to reduced latency but it's
obviously not the long pole in the tent. I don't think you are addressing
the root cause of your slowness. Can you provide more details on the
calculations the proc performs. Perhaps some code and DDL would help.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Kannan" <Kannanmca@.gmail.com> wrote in message
news:1134591179.063554.66800@.g14g2000cwa.googlegroups.com...
> Its SQL server 2000.
> Its not a single proc that runs for 500 seconds its becuse the same
> procedure is called 500 times with different parameters.
> As I mentioned if you run the stored proc once it wont even run for a
> second.
> There are applications which take input from users and invoke my stored
> procedure , The user may enter one value or 500 value.
> If the user enters 500 values then the application calls my stored proc
> 500 times one after another.
> That is what is causing a problem , So I created another proc which can
> take any number of parameters and then invoke my orignal proc .
> Like exec super_proc a,b,c will invoke
> exec original_proc 'a'
> exec original_proc 'b'
> exec original_proc 'c'
> Here again SQL server starts executing the next proc after it finishes
> first.
> I dont want sql server to execute serially but paralelly.
> This explains why the load and memory are not utilized fully.
> regards
> Kannan
>|||I used one second just to illustrate my point. It actually runs in
milliseconds as u have mentioned.
I am not sure if i can post the code / Let me check on this .
will opening multiple connections from end application help ' multiple
connections will be run without any wait time right.
In other words if I run the same proc from two places at the same time
then the second proc will not wait for first one to complete right ?
This is what I want to achive using one connection !.
Kannan|||>I used one second just to illustrate my point. It actually runs in
> milliseconds as u have mentioned.
Is the 500 seconds total elapsed time accurate? Total elapsed time should
be roughly the sum the proc duration plus application processing time. So,
if you run a proc 500 times at an average of 10 ms. each, total duration
ought to be about 5 seconds.
> will opening multiple connections from end application help ' multiple
> connections will be run without any wait time right.
> In other words if I run the same proc from two places at the same time
> then the second proc will not wait for first one to complete right ?
> This is what I want to achive using one connection !.
There should be very little 'wait' time between proc executions on a single
connection. Perhaps a little latency but with only 500 executions, it
shouldn't add up to more than a few milliseconds total.
Multiple connections (multi-threaded processing) might help if you are not
resource constrained but you really need to know the cause of the problem is
before you develop a solution.
> I am not sure if i can post the code / Let me check on this .
The code might not be needed if the proc only runs in few milliseconds.
There's something else going on if the total elapsed time is high.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Kannan" <Kannanmca@.gmail.com> wrote in message
news:1134594222.338716.212980@.g43g2000cwa.googlegroups.com...
>I used one second just to illustrate my point. It actually runs in
> milliseconds as u have mentioned.
> I am not sure if i can post the code / Let me check on this .
> will opening multiple connections from end application help ' multiple
> connections will be run without any wait time right.
> In other words if I run the same proc from two places at the same time
> then the second proc will not wait for first one to complete right ?
> This is what I want to achive using one connection !.
> Kannan
>
Wednesday, March 21, 2012
Run two stored procs in parallel
Hi
I have a simple stored proc which runs in less than a second.
This stored proc calculates different values based on parameters
passed.
For example sp_name "test 1 ' and
sp_name 'test 2 ' are totally different.
Now The issue is this stored proc is called more than 500 times in some
applications.
So these applications run for 500+ seconds . Although load on sql
server is almost negligible. Memory is also hugely available.
I need your suggestion in running these all at the same time.
In other words all 500 must be started at the same time ..there is no
need for one procedure to complete and the next to start. None of the
results are depenedent on any other results.
pls help me .
Kannan
Is this SQL 2000 or SQL 2005?
In 2005 is very easily accomplished using Service Broker. Instead of calling
the procedure 500 times, send 500 messages to a service that uses an
activated stored procedure. The message body would contain the arguments you
now pass in. Using the 'max_queue_readers' clause of CREATE QUEUE (see
http://msdn2.microsoft.com/en-us/library/ms190495(en-US,SQL.90).aspx) you
can control the maximum number of procedures to run in paralel.
This posting is provided "AS IS" with no warranties, and confers no rights.
HTH,
~ Remus Rusanu
SQL Service Broker
http://msdn2.microsoft.com/en-us/library/ms166043(en-US,SQL.90).aspx
"Kannan" <Kannanmca@.gmail.com> wrote in message
news:1134587293.323886.256810@.z14g2000cwz.googlegr oups.com...
> Hi
> I have a simple stored proc which runs in less than a second.
> This stored proc calculates different values based on parameters
> passed.
> For example sp_name "test 1 ' and
> sp_name 'test 2 ' are totally different.
>
> Now The issue is this stored proc is called more than 500 times in some
> applications.
> So these applications run for 500+ seconds . Although load on sql
> server is almost negligible. Memory is also hugely available.
> I need your suggestion in running these all at the same time.
> In other words all 500 must be started at the same time ..there is no
> need for one procedure to complete and the next to start. None of the
> results are depenedent on any other results.
>
> pls help me .
> Kannan
>
|||> So these applications run for 500+ seconds . Although load on sql
> server is almost negligible. Memory is also hugely available.
Remus provided some SQL 2005 suggestions to improve throughput but I suggest
you do root cause performance analysis rather than throw parallel processing
at the problem.
Why do the procs run so long? Disk i/o? CPU? Network utilization? Do you
have SET NOCOUNT ON in your procs? If the load on SQL Server is low and you
have no resource problem, the procs should either run very fast or you
should observe high resource utilization.
Hope this helps.
Dan Guzman
SQL Server MVP
"Kannan" <Kannanmca@.gmail.com> wrote in message
news:1134587293.323886.256810@.z14g2000cwz.googlegr oups.com...
> Hi
> I have a simple stored proc which runs in less than a second.
> This stored proc calculates different values based on parameters
> passed.
> For example sp_name "test 1 ' and
> sp_name 'test 2 ' are totally different.
>
> Now The issue is this stored proc is called more than 500 times in some
> applications.
> So these applications run for 500+ seconds . Although load on sql
> server is almost negligible. Memory is also hugely available.
> I need your suggestion in running these all at the same time.
> In other words all 500 must be started at the same time ..there is no
> need for one procedure to complete and the next to start. None of the
> results are depenedent on any other results.
>
> pls help me .
> Kannan
>
|||Its SQL server 2000.
Its not a single proc that runs for 500 seconds its becuse the same
procedure is called 500 times with different parameters.
As I mentioned if you run the stored proc once it wont even run for a
second.
There are applications which take input from users and invoke my stored
procedure , The user may enter one value or 500 value.
If the user enters 500 values then the application calls my stored proc
500 times one after another.
That is what is causing a problem , So I created another proc which can
take any number of parameters and then invoke my orignal proc .
Like exec super_proc a,b,c will invoke
exec original_proc 'a'
exec original_proc 'b'
exec original_proc 'c'
Here again SQL server starts executing the next proc after it finishes
first.
I dont want sql server to execute serially but paralelly.
This explains why the load and memory are not utilized fully.
regards
Kannan
|||> Its not a single proc that runs for 500 seconds its becuse the same
> procedure is called 500 times with different parameters.
> As I mentioned if you run the stored proc once it wont even run for a
> second.
Yes, I gathered this from your original post. My concern is that one second
is a *very* long time. I have seen single-threaded applications repeatedly
execute an insert stored procedure several hundred times per second. If
each of your proc executions run for a second, I would expect that you would
see high resource utilization (CPU, disk or network) for the duration of the
application run. If you don't, then something is wrong. You can certainly
throw additional threads at the problem but I suspect the performance
improvement won't be as good as you would like. For example, if you are I/O
bound, parallel processing might actually hurt performance.
> If the user enters 500 values then the application calls my stored proc
> 500 times one after another.
> That is what is causing a problem , So I created another proc which can
> take any number of parameters and then invoke my orignal proc .
This might make a miniscule difference due to reduced latency but it's
obviously not the long pole in the tent. I don't think you are addressing
the root cause of your slowness. Can you provide more details on the
calculations the proc performs. Perhaps some code and DDL would help.
Hope this helps.
Dan Guzman
SQL Server MVP
"Kannan" <Kannanmca@.gmail.com> wrote in message
news:1134591179.063554.66800@.g14g2000cwa.googlegro ups.com...
> Its SQL server 2000.
> Its not a single proc that runs for 500 seconds its becuse the same
> procedure is called 500 times with different parameters.
> As I mentioned if you run the stored proc once it wont even run for a
> second.
> There are applications which take input from users and invoke my stored
> procedure , The user may enter one value or 500 value.
> If the user enters 500 values then the application calls my stored proc
> 500 times one after another.
> That is what is causing a problem , So I created another proc which can
> take any number of parameters and then invoke my orignal proc .
> Like exec super_proc a,b,c will invoke
> exec original_proc 'a'
> exec original_proc 'b'
> exec original_proc 'c'
> Here again SQL server starts executing the next proc after it finishes
> first.
> I dont want sql server to execute serially but paralelly.
> This explains why the load and memory are not utilized fully.
> regards
> Kannan
>
|||I used one second just to illustrate my point. It actually runs in
milliseconds as u have mentioned.
I am not sure if i can post the code / Let me check on this .
will opening multiple connections from end application help ? multiple
connections will be run without any wait time right.
In other words if I run the same proc from two places at the same time
then the second proc will not wait for first one to complete right ?
This is what I want to achive using one connection !.
Kannan
|||>I used one second just to illustrate my point. It actually runs in
> milliseconds as u have mentioned.
Is the 500 seconds total elapsed time accurate? Total elapsed time should
be roughly the sum the proc duration plus application processing time. So,
if you run a proc 500 times at an average of 10 ms. each, total duration
ought to be about 5 seconds.
> will opening multiple connections from end application help ? multiple
> connections will be run without any wait time right.
> In other words if I run the same proc from two places at the same time
> then the second proc will not wait for first one to complete right ?
> This is what I want to achive using one connection !.
There should be very little 'wait' time between proc executions on a single
connection. Perhaps a little latency but with only 500 executions, it
shouldn't add up to more than a few milliseconds total.
Multiple connections (multi-threaded processing) might help if you are not
resource constrained but you really need to know the cause of the problem is
before you develop a solution.
> I am not sure if i can post the code / Let me check on this .
The code might not be needed if the proc only runs in few milliseconds.
There's something else going on if the total elapsed time is high.
Hope this helps.
Dan Guzman
SQL Server MVP
"Kannan" <Kannanmca@.gmail.com> wrote in message
news:1134594222.338716.212980@.g43g2000cwa.googlegr oups.com...
>I used one second just to illustrate my point. It actually runs in
> milliseconds as u have mentioned.
> I am not sure if i can post the code / Let me check on this .
> will opening multiple connections from end application help ? multiple
> connections will be run without any wait time right.
> In other words if I run the same proc from two places at the same time
> then the second proc will not wait for first one to complete right ?
> This is what I want to achive using one connection !.
> Kannan
>
I have a simple stored proc which runs in less than a second.
This stored proc calculates different values based on parameters
passed.
For example sp_name "test 1 ' and
sp_name 'test 2 ' are totally different.
Now The issue is this stored proc is called more than 500 times in some
applications.
So these applications run for 500+ seconds . Although load on sql
server is almost negligible. Memory is also hugely available.
I need your suggestion in running these all at the same time.
In other words all 500 must be started at the same time ..there is no
need for one procedure to complete and the next to start. None of the
results are depenedent on any other results.
pls help me .
Kannan
Is this SQL 2000 or SQL 2005?
In 2005 is very easily accomplished using Service Broker. Instead of calling
the procedure 500 times, send 500 messages to a service that uses an
activated stored procedure. The message body would contain the arguments you
now pass in. Using the 'max_queue_readers' clause of CREATE QUEUE (see
http://msdn2.microsoft.com/en-us/library/ms190495(en-US,SQL.90).aspx) you
can control the maximum number of procedures to run in paralel.
This posting is provided "AS IS" with no warranties, and confers no rights.
HTH,
~ Remus Rusanu
SQL Service Broker
http://msdn2.microsoft.com/en-us/library/ms166043(en-US,SQL.90).aspx
"Kannan" <Kannanmca@.gmail.com> wrote in message
news:1134587293.323886.256810@.z14g2000cwz.googlegr oups.com...
> Hi
> I have a simple stored proc which runs in less than a second.
> This stored proc calculates different values based on parameters
> passed.
> For example sp_name "test 1 ' and
> sp_name 'test 2 ' are totally different.
>
> Now The issue is this stored proc is called more than 500 times in some
> applications.
> So these applications run for 500+ seconds . Although load on sql
> server is almost negligible. Memory is also hugely available.
> I need your suggestion in running these all at the same time.
> In other words all 500 must be started at the same time ..there is no
> need for one procedure to complete and the next to start. None of the
> results are depenedent on any other results.
>
> pls help me .
> Kannan
>
|||> So these applications run for 500+ seconds . Although load on sql
> server is almost negligible. Memory is also hugely available.
Remus provided some SQL 2005 suggestions to improve throughput but I suggest
you do root cause performance analysis rather than throw parallel processing
at the problem.
Why do the procs run so long? Disk i/o? CPU? Network utilization? Do you
have SET NOCOUNT ON in your procs? If the load on SQL Server is low and you
have no resource problem, the procs should either run very fast or you
should observe high resource utilization.
Hope this helps.
Dan Guzman
SQL Server MVP
"Kannan" <Kannanmca@.gmail.com> wrote in message
news:1134587293.323886.256810@.z14g2000cwz.googlegr oups.com...
> Hi
> I have a simple stored proc which runs in less than a second.
> This stored proc calculates different values based on parameters
> passed.
> For example sp_name "test 1 ' and
> sp_name 'test 2 ' are totally different.
>
> Now The issue is this stored proc is called more than 500 times in some
> applications.
> So these applications run for 500+ seconds . Although load on sql
> server is almost negligible. Memory is also hugely available.
> I need your suggestion in running these all at the same time.
> In other words all 500 must be started at the same time ..there is no
> need for one procedure to complete and the next to start. None of the
> results are depenedent on any other results.
>
> pls help me .
> Kannan
>
|||Its SQL server 2000.
Its not a single proc that runs for 500 seconds its becuse the same
procedure is called 500 times with different parameters.
As I mentioned if you run the stored proc once it wont even run for a
second.
There are applications which take input from users and invoke my stored
procedure , The user may enter one value or 500 value.
If the user enters 500 values then the application calls my stored proc
500 times one after another.
That is what is causing a problem , So I created another proc which can
take any number of parameters and then invoke my orignal proc .
Like exec super_proc a,b,c will invoke
exec original_proc 'a'
exec original_proc 'b'
exec original_proc 'c'
Here again SQL server starts executing the next proc after it finishes
first.
I dont want sql server to execute serially but paralelly.
This explains why the load and memory are not utilized fully.
regards
Kannan
|||> Its not a single proc that runs for 500 seconds its becuse the same
> procedure is called 500 times with different parameters.
> As I mentioned if you run the stored proc once it wont even run for a
> second.
Yes, I gathered this from your original post. My concern is that one second
is a *very* long time. I have seen single-threaded applications repeatedly
execute an insert stored procedure several hundred times per second. If
each of your proc executions run for a second, I would expect that you would
see high resource utilization (CPU, disk or network) for the duration of the
application run. If you don't, then something is wrong. You can certainly
throw additional threads at the problem but I suspect the performance
improvement won't be as good as you would like. For example, if you are I/O
bound, parallel processing might actually hurt performance.
> If the user enters 500 values then the application calls my stored proc
> 500 times one after another.
> That is what is causing a problem , So I created another proc which can
> take any number of parameters and then invoke my orignal proc .
This might make a miniscule difference due to reduced latency but it's
obviously not the long pole in the tent. I don't think you are addressing
the root cause of your slowness. Can you provide more details on the
calculations the proc performs. Perhaps some code and DDL would help.
Hope this helps.
Dan Guzman
SQL Server MVP
"Kannan" <Kannanmca@.gmail.com> wrote in message
news:1134591179.063554.66800@.g14g2000cwa.googlegro ups.com...
> Its SQL server 2000.
> Its not a single proc that runs for 500 seconds its becuse the same
> procedure is called 500 times with different parameters.
> As I mentioned if you run the stored proc once it wont even run for a
> second.
> There are applications which take input from users and invoke my stored
> procedure , The user may enter one value or 500 value.
> If the user enters 500 values then the application calls my stored proc
> 500 times one after another.
> That is what is causing a problem , So I created another proc which can
> take any number of parameters and then invoke my orignal proc .
> Like exec super_proc a,b,c will invoke
> exec original_proc 'a'
> exec original_proc 'b'
> exec original_proc 'c'
> Here again SQL server starts executing the next proc after it finishes
> first.
> I dont want sql server to execute serially but paralelly.
> This explains why the load and memory are not utilized fully.
> regards
> Kannan
>
|||I used one second just to illustrate my point. It actually runs in
milliseconds as u have mentioned.
I am not sure if i can post the code / Let me check on this .
will opening multiple connections from end application help ? multiple
connections will be run without any wait time right.
In other words if I run the same proc from two places at the same time
then the second proc will not wait for first one to complete right ?
This is what I want to achive using one connection !.
Kannan
|||>I used one second just to illustrate my point. It actually runs in
> milliseconds as u have mentioned.
Is the 500 seconds total elapsed time accurate? Total elapsed time should
be roughly the sum the proc duration plus application processing time. So,
if you run a proc 500 times at an average of 10 ms. each, total duration
ought to be about 5 seconds.
> will opening multiple connections from end application help ? multiple
> connections will be run without any wait time right.
> In other words if I run the same proc from two places at the same time
> then the second proc will not wait for first one to complete right ?
> This is what I want to achive using one connection !.
There should be very little 'wait' time between proc executions on a single
connection. Perhaps a little latency but with only 500 executions, it
shouldn't add up to more than a few milliseconds total.
Multiple connections (multi-threaded processing) might help if you are not
resource constrained but you really need to know the cause of the problem is
before you develop a solution.
> I am not sure if i can post the code / Let me check on this .
The code might not be needed if the proc only runs in few milliseconds.
There's something else going on if the total elapsed time is high.
Hope this helps.
Dan Guzman
SQL Server MVP
"Kannan" <Kannanmca@.gmail.com> wrote in message
news:1134594222.338716.212980@.g43g2000cwa.googlegr oups.com...
>I used one second just to illustrate my point. It actually runs in
> milliseconds as u have mentioned.
> I am not sure if i can post the code / Let me check on this .
> will opening multiple connections from end application help ? multiple
> connections will be run without any wait time right.
> In other words if I run the same proc from two places at the same time
> then the second proc will not wait for first one to complete right ?
> This is what I want to achive using one connection !.
> Kannan
>
Run two stored procs in parallel
Hi
I have a simple stored proc which runs in less than a second.
This stored proc calculates different values based on parameters
passed.
For example sp_name "test 1 ' and
sp_name 'test 2 ' are totally different.
Now The issue is this stored proc is called more than 500 times in some
applications.
So these applications run for 500+ seconds . Although load on sql
server is almost negligible. Memory is also hugely available.
I need your suggestion in running these all at the same time.
In other words all 500 must be started at the same time ..there is no
need for one procedure to complete and the next to start. None of the
results are depenedent on any other results.
pls help me .
KannanIs this SQL 2000 or SQL 2005?
In 2005 is very easily accomplished using Service Broker. Instead of calling
the procedure 500 times, send 500 messages to a service that uses an
activated stored procedure. The message body would contain the arguments you
now pass in. Using the 'max_queue_readers' clause of CREATE QUEUE (see
http://msdn2.microsoft.com/en-us/library/ms190495(en-US,SQL.90).aspx) you
can control the maximum number of procedures to run in paralel.
This posting is provided "AS IS" with no warranties, and confers no rights.
HTH,
~ Remus Rusanu
SQL Service Broker
http://msdn2.microsoft.com/en-us/library/ms166043(en-US,SQL.90).aspx
"Kannan" <Kannanmca@.gmail.com> wrote in message
news:1134587293.323886.256810@.z14g2000cwz.googlegroups.com...
> Hi
> I have a simple stored proc which runs in less than a second.
> This stored proc calculates different values based on parameters
> passed.
> For example sp_name "test 1 ' and
> sp_name 'test 2 ' are totally different.
>
> Now The issue is this stored proc is called more than 500 times in some
> applications.
> So these applications run for 500+ seconds . Although load on sql
> server is almost negligible. Memory is also hugely available.
> I need your suggestion in running these all at the same time.
> In other words all 500 must be started at the same time ..there is no
> need for one procedure to complete and the next to start. None of the
> results are depenedent on any other results.
>
> pls help me .
> Kannan
>|||> So these applications run for 500+ seconds . Although load on sql
> server is almost negligible. Memory is also hugely available.
Remus provided some SQL 2005 suggestions to improve throughput but I suggest
you do root cause performance analysis rather than throw parallel processing
at the problem.
Why do the procs run so long? Disk i/o? CPU? Network utilization? Do you
have SET NOCOUNT ON in your procs? If the load on SQL Server is low and you
have no resource problem, the procs should either run very fast or you
should observe high resource utilization.
Hope this helps.
Dan Guzman
SQL Server MVP
"Kannan" <Kannanmca@.gmail.com> wrote in message
news:1134587293.323886.256810@.z14g2000cwz.googlegroups.com...
> Hi
> I have a simple stored proc which runs in less than a second.
> This stored proc calculates different values based on parameters
> passed.
> For example sp_name "test 1 ' and
> sp_name 'test 2 ' are totally different.
>
> Now The issue is this stored proc is called more than 500 times in some
> applications.
> So these applications run for 500+ seconds . Although load on sql
> server is almost negligible. Memory is also hugely available.
> I need your suggestion in running these all at the same time.
> In other words all 500 must be started at the same time ..there is no
> need for one procedure to complete and the next to start. None of the
> results are depenedent on any other results.
>
> pls help me .
> Kannan
>|||Its SQL server 2000.
Its not a single proc that runs for 500 seconds its becuse the same
procedure is called 500 times with different parameters.
As I mentioned if you run the stored proc once it wont even run for a
second.
There are applications which take input from users and invoke my stored
procedure , The user may enter one value or 500 value.
If the user enters 500 values then the application calls my stored proc
500 times one after another.
That is what is causing a problem , So I created another proc which can
take any number of parameters and then invoke my orignal proc .
Like exec super_proc a,b,c will invoke
exec original_proc 'a'
exec original_proc 'b'
exec original_proc 'c'
Here again SQL server starts executing the next proc after it finishes
first.
I dont want sql server to execute serially but paralelly.
This explains why the load and memory are not utilized fully.
regards
Kannan|||> Its not a single proc that runs for 500 seconds its becuse the same
> procedure is called 500 times with different parameters.
> As I mentioned if you run the stored proc once it wont even run for a
> second.
Yes, I gathered this from your original post. My concern is that one second
is a *very* long time. I have seen single-threaded applications repeatedly
execute an insert stored procedure several hundred times per second. If
each of your proc executions run for a second, I would expect that you would
see high resource utilization (CPU, disk or network) for the duration of the
application run. If you don't, then something is wrong. You can certainly
throw additional threads at the problem but I suspect the performance
improvement won't be as good as you would like. For example, if you are I/O
bound, parallel processing might actually hurt performance.
> If the user enters 500 values then the application calls my stored proc
> 500 times one after another.
> That is what is causing a problem , So I created another proc which can
> take any number of parameters and then invoke my orignal proc .
This might make a miniscule difference due to reduced latency but it's
obviously not the long pole in the tent. I don't think you are addressing
the root cause of your slowness. Can you provide more details on the
calculations the proc performs. Perhaps some code and DDL would help.
Hope this helps.
Dan Guzman
SQL Server MVP
"Kannan" <Kannanmca@.gmail.com> wrote in message
news:1134591179.063554.66800@.g14g2000cwa.googlegroups.com...
> Its SQL server 2000.
> Its not a single proc that runs for 500 seconds its becuse the same
> procedure is called 500 times with different parameters.
> As I mentioned if you run the stored proc once it wont even run for a
> second.
> There are applications which take input from users and invoke my stored
> procedure , The user may enter one value or 500 value.
> If the user enters 500 values then the application calls my stored proc
> 500 times one after another.
> That is what is causing a problem , So I created another proc which can
> take any number of parameters and then invoke my orignal proc .
> Like exec super_proc a,b,c will invoke
> exec original_proc 'a'
> exec original_proc 'b'
> exec original_proc 'c'
> Here again SQL server starts executing the next proc after it finishes
> first.
> I dont want sql server to execute serially but paralelly.
> This explains why the load and memory are not utilized fully.
> regards
> Kannan
>|||I used one second just to illustrate my point. It actually runs in
milliseconds as u have mentioned.
I am not sure if i can post the code / Let me check on this .
will opening multiple connections from end application help ' multiple
connections will be run without any wait time right.
In other words if I run the same proc from two places at the same time
then the second proc will not wait for first one to complete right ?
This is what I want to achive using one connection !.
Kannan|||>I used one second just to illustrate my point. It actually runs in
> milliseconds as u have mentioned.
Is the 500 seconds total elapsed time accurate? Total elapsed time should
be roughly the sum the proc duration plus application processing time. So,
if you run a proc 500 times at an average of 10 ms. each, total duration
ought to be about 5 seconds.
> will opening multiple connections from end application help ' multiple
> connections will be run without any wait time right.
> In other words if I run the same proc from two places at the same time
> then the second proc will not wait for first one to complete right ?
> This is what I want to achive using one connection !.
There should be very little 'wait' time between proc executions on a single
connection. Perhaps a little latency but with only 500 executions, it
shouldn't add up to more than a few milliseconds total.
Multiple connections (multi-threaded processing) might help if you are not
resource constrained but you really need to know the cause of the problem is
before you develop a solution.
> I am not sure if i can post the code / Let me check on this .
The code might not be needed if the proc only runs in few milliseconds.
There's something else going on if the total elapsed time is high.
Hope this helps.
Dan Guzman
SQL Server MVP
"Kannan" <Kannanmca@.gmail.com> wrote in message
news:1134594222.338716.212980@.g43g2000cwa.googlegroups.com...
>I used one second just to illustrate my point. It actually runs in
> milliseconds as u have mentioned.
> I am not sure if i can post the code / Let me check on this .
> will opening multiple connections from end application help ' multiple
> connections will be run without any wait time right.
> In other words if I run the same proc from two places at the same time
> then the second proc will not wait for first one to complete right ?
> This is what I want to achive using one connection !.
> Kannan
>
I have a simple stored proc which runs in less than a second.
This stored proc calculates different values based on parameters
passed.
For example sp_name "test 1 ' and
sp_name 'test 2 ' are totally different.
Now The issue is this stored proc is called more than 500 times in some
applications.
So these applications run for 500+ seconds . Although load on sql
server is almost negligible. Memory is also hugely available.
I need your suggestion in running these all at the same time.
In other words all 500 must be started at the same time ..there is no
need for one procedure to complete and the next to start. None of the
results are depenedent on any other results.
pls help me .
KannanIs this SQL 2000 or SQL 2005?
In 2005 is very easily accomplished using Service Broker. Instead of calling
the procedure 500 times, send 500 messages to a service that uses an
activated stored procedure. The message body would contain the arguments you
now pass in. Using the 'max_queue_readers' clause of CREATE QUEUE (see
http://msdn2.microsoft.com/en-us/library/ms190495(en-US,SQL.90).aspx) you
can control the maximum number of procedures to run in paralel.
This posting is provided "AS IS" with no warranties, and confers no rights.
HTH,
~ Remus Rusanu
SQL Service Broker
http://msdn2.microsoft.com/en-us/library/ms166043(en-US,SQL.90).aspx
"Kannan" <Kannanmca@.gmail.com> wrote in message
news:1134587293.323886.256810@.z14g2000cwz.googlegroups.com...
> Hi
> I have a simple stored proc which runs in less than a second.
> This stored proc calculates different values based on parameters
> passed.
> For example sp_name "test 1 ' and
> sp_name 'test 2 ' are totally different.
>
> Now The issue is this stored proc is called more than 500 times in some
> applications.
> So these applications run for 500+ seconds . Although load on sql
> server is almost negligible. Memory is also hugely available.
> I need your suggestion in running these all at the same time.
> In other words all 500 must be started at the same time ..there is no
> need for one procedure to complete and the next to start. None of the
> results are depenedent on any other results.
>
> pls help me .
> Kannan
>|||> So these applications run for 500+ seconds . Although load on sql
> server is almost negligible. Memory is also hugely available.
Remus provided some SQL 2005 suggestions to improve throughput but I suggest
you do root cause performance analysis rather than throw parallel processing
at the problem.
Why do the procs run so long? Disk i/o? CPU? Network utilization? Do you
have SET NOCOUNT ON in your procs? If the load on SQL Server is low and you
have no resource problem, the procs should either run very fast or you
should observe high resource utilization.
Hope this helps.
Dan Guzman
SQL Server MVP
"Kannan" <Kannanmca@.gmail.com> wrote in message
news:1134587293.323886.256810@.z14g2000cwz.googlegroups.com...
> Hi
> I have a simple stored proc which runs in less than a second.
> This stored proc calculates different values based on parameters
> passed.
> For example sp_name "test 1 ' and
> sp_name 'test 2 ' are totally different.
>
> Now The issue is this stored proc is called more than 500 times in some
> applications.
> So these applications run for 500+ seconds . Although load on sql
> server is almost negligible. Memory is also hugely available.
> I need your suggestion in running these all at the same time.
> In other words all 500 must be started at the same time ..there is no
> need for one procedure to complete and the next to start. None of the
> results are depenedent on any other results.
>
> pls help me .
> Kannan
>|||Its SQL server 2000.
Its not a single proc that runs for 500 seconds its becuse the same
procedure is called 500 times with different parameters.
As I mentioned if you run the stored proc once it wont even run for a
second.
There are applications which take input from users and invoke my stored
procedure , The user may enter one value or 500 value.
If the user enters 500 values then the application calls my stored proc
500 times one after another.
That is what is causing a problem , So I created another proc which can
take any number of parameters and then invoke my orignal proc .
Like exec super_proc a,b,c will invoke
exec original_proc 'a'
exec original_proc 'b'
exec original_proc 'c'
Here again SQL server starts executing the next proc after it finishes
first.
I dont want sql server to execute serially but paralelly.
This explains why the load and memory are not utilized fully.
regards
Kannan|||> Its not a single proc that runs for 500 seconds its becuse the same
> procedure is called 500 times with different parameters.
> As I mentioned if you run the stored proc once it wont even run for a
> second.
Yes, I gathered this from your original post. My concern is that one second
is a *very* long time. I have seen single-threaded applications repeatedly
execute an insert stored procedure several hundred times per second. If
each of your proc executions run for a second, I would expect that you would
see high resource utilization (CPU, disk or network) for the duration of the
application run. If you don't, then something is wrong. You can certainly
throw additional threads at the problem but I suspect the performance
improvement won't be as good as you would like. For example, if you are I/O
bound, parallel processing might actually hurt performance.
> If the user enters 500 values then the application calls my stored proc
> 500 times one after another.
> That is what is causing a problem , So I created another proc which can
> take any number of parameters and then invoke my orignal proc .
This might make a miniscule difference due to reduced latency but it's
obviously not the long pole in the tent. I don't think you are addressing
the root cause of your slowness. Can you provide more details on the
calculations the proc performs. Perhaps some code and DDL would help.
Hope this helps.
Dan Guzman
SQL Server MVP
"Kannan" <Kannanmca@.gmail.com> wrote in message
news:1134591179.063554.66800@.g14g2000cwa.googlegroups.com...
> Its SQL server 2000.
> Its not a single proc that runs for 500 seconds its becuse the same
> procedure is called 500 times with different parameters.
> As I mentioned if you run the stored proc once it wont even run for a
> second.
> There are applications which take input from users and invoke my stored
> procedure , The user may enter one value or 500 value.
> If the user enters 500 values then the application calls my stored proc
> 500 times one after another.
> That is what is causing a problem , So I created another proc which can
> take any number of parameters and then invoke my orignal proc .
> Like exec super_proc a,b,c will invoke
> exec original_proc 'a'
> exec original_proc 'b'
> exec original_proc 'c'
> Here again SQL server starts executing the next proc after it finishes
> first.
> I dont want sql server to execute serially but paralelly.
> This explains why the load and memory are not utilized fully.
> regards
> Kannan
>|||I used one second just to illustrate my point. It actually runs in
milliseconds as u have mentioned.
I am not sure if i can post the code / Let me check on this .
will opening multiple connections from end application help ' multiple
connections will be run without any wait time right.
In other words if I run the same proc from two places at the same time
then the second proc will not wait for first one to complete right ?
This is what I want to achive using one connection !.
Kannan|||>I used one second just to illustrate my point. It actually runs in
> milliseconds as u have mentioned.
Is the 500 seconds total elapsed time accurate? Total elapsed time should
be roughly the sum the proc duration plus application processing time. So,
if you run a proc 500 times at an average of 10 ms. each, total duration
ought to be about 5 seconds.
> will opening multiple connections from end application help ' multiple
> connections will be run without any wait time right.
> In other words if I run the same proc from two places at the same time
> then the second proc will not wait for first one to complete right ?
> This is what I want to achive using one connection !.
There should be very little 'wait' time between proc executions on a single
connection. Perhaps a little latency but with only 500 executions, it
shouldn't add up to more than a few milliseconds total.
Multiple connections (multi-threaded processing) might help if you are not
resource constrained but you really need to know the cause of the problem is
before you develop a solution.
> I am not sure if i can post the code / Let me check on this .
The code might not be needed if the proc only runs in few milliseconds.
There's something else going on if the total elapsed time is high.
Hope this helps.
Dan Guzman
SQL Server MVP
"Kannan" <Kannanmca@.gmail.com> wrote in message
news:1134594222.338716.212980@.g43g2000cwa.googlegroups.com...
>I used one second just to illustrate my point. It actually runs in
> milliseconds as u have mentioned.
> I am not sure if i can post the code / Let me check on this .
> will opening multiple connections from end application help ' multiple
> connections will be run without any wait time right.
> In other words if I run the same proc from two places at the same time
> then the second proc will not wait for first one to complete right ?
> This is what I want to achive using one connection !.
> Kannan
>
Monday, March 12, 2012
Run jobs in SELECT CASE?
Hello!
Is that possible to call a job using SELECT CASE statement? I am trying
to run some jobs based on some cases in my stored procedure. See below
the code:
select case RptName
when 'A' then [msdb].[dbo].[sp_start_job] @.job_name = 'A'
when 'B' then [msdb].[dbo].[sp_start_job] @.job_name = 'B'
when 'C' then [msdb].[dbo].[sp_start_job] @.job_name = 'C'
when 'D' then [msdb].[dbo].[sp_start_job] @.job_name = 'D'
end
from Table
Trying not to use IF-ELSE statement (which I have tried and it is
working fine).
Thanks for your help!
*** Sent via Developersdex http://www.examnotes.net ***>> Trying not to use IF-ELSE statement
SELECT statement returns a resultset, it is not not meant to execute
procedures. CASE is not supposed to be used as you have suggested. It
returns a scalar value.
Each sp_start_job invocation is a separate statement. Use IF.. ELSE
construct to execute them conditionally.
Anith|||In T-SQL, there is no [select case ..] statement. Instead, [case.. when..
then.. end] is an expression, so you can't execute a procedure from it, but
you can call functions.
However, this would seem to do what you want:
select @.RptName = RptName from Table
if @.RptName = 'A' exec sp_start_job @.job_name = 'A'
if @.RptName = 'B' exec sp_start_job @.job_name = 'B'
Or, looking at your example, it seems that perhaps just this would work:
exec sp_start_job @.job_name = @.RptName
"Test Test" <farooqhs_2000@.yahoo.com> wrote in message
news:eWaWmjaBGHA.1864@.TK2MSFTNGP12.phx.gbl...
> Hello!
> Is that possible to call a job using SELECT CASE statement? I am trying
> to run some jobs based on some cases in my stored procedure. See below
> the code:
> select case RptName
> when 'A' then [msdb].[dbo].[sp_start_job] @.job_name = 'A'
> when 'B' then [msdb].[dbo].[sp_start_job] @.job_name = 'B'
> when 'C' then [msdb].[dbo].[sp_start_job] @.job_name = 'C'
> when 'D' then [msdb].[dbo].[sp_start_job] @.job_name = 'D'
> end
> from Table
> Trying not to use IF-ELSE statement (which I have tried and it is
> working fine).
> Thanks for your help!
>
> *** Sent via Developersdex http://www.examnotes.net ***|||Thanks, Anith.
*** Sent via Developersdex http://www.examnotes.net ***|||But then so would...
select @.RptName = RptName from Table
exec sp_start_job @.job_name = @.RptName
Just remember to keep the RptName matching the Job name.
Colin Dawson
www.cjdawson.com
"JT" <someone@.microsoft.com> wrote in message
news:OwGor8aBGHA.1864@.TK2MSFTNGP12.phx.gbl...
> In T-SQL, there is no [select case ..] statement. Instead, [case.. when..
> then.. end] is an expression, so you can't execute a procedure from it,
> but you can call functions.
> However, this would seem to do what you want:
> select @.RptName = RptName from Table
> if @.RptName = 'A' exec sp_start_job @.job_name = 'A'
> if @.RptName = 'B' exec sp_start_job @.job_name = 'B'
> Or, looking at your example, it seems that perhaps just this would work:
> exec sp_start_job @.job_name = @.RptName
>
> "Test Test" <farooqhs_2000@.yahoo.com> wrote in message
> news:eWaWmjaBGHA.1864@.TK2MSFTNGP12.phx.gbl...
>
Is that possible to call a job using SELECT CASE statement? I am trying
to run some jobs based on some cases in my stored procedure. See below
the code:
select case RptName
when 'A' then [msdb].[dbo].[sp_start_job] @.job_name = 'A'
when 'B' then [msdb].[dbo].[sp_start_job] @.job_name = 'B'
when 'C' then [msdb].[dbo].[sp_start_job] @.job_name = 'C'
when 'D' then [msdb].[dbo].[sp_start_job] @.job_name = 'D'
end
from Table
Trying not to use IF-ELSE statement (which I have tried and it is
working fine).
Thanks for your help!
*** Sent via Developersdex http://www.examnotes.net ***>> Trying not to use IF-ELSE statement
SELECT statement returns a resultset, it is not not meant to execute
procedures. CASE is not supposed to be used as you have suggested. It
returns a scalar value.
Each sp_start_job invocation is a separate statement. Use IF.. ELSE
construct to execute them conditionally.
Anith|||In T-SQL, there is no [select case ..] statement. Instead, [case.. when..
then.. end] is an expression, so you can't execute a procedure from it, but
you can call functions.
However, this would seem to do what you want:
select @.RptName = RptName from Table
if @.RptName = 'A' exec sp_start_job @.job_name = 'A'
if @.RptName = 'B' exec sp_start_job @.job_name = 'B'
Or, looking at your example, it seems that perhaps just this would work:
exec sp_start_job @.job_name = @.RptName
"Test Test" <farooqhs_2000@.yahoo.com> wrote in message
news:eWaWmjaBGHA.1864@.TK2MSFTNGP12.phx.gbl...
> Hello!
> Is that possible to call a job using SELECT CASE statement? I am trying
> to run some jobs based on some cases in my stored procedure. See below
> the code:
> select case RptName
> when 'A' then [msdb].[dbo].[sp_start_job] @.job_name = 'A'
> when 'B' then [msdb].[dbo].[sp_start_job] @.job_name = 'B'
> when 'C' then [msdb].[dbo].[sp_start_job] @.job_name = 'C'
> when 'D' then [msdb].[dbo].[sp_start_job] @.job_name = 'D'
> end
> from Table
> Trying not to use IF-ELSE statement (which I have tried and it is
> working fine).
> Thanks for your help!
>
> *** Sent via Developersdex http://www.examnotes.net ***|||Thanks, Anith.
*** Sent via Developersdex http://www.examnotes.net ***|||But then so would...
select @.RptName = RptName from Table
exec sp_start_job @.job_name = @.RptName
Just remember to keep the RptName matching the Job name.
Colin Dawson
www.cjdawson.com
"JT" <someone@.microsoft.com> wrote in message
news:OwGor8aBGHA.1864@.TK2MSFTNGP12.phx.gbl...
> In T-SQL, there is no [select case ..] statement. Instead, [case.. when..
> then.. end] is an expression, so you can't execute a procedure from it,
> but you can call functions.
> However, this would seem to do what you want:
> select @.RptName = RptName from Table
> if @.RptName = 'A' exec sp_start_job @.job_name = 'A'
> if @.RptName = 'B' exec sp_start_job @.job_name = 'B'
> Or, looking at your example, it seems that perhaps just this would work:
> exec sp_start_job @.job_name = @.RptName
>
> "Test Test" <farooqhs_2000@.yahoo.com> wrote in message
> news:eWaWmjaBGHA.1864@.TK2MSFTNGP12.phx.gbl...
>
Friday, March 9, 2012
Run DTS Package based on a Variable
I'm trying to run a DTS package based on the result of a partcular
query.
SELECT SUM(Bal_Orig_Curr) AS bal
INTO tempbal
FROM Gw078p
I want to run the rest of the package only if the value of "bal" is
equal to zero otherwise generate an email. How can create this split?
ThanksYou could store the results of the query in a global variable. After that, a
vbscript task can create the branching logic by updating the precedence
constraints.
Please see http://www.sqldts.com/214.aspx for more info. Much easier in SSIS
as the precedence constraints themselves can be based on an expression in
the GUI.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
query.
SELECT SUM(Bal_Orig_Curr) AS bal
INTO tempbal
FROM Gw078p
I want to run the rest of the package only if the value of "bal" is
equal to zero otherwise generate an email. How can create this split?
ThanksYou could store the results of the query in a global variable. After that, a
vbscript task can create the branching logic by updating the precedence
constraints.
Please see http://www.sqldts.com/214.aspx for more info. Much easier in SSIS
as the precedence constraints themselves can be based on an expression in
the GUI.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
Run DTS Package based on a Variable
I'm trying to run a DTS package based on the result of a partcular
query.
SELECT SUM(Bal_Orig_Curr) AS bal
INTO tempbal
FROM Gw078p
I want to run the rest of the package only if the value of "bal" is
equal to zero otherwise generate an email. How can create this split?
Thanks
You could store the results of the query in a global variable. After that, a
vbscript task can create the branching logic by updating the precedence
constraints.
Please see http://www.sqldts.com/214.aspx for more info. Much easier in SSIS
as the precedence constraints themselves can be based on an expression in
the GUI.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
query.
SELECT SUM(Bal_Orig_Curr) AS bal
INTO tempbal
FROM Gw078p
I want to run the rest of the package only if the value of "bal" is
equal to zero otherwise generate an email. How can create this split?
Thanks
You could store the results of the query in a global variable. After that, a
vbscript task can create the branching logic by updating the precedence
constraints.
Please see http://www.sqldts.com/214.aspx for more info. Much easier in SSIS
as the precedence constraints themselves can be based on an expression in
the GUI.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
Run DTS Package based on a Variable
I'm trying to run a DTS package based on the result of a partcular
query.
SELECT SUM(Bal_Orig_Curr) AS bal
INTO tempbal
FROM Gw078p
I want to run the rest of the package only if the value of "bal" is
equal to zero otherwise generate an email. How can create this split?
ThanksYou could store the results of the query in a global variable. After that, a
vbscript task can create the branching logic by updating the precedence
constraints.
Please see http://www.sqldts.com/214.aspx for more info. Much easier in SSIS
as the precedence constraints themselves can be based on an expression in
the GUI.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
query.
SELECT SUM(Bal_Orig_Curr) AS bal
INTO tempbal
FROM Gw078p
I want to run the rest of the package only if the value of "bal" is
equal to zero otherwise generate an email. How can create this split?
ThanksYou could store the results of the query in a global variable. After that, a
vbscript task can create the branching logic by updating the precedence
constraints.
Please see http://www.sqldts.com/214.aspx for more info. Much easier in SSIS
as the precedence constraints themselves can be based on an expression in
the GUI.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
Wednesday, March 7, 2012
run a Package from package
I have a DTS package that executes a procedure returns a global variable.
In the next ActiveX task (vb) I'd like to examine the variable and based on its value run other DTS packages but I do not know how to set up the code to run a DTS package from within an ActiveX script.
Any help appreciated .
SteveGo to Start > Run and type DTSRUNUI
Type in the SQL Server connection info at the bottom
Click the [...] button at the to choose the package name. Click [Advanced]
Click the [Generate] button
To the left of the [Generate] button, you will see the command to run the DTS from command line.
Saturday, February 25, 2012
Rules based Configuration ER design
I'm looking at a head start in developing a "Rules based configuration
system." One like Dell Computer has where you build your PC. Are there any
database designs available for this type of thing?
Regards,
Gary Blakely
Hello Gary,
Since rules based system is too general and you may want to be more
specific.
A very simple sample, let's say you have 3 configuration parameters and 2
rules. 1 rule has some relation to all 3 parameters. The tables shall be
tbl-rule
ruleid rulename ..
1rule1
tbl-parameters
paramid paramname ..
1p1
tbl-rule-parm-relation
ruleid paramid value relation
1110>
125<
Some more complex situation might be based on knowledge management, expert
system etc which is beyond a simple E-R desgin.
Some issues may require a bit more in depth attention and may fall under
the umbrella of Advisory Services. Microsoft now offers short-term and
proactive assistance for specific planning, design, development or
assistance with installing, deploying, and general "how to" advice via
telephone. For more information:
http://support.microsoft.com/default.aspx?scid=fh;en-us;advisoryservice
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
<http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
<http://msdn.microsoft.com/subscriptions/support/default.aspx>.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
system." One like Dell Computer has where you build your PC. Are there any
database designs available for this type of thing?
Regards,
Gary Blakely
Hello Gary,
Since rules based system is too general and you may want to be more
specific.
A very simple sample, let's say you have 3 configuration parameters and 2
rules. 1 rule has some relation to all 3 parameters. The tables shall be
tbl-rule
ruleid rulename ..
1rule1
tbl-parameters
paramid paramname ..
1p1
tbl-rule-parm-relation
ruleid paramid value relation
1110>
125<
Some more complex situation might be based on knowledge management, expert
system etc which is beyond a simple E-R desgin.
Some issues may require a bit more in depth attention and may fall under
the umbrella of Advisory Services. Microsoft now offers short-term and
proactive assistance for specific planning, design, development or
assistance with installing, deploying, and general "how to" advice via
telephone. For more information:
http://support.microsoft.com/default.aspx?scid=fh;en-us;advisoryservice
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
<http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
<http://msdn.microsoft.com/subscriptions/support/default.aspx>.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
Rules based Configuration ER design
I'm looking at a head start in developing a "Rules based configuration
system." One like Dell Computer has where you build your PC. Are there any
database designs available for this type of thing?
Regards,
Gary BlakelyHello Gary,
Since rules based system is too general and you may want to be more
specific.
A very simple sample, let's say you have 3 configuration parameters and 2
rules. 1 rule has some relation to all 3 parameters. The tables shall be
tbl-rule
ruleid rulename ..
1 rule1
tbl-parameters
paramid paramname ..
1 p1
tbl-rule-parm-relation
ruleid paramid value relation
1 1 10 >
1 2 5 <
Some more complex situation might be based on knowledge management, expert
system etc which is beyond a simple E-R desgin.
Some issues may require a bit more in depth attention and may fall under
the umbrella of Advisory Services. Microsoft now offers short-term and
proactive assistance for specific planning, design, development or
assistance with installing, deploying, and general "how to" advice via
telephone. For more information:
http://support.microsoft.com/defaul...advisoryservice
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Community Support
========================================
==========
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscript...ault.aspx#notif
ications
<http://msdn.microsoft.com/subscript...ps/default.aspx>.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
<http://msdn.microsoft.com/subscript...rt/default.aspx>.
========================================
==========
This posting is provided "AS IS" with no warranties, and confers no rights.
system." One like Dell Computer has where you build your PC. Are there any
database designs available for this type of thing?
Regards,
Gary BlakelyHello Gary,
Since rules based system is too general and you may want to be more
specific.
A very simple sample, let's say you have 3 configuration parameters and 2
rules. 1 rule has some relation to all 3 parameters. The tables shall be
tbl-rule
ruleid rulename ..
1 rule1
tbl-parameters
paramid paramname ..
1 p1
tbl-rule-parm-relation
ruleid paramid value relation
1 1 10 >
1 2 5 <
Some more complex situation might be based on knowledge management, expert
system etc which is beyond a simple E-R desgin.
Some issues may require a bit more in depth attention and may fall under
the umbrella of Advisory Services. Microsoft now offers short-term and
proactive assistance for specific planning, design, development or
assistance with installing, deploying, and general "how to" advice via
telephone. For more information:
http://support.microsoft.com/defaul...advisoryservice
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Community Support
========================================
==========
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscript...ault.aspx#notif
ications
<http://msdn.microsoft.com/subscript...ps/default.aspx>.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
<http://msdn.microsoft.com/subscript...rt/default.aspx>.
========================================
==========
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to:
Posts (Atom)