Showing posts with label jobs. Show all posts
Showing posts with label jobs. Show all posts

Sunday, February 19, 2012

Best way to schedule a package to run during the day

Hi,

What is the best way to schedule a package to run every 30 minutes during the day. Would it be using SQL Agent Jobs? If so, what is the things I need to consider.

Thank you,

Aldo

Hi ya,

Yes it would be Sql Server Agent job. You would need to make the package and then deploy it to either Sql Server or File system. You will get errors if the Agent credentials running agent service is different then your package credentials. If that is the case search for either Sql Agent proxy or SSIS jobs not running in Sql Server agent and you will find loads of posts.

The rest is pretty easy. You would create a new job in agent and then for daily frequency put it as 30 minutes.

Hope this helps


Cheers

Rizwan

|||Thanks you!

Thursday, February 16, 2012

Best way to maintain up to date SQL Jobs and SSIS on failover Serv

Hi,
on SQL 2005 we use log shipping to maintain our production server to an
alternate server. Now I would like to do something similar with our SQL
Agent jobs and SSIS. While those jobs are enabled on the production server,
I would like them to become disable on the alternate server, this process
would be scheduled once per day.
I'm sure there are many ways to achieve this, but I am wondering what would
be the most efficient.
any ideas ?
Thanks
Fred
ok, I just figured out how to transfer/disable jobs using the Transfer Job
task in SSIS, it's quite nice actually.
But, I am still in the dark on how to transfer SSIS from one server to
another.
BTW, a backup and restore of MSDB is out of the question.
Thanks
"FredDBA" wrote:

> Hi,
> on SQL 2005 we use log shipping to maintain our production server to an
> alternate server. Now I would like to do something similar with our SQL
> Agent jobs and SSIS. While those jobs are enabled on the production server,
> I would like them to become disable on the alternate server, this process
> would be scheduled once per day.
> I'm sure there are many ways to achieve this, but I am wondering what would
> be the most efficient.
> any ideas ?
> Thanks
> Fred

Best way to maintain up to date SQL Jobs and SSIS on failover Serv

Hi,
on SQL 2005 we use log shipping to maintain our production server to an
alternate server. Now I would like to do something similar with our SQL
Agent jobs and SSIS. While those jobs are enabled on the production server,
I would like them to become disable on the alternate server, this process
would be scheduled once per day.
I'm sure there are many ways to achieve this, but I am wondering what would
be the most efficient.
any ideas ?
Thanks
Fredok, I just figured out how to transfer/disable jobs using the Transfer Job
task in SSIS, it's quite nice actually.
But, I am still in the dark on how to transfer SSIS from one server to
another.
BTW, a backup and restore of MSDB is out of the question.
Thanks
"FredDBA" wrote:

> Hi,
> on SQL 2005 we use log shipping to maintain our production server to an
> alternate server. Now I would like to do something similar with our SQL
> Agent jobs and SSIS. While those jobs are enabled on the production serve
r,
> I would like them to become disable on the alternate server, this process
> would be scheduled once per day.
> I'm sure there are many ways to achieve this, but I am wondering what woul
d
> be the most efficient.
> any ideas ?
> Thanks
> Fred|||If its not too late, consider storing your SSIS packages in the
filesystem and just keep copies on your DR machines
Terry|||Anotther thing we do here (mostly for legacy dts packages) is to
restore the MSDB as another name. During DR, rename that database to
MSDB and all the objects will be there.
Terry

Best way to maintain up to date SQL Jobs and SSIS on failover Serv

Hi,
on SQL 2005 we use log shipping to maintain our production server to an
alternate server. Now I would like to do something similar with our SQL
Agent jobs and SSIS. While those jobs are enabled on the production server,
I would like them to become disable on the alternate server, this process
would be scheduled once per day.
I'm sure there are many ways to achieve this, but I am wondering what would
be the most efficient.
any ideas ?
Thanks
Fredok, I just figured out how to transfer/disable jobs using the Transfer Job
task in SSIS, it's quite nice actually.
But, I am still in the dark on how to transfer SSIS from one server to
another.
BTW, a backup and restore of MSDB is out of the question.
Thanks
"FredDBA" wrote:
> Hi,
> on SQL 2005 we use log shipping to maintain our production server to an
> alternate server. Now I would like to do something similar with our SQL
> Agent jobs and SSIS. While those jobs are enabled on the production server,
> I would like them to become disable on the alternate server, this process
> would be scheduled once per day.
> I'm sure there are many ways to achieve this, but I am wondering what would
> be the most efficient.
> any ideas ?
> Thanks
> Fred|||If its not too late, consider storing your SSIS packages in the
filesystem and just keep copies on your DR machines
Terry|||Anotther thing we do here (mostly for legacy dts packages) is to
restore the MSDB as another name. During DR, rename that database to
MSDB and all the objects will be there.
Terry

Tuesday, February 14, 2012

Best way to keep track of SQL server changes...!

What would be the best practice to follow to keep track of MS SQL
server changes... Stroed procs, tables, views, triggers, indexes, DTS
and also jobs ect...
I am not quite sure how Source safe works with sql server. Any other
way to do this... Even if its manual work, its okey.. I would
appreciate if any of the DBA's let me know how they are facing this
issue...
Thanks in advance...
Hi,
Have you thought about server side tracing?
If you do not wish to do the above and is ready to spend some money, then
there are few third-party tools available in the market, For ex: Red-gate.
Thanks
Yogish
|||check out www.dbghost.com for SQL Server database change management with
source control intergration.
"SQLDBA" wrote:

> What would be the best practice to follow to keep track of MS SQL
> server changes... Stroed procs, tables, views, triggers, indexes, DTS
> and also jobs ect...
> I am not quite sure how Source safe works with sql server. Any other
> way to do this... Even if its manual work, its okey.. I would
> appreciate if any of the DBA's let me know how they are facing this
> issue...
> Thanks in advance...
>

Best way to keep track of SQL server changes...!

What would be the best practice to follow to keep track of MS SQL
server changes... Stroed procs, tables, views, triggers, indexes, DTS
and also jobs ect...
I am not quite sure how Source safe works with sql server. Any other
way to do this... Even if its manual work, its okey.. I would
appreciate if any of the DBA's let me know how they are facing this
issue...
Thanks in advance...Hi,
Have you thought about server side tracing?
If you do not wish to do the above and is ready to spend some money, then
there are few third-party tools available in the market, For ex: Red-gate.
Thanks
Yogish|||check out www.dbghost.com for SQL Server database change management with
source control intergration.
"SQLDBA" wrote:

> What would be the best practice to follow to keep track of MS SQL
> server changes... Stroed procs, tables, views, triggers, indexes, DTS
> and also jobs ect...
> I am not quite sure how Source safe works with sql server. Any other
> way to do this... Even if its manual work, its okey.. I would
> appreciate if any of the DBA's let me know how they are facing this
> issue...
> Thanks in advance...
>

Best way to keep track of SQL server changes...!

What would be the best practice to follow to keep track of MS SQL
server changes... Stroed procs, tables, views, triggers, indexes, DTS
and also jobs ect...
I am not quite sure how Source safe works with sql server. Any other
way to do this... Even if its manual work, its okey.. I would
appreciate if any of the DBA's let me know how they are facing this
issue...
Thanks in advance...Hi,
Have you thought about server side tracing?
If you do not wish to do the above and is ready to spend some money, then
there are few third-party tools available in the market, For ex: Red-gate.
--
Thanks
Yogish|||check out www.dbghost.com for SQL Server database change management with
source control intergration.
"SQLDBA" wrote:
> What would be the best practice to follow to keep track of MS SQL
> server changes... Stroed procs, tables, views, triggers, indexes, DTS
> and also jobs ect...
> I am not quite sure how Source safe works with sql server. Any other
> way to do this... Even if its manual work, its okey.. I would
> appreciate if any of the DBA's let me know how they are facing this
> issue...
> Thanks in advance...
>

Best way to keep track of SQL Server Changes

What would be the best practice to follow to keep track of MS SQL
server changes... Stroed procs, tables, views, triggers, indexes, DTS
and also jobs ect...

I am not quite sure how Source safe works with sql server. Any other
way to do this... Even if its manual work, its okey.. I would
appreciate if any of the DBA's let me know how they are facing this
issue...

Thanks in advance..."SQLDBA" <pg.242w@.gmail.com> wrote in message
news:1104953120.142642.99410@.z14g2000cwz.googlegro ups.com...
> What would be the best practice to follow to keep track of MS SQL
> server changes... Stroed procs, tables, views, triggers, indexes, DTS
> and also jobs ect...
> I am not quite sure how Source safe works with sql server. Any other
> way to do this... Even if its manual work, its okey.. I would
> appreciate if any of the DBA's let me know how they are facing this
> issue...
> Thanks in advance...

There's lot of information on the web - Google 'sql 2000 source control' or
something similar to find more information. You might also want to check out
the thread in this group from yesterday called 'Backing up design changes',
as well as this approach from Erland:

http://www.abaris.se/abaperls/index.html

To get started quickly, you can script your objects to files using
Enterprise Manager, check them all in to VSS, then start using source
control for all changes. You'll need to do some basic work on source control
processes, but there's lot of stuff on the web, and you may already have
something in your organization that you can re-use.

It's also very useful to have some sort of comparison tool (I've used Red
Gate's SQL Compare before) to check the differences between databases, and
synchronize them as needed.

DTS is a bit more problematic, because packages are binary objects, not text
files, but DTS does support multiple package versions anyway, so you might
just decide to keep the last 5 versions in a package or whatever.

Simon|||Thank you very much... We do have VSS but my knowledge in VSS is
limited. So I would appreciate if you could give me a drill down on how
I can set it up. Is there any way I can link these scripts to SQL
Server objects so that everytime when someone try to make any changes
to these scripts, it needs to be checked out to get modified? Because I
need to enforce a method among the developers to follow...!|||SQLDBA (pg.242w@.gmail.com) writes:
> Thank you very much... We do have VSS but my knowledge in VSS is
> limited. So I would appreciate if you could give me a drill down on how
> I can set it up. Is there any way I can link these scripts to SQL
> Server objects so that everytime when someone try to make any changes
> to these scripts, it needs to be checked out to get modified? Because I
> need to enforce a method among the developers to follow...!

There might be means to in Visual Studio.

But in my opinion, that's flawed. Checking out - and in - should be
a concious decision, and the source for the check-in should be a file,
not an object in a database.

That's the core of configuration management: if you need to change a
file, you go the version-control system and check it out, do your
change, and then check it in. If the change is not in the version-
control system, it does simply not exists. All builds and deployments
are made from the version-control system.

Of course, if there is only one development database, this policy may
be somewhat difficult to enforce, not the least if people use tools
like Query Analyzer where it's easier to load a stored procedure to
the database than saving it to disk.

In our shop there are an unknown number of development databases, so it
becomes quite apparent that there must be a central clearinghouse for
the code, and that is is SourceSafe.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Thank you all for your input. In my situation, I just need to enforce
some good practice methodology among the developers. We already have
some third party tool (Redgate SQL compare) that does a wonderful job
in migrating changes among different databases.. This is just to keep
track of who is changing what and to keep the process going without any
flaws... So anyone has any suggestions to a situation like this?
Thanks again..!

Sunday, February 12, 2012

best way to delete the reporting services jobs in sqlserver

I have six thousand reporting services jobs in sqlserver, which were
scheduled to run only once and their execution date is older than a month.
how do I know which of the jobs are useful out of these 6000.
Can I write a job, to purge the reporting services jobs older than a month
and schedule it to run every week, basically how do I manage these ever
growing jobs ?
Thanks in advance..GAis it okay to delete the subscriptions like below '
delete from reportserver..subscriptions
WHERE ModifiedDate < dateadd(day, -7, getdate()) AND Description LIKE 'SRS%'
TIA
"DallasBlue" wrote:
> I have six thousand reporting services jobs in sqlserver, which were
> scheduled to run only once and their execution date is older than a month.
> how do I know which of the jobs are useful out of these 6000.
> Can I write a job, to purge the reporting services jobs older than a month
> and schedule it to run every week, basically how do I manage these ever
> growing jobs ?
>
> Thanks in advance..GA
>|||I have deleted subscriptions using this method. There are cascading deletes
when to remove the related records in ReportSchedule and Schedule tables.
Though, bulk deleting a lot of subscriptions at the same time might not work
with that statement. I know for me I've gotten timeouts when trying a direct
delete. So instead, I create a memory table (DECLARE @.x TABLE...) and put in
all the SubscriptionID for the ones I want to delete. Then I delete from the
Subscription table using a join to the memory table. I know it might seem
strange to do it that way, but because of the way the tables are indexed, it
works.
Once you the records are deleted from the tables, the Reporting Service will
automatically delete the actual SQL Agent jobs when it does its maintenance,
I'm not sure of the frequency that it does that, but at minimum its once a
day.
Carmine
"DallasBlue" wrote:
> is it okay to delete the subscriptions like below '
> delete from reportserver..subscriptions
> WHERE ModifiedDate < dateadd(day, -7, getdate()) AND Description LIKE 'SRS%'
> TIA
> "DallasBlue" wrote:
> > I have six thousand reporting services jobs in sqlserver, which were
> > scheduled to run only once and their execution date is older than a month.
> > how do I know which of the jobs are useful out of these 6000.
> > Can I write a job, to purge the reporting services jobs older than a month
> > and schedule it to run every week, basically how do I manage these ever
> > growing jobs ?
> >
> >
> > Thanks in advance..GA
> >
> >