Hello,
I have a question about stored procedures in Sql Server, when i will do replication from Sql Server to Oracle, what will happen with stored procedures, will they be replicated to along with tables and data?
Thank's in advance.
Urko
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.
you have the option to replicate them. It is unclear if Oracle will support
their creation though.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"SqlJunkies User" <User@.-NOSPAM-SqlJunkies.com> wrote in message
news:O90M1C$ZEHA.808@.tk2msftngp13.phx.gbl...
> Hello,
> I have a question about stored procedures in Sql Server, when i will do
replication from Sql Server to Oracle, what will happen with stored
procedures, will they be replicated to along with tables and data?
> Thank's in advance.
> Urko
> --
> Posted using Wimdows.net NntpNews Component -
> Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine
supports Post Alerts, Ratings, and Searching.
Showing posts with label procedures. Show all posts
Showing posts with label procedures. Show all posts
Monday, March 19, 2012
Another replication question ( Stored procedures)
I have a question, about stored procedures.
When i will do a replication from Sql Server to Oracle, what will happed with Stored Procedures, wil they replicate to?(Along with tables and data)
you have the option to replicate them. It is unclear whether Oracle will
support their creation though.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Uros" <Uros@.discussions.microsoft.com> wrote in message
news:A9F82B1D-1E93-448E-AE67-A55FA5E7FAE3@.microsoft.com...
> I have a question, about stored procedures.
> When i will do a replication from Sql Server to Oracle, what will happed
with Stored Procedures, wil they replicate to?(Along with tables and data)
>
When i will do a replication from Sql Server to Oracle, what will happed with Stored Procedures, wil they replicate to?(Along with tables and data)
you have the option to replicate them. It is unclear whether Oracle will
support their creation though.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Uros" <Uros@.discussions.microsoft.com> wrote in message
news:A9F82B1D-1E93-448E-AE67-A55FA5E7FAE3@.microsoft.com...
> I have a question, about stored procedures.
> When i will do a replication from Sql Server to Oracle, what will happed
with Stored Procedures, wil they replicate to?(Along with tables and data)
>
Sunday, March 11, 2012
Another question on backups
I have a database that takes up around 12 gigs or so that I would like
to back up to a network share.
As part of our recovery procedures, I'm also backing up the source files
that we use to create about 90% of the data on our database (the
database is a sales information system, with reports generated over the
web). There may be some data entry into the project, but it is minimal.
Is there a way to back up the things I'd need to restore the tables,
such as the data structure of them, the stored procedures that load them
and the jobs that execute those stored procedures? In other words, back
up everything but the data inside the 90% of the tables which we can
re-create on the next table load?
I'm looking for a way to whittle down the amount of data I'm backing up,
actually backing up just what I specifically need to have to get going
again.
BCscript the database and store it in Source Safe.
Greg Jackson
PDX, Oregon|||Hi,
There are 2 options for you:-
1. Use generate script to script all the objects (ALL DDLs) and right click
above the job and script the jobs.
2. Do a full database backup once and perform a differential backup daily.
For jobs backup the MSDB database.
Differential backup will backup only the changes after the last backup
and will be very fast in your case since you have very less changes
on a daily basis.
Thanks
Hari
SQL Server MVP
"Blasting Cap" <goober@.christian.net> wrote in message
news:ueeTd0ocFHA.584@.TK2MSFTNGP15.phx.gbl...
>I have a database that takes up around 12 gigs or so that I would like to
>back up to a network share.
> As part of our recovery procedures, I'm also backing up the source files
> that we use to create about 90% of the data on our database (the database
> is a sales information system, with reports generated over the web).
> There may be some data entry into the project, but it is minimal.
> Is there a way to back up the things I'd need to restore the tables, such
> as the data structure of them, the stored procedures that load them and
> the jobs that execute those stored procedures? In other words, back up
> everything but the data inside the 90% of the tables which we can
> re-create on the next table load?
> I'm looking for a way to whittle down the amount of data I'm backing up,
> actually backing up just what I specifically need to have to get going
> again.
> BC
>
to back up to a network share.
As part of our recovery procedures, I'm also backing up the source files
that we use to create about 90% of the data on our database (the
database is a sales information system, with reports generated over the
web). There may be some data entry into the project, but it is minimal.
Is there a way to back up the things I'd need to restore the tables,
such as the data structure of them, the stored procedures that load them
and the jobs that execute those stored procedures? In other words, back
up everything but the data inside the 90% of the tables which we can
re-create on the next table load?
I'm looking for a way to whittle down the amount of data I'm backing up,
actually backing up just what I specifically need to have to get going
again.
BCscript the database and store it in Source Safe.
Greg Jackson
PDX, Oregon|||Hi,
There are 2 options for you:-
1. Use generate script to script all the objects (ALL DDLs) and right click
above the job and script the jobs.
2. Do a full database backup once and perform a differential backup daily.
For jobs backup the MSDB database.
Differential backup will backup only the changes after the last backup
and will be very fast in your case since you have very less changes
on a daily basis.
Thanks
Hari
SQL Server MVP
"Blasting Cap" <goober@.christian.net> wrote in message
news:ueeTd0ocFHA.584@.TK2MSFTNGP15.phx.gbl...
>I have a database that takes up around 12 gigs or so that I would like to
>back up to a network share.
> As part of our recovery procedures, I'm also backing up the source files
> that we use to create about 90% of the data on our database (the database
> is a sales information system, with reports generated over the web).
> There may be some data entry into the project, but it is minimal.
> Is there a way to back up the things I'd need to restore the tables, such
> as the data structure of them, the stored procedures that load them and
> the jobs that execute those stored procedures? In other words, back up
> everything but the data inside the 90% of the tables which we can
> re-create on the next table load?
> I'm looking for a way to whittle down the amount of data I'm backing up,
> actually backing up just what I specifically need to have to get going
> again.
> BC
>
Another question on backups
I have a database that takes up around 12 gigs or so that I would like
to back up to a network share.
As part of our recovery procedures, I'm also backing up the source files
that we use to create about 90% of the data on our database (the
database is a sales information system, with reports generated over the
web). There may be some data entry into the project, but it is minimal.
Is there a way to back up the things I'd need to restore the tables,
such as the data structure of them, the stored procedures that load them
and the jobs that execute those stored procedures? In other words, back
up everything but the data inside the 90% of the tables which we can
re-create on the next table load?
I'm looking for a way to whittle down the amount of data I'm backing up,
actually backing up just what I specifically need to have to get going
again.
BCscript the database and store it in Source Safe.
Greg Jackson
PDX, Oregon|||Hi,
There are 2 options for you:-
1. Use generate script to script all the objects (ALL DDLs) and right click
above the job and script the jobs.
2. Do a full database backup once and perform a differential backup daily.
For jobs backup the MSDB database.
Differential backup will backup only the changes after the last backup
and will be very fast in your case since you have very less changes
on a daily basis.
Thanks
Hari
SQL Server MVP
"Blasting Cap" <goober@.christian.net> wrote in message
news:ueeTd0ocFHA.584@.TK2MSFTNGP15.phx.gbl...
>I have a database that takes up around 12 gigs or so that I would like to
>back up to a network share.
> As part of our recovery procedures, I'm also backing up the source files
> that we use to create about 90% of the data on our database (the database
> is a sales information system, with reports generated over the web).
> There may be some data entry into the project, but it is minimal.
> Is there a way to back up the things I'd need to restore the tables, such
> as the data structure of them, the stored procedures that load them and
> the jobs that execute those stored procedures? In other words, back up
> everything but the data inside the 90% of the tables which we can
> re-create on the next table load?
> I'm looking for a way to whittle down the amount of data I'm backing up,
> actually backing up just what I specifically need to have to get going
> again.
> BC
>
to back up to a network share.
As part of our recovery procedures, I'm also backing up the source files
that we use to create about 90% of the data on our database (the
database is a sales information system, with reports generated over the
web). There may be some data entry into the project, but it is minimal.
Is there a way to back up the things I'd need to restore the tables,
such as the data structure of them, the stored procedures that load them
and the jobs that execute those stored procedures? In other words, back
up everything but the data inside the 90% of the tables which we can
re-create on the next table load?
I'm looking for a way to whittle down the amount of data I'm backing up,
actually backing up just what I specifically need to have to get going
again.
BCscript the database and store it in Source Safe.
Greg Jackson
PDX, Oregon|||Hi,
There are 2 options for you:-
1. Use generate script to script all the objects (ALL DDLs) and right click
above the job and script the jobs.
2. Do a full database backup once and perform a differential backup daily.
For jobs backup the MSDB database.
Differential backup will backup only the changes after the last backup
and will be very fast in your case since you have very less changes
on a daily basis.
Thanks
Hari
SQL Server MVP
"Blasting Cap" <goober@.christian.net> wrote in message
news:ueeTd0ocFHA.584@.TK2MSFTNGP15.phx.gbl...
>I have a database that takes up around 12 gigs or so that I would like to
>back up to a network share.
> As part of our recovery procedures, I'm also backing up the source files
> that we use to create about 90% of the data on our database (the database
> is a sales information system, with reports generated over the web).
> There may be some data entry into the project, but it is minimal.
> Is there a way to back up the things I'd need to restore the tables, such
> as the data structure of them, the stored procedures that load them and
> the jobs that execute those stored procedures? In other words, back up
> everything but the data inside the 90% of the tables which we can
> re-create on the next table load?
> I'm looking for a way to whittle down the amount of data I'm backing up,
> actually backing up just what I specifically need to have to get going
> again.
> BC
>
Another question on backups
I have a database that takes up around 12 gigs or so that I would like
to back up to a network share.
As part of our recovery procedures, I'm also backing up the source files
that we use to create about 90% of the data on our database (the
database is a sales information system, with reports generated over the
web). There may be some data entry into the project, but it is minimal.
Is there a way to back up the things I'd need to restore the tables,
such as the data structure of them, the stored procedures that load them
and the jobs that execute those stored procedures? In other words, back
up everything but the data inside the 90% of the tables which we can
re-create on the next table load?
I'm looking for a way to whittle down the amount of data I'm backing up,
actually backing up just what I specifically need to have to get going
again.
BC
script the database and store it in Source Safe.
Greg Jackson
PDX, Oregon
|||Hi,
There are 2 options for you:-
1. Use generate script to script all the objects (ALL DDLs) and right click
above the job and script the jobs.
2. Do a full database backup once and perform a differential backup daily.
For jobs backup the MSDB database.
Differential backup will backup only the changes after the last backup
and will be very fast in your case since you have very less changes
on a daily basis.
Thanks
Hari
SQL Server MVP
"Blasting Cap" <goober@.christian.net> wrote in message
news:ueeTd0ocFHA.584@.TK2MSFTNGP15.phx.gbl...
>I have a database that takes up around 12 gigs or so that I would like to
>back up to a network share.
> As part of our recovery procedures, I'm also backing up the source files
> that we use to create about 90% of the data on our database (the database
> is a sales information system, with reports generated over the web).
> There may be some data entry into the project, but it is minimal.
> Is there a way to back up the things I'd need to restore the tables, such
> as the data structure of them, the stored procedures that load them and
> the jobs that execute those stored procedures? In other words, back up
> everything but the data inside the 90% of the tables which we can
> re-create on the next table load?
> I'm looking for a way to whittle down the amount of data I'm backing up,
> actually backing up just what I specifically need to have to get going
> again.
> BC
>
to back up to a network share.
As part of our recovery procedures, I'm also backing up the source files
that we use to create about 90% of the data on our database (the
database is a sales information system, with reports generated over the
web). There may be some data entry into the project, but it is minimal.
Is there a way to back up the things I'd need to restore the tables,
such as the data structure of them, the stored procedures that load them
and the jobs that execute those stored procedures? In other words, back
up everything but the data inside the 90% of the tables which we can
re-create on the next table load?
I'm looking for a way to whittle down the amount of data I'm backing up,
actually backing up just what I specifically need to have to get going
again.
BC
script the database and store it in Source Safe.
Greg Jackson
PDX, Oregon
|||Hi,
There are 2 options for you:-
1. Use generate script to script all the objects (ALL DDLs) and right click
above the job and script the jobs.
2. Do a full database backup once and perform a differential backup daily.
For jobs backup the MSDB database.
Differential backup will backup only the changes after the last backup
and will be very fast in your case since you have very less changes
on a daily basis.
Thanks
Hari
SQL Server MVP
"Blasting Cap" <goober@.christian.net> wrote in message
news:ueeTd0ocFHA.584@.TK2MSFTNGP15.phx.gbl...
>I have a database that takes up around 12 gigs or so that I would like to
>back up to a network share.
> As part of our recovery procedures, I'm also backing up the source files
> that we use to create about 90% of the data on our database (the database
> is a sales information system, with reports generated over the web).
> There may be some data entry into the project, but it is minimal.
> Is there a way to back up the things I'd need to restore the tables, such
> as the data structure of them, the stored procedures that load them and
> the jobs that execute those stored procedures? In other words, back up
> everything but the data inside the 90% of the tables which we can
> re-create on the next table load?
> I'm looking for a way to whittle down the amount of data I'm backing up,
> actually backing up just what I specifically need to have to get going
> again.
> BC
>
Sunday, February 19, 2012
Analyzing Stored Procedures - does a tool exist?
My boss wants me to go through the many stored procedures that are on our many SQL servers and generate a list of how often they are used, and then use that info to retire any stored procs that are not being used.
I did a search for tools and came across the SPUD tool at http://www.hybridx.com but the only problem with that tool is that i need to modify each stored procedure before it will start logging information on the stored proc.
Does anyone know of or use any tools that generate this sort of information in a non-invasive way? Any help would be greatly appreciated. Thanks.
There really isn't any tool that will do this sort of thing for you other
than running a constant profiler trace with sp_completed and see which ones
are called. Of coarse just because it isn't called for a day or so does not
mean it isn't used but it will give you a start and then you can narrow down
the list.
Andrew J. Kelly SQL MVP
"Sam" <Sam@.discussions.microsoft.com> wrote in message
news:6EBFC2B2-6FCC-4826-BCBA-9FFA351F2EF7@.microsoft.com...
> My boss wants me to go through the many stored procedures that are on our
many SQL servers and generate a list of how often they are used, and then
use that info to retire any stored procs that are not being used.
> I did a search for tools and came across the SPUD tool at
http://www.hybridx.com but the only problem with that tool is that i need to
modify each stored procedure before it will start logging information on the
stored proc.
> Does anyone know of or use any tools that generate this sort of
information in a non-invasive way? Any help would be greatly appreciated.
Thanks.
|||<<
> http://www.hybridx.com but the only problem with that tool is that i need
to
> modify each stored procedure before it will start logging information on
the[vbcol=seagreen]
> stored proc.
That sounds like a horrible idea to me. That creates too many opportunites
for thier code to cause problems with your code.
Andrew's suggestion of running Profiler is probably the best thing to do.
Brian
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:OGTvDp$cEHA.1764@.TK2MSFTNGP10.phx.gbl...
> There really isn't any tool that will do this sort of thing for you other
> than running a constant profiler trace with sp_completed and see which
ones
> are called. Of coarse just because it isn't called for a day or so does
not
> mean it isn't used but it will give you a start and then you can narrow
down[vbcol=seagreen]
> the list.
> --
> Andrew J. Kelly SQL MVP
>
> "Sam" <Sam@.discussions.microsoft.com> wrote in message
> news:6EBFC2B2-6FCC-4826-BCBA-9FFA351F2EF7@.microsoft.com...
our
> many SQL servers and generate a list of how often they are used, and then
> use that info to retire any stored procs that are not being used.
> http://www.hybridx.com but the only problem with that tool is that i need
to
> modify each stored procedure before it will start logging information on
the
> stored proc.
> information in a non-invasive way? Any help would be greatly appreciated.
> Thanks.
>
I did a search for tools and came across the SPUD tool at http://www.hybridx.com but the only problem with that tool is that i need to modify each stored procedure before it will start logging information on the stored proc.
Does anyone know of or use any tools that generate this sort of information in a non-invasive way? Any help would be greatly appreciated. Thanks.
There really isn't any tool that will do this sort of thing for you other
than running a constant profiler trace with sp_completed and see which ones
are called. Of coarse just because it isn't called for a day or so does not
mean it isn't used but it will give you a start and then you can narrow down
the list.
Andrew J. Kelly SQL MVP
"Sam" <Sam@.discussions.microsoft.com> wrote in message
news:6EBFC2B2-6FCC-4826-BCBA-9FFA351F2EF7@.microsoft.com...
> My boss wants me to go through the many stored procedures that are on our
many SQL servers and generate a list of how often they are used, and then
use that info to retire any stored procs that are not being used.
> I did a search for tools and came across the SPUD tool at
http://www.hybridx.com but the only problem with that tool is that i need to
modify each stored procedure before it will start logging information on the
stored proc.
> Does anyone know of or use any tools that generate this sort of
information in a non-invasive way? Any help would be greatly appreciated.
Thanks.
|||<<
> http://www.hybridx.com but the only problem with that tool is that i need
to
> modify each stored procedure before it will start logging information on
the[vbcol=seagreen]
> stored proc.
That sounds like a horrible idea to me. That creates too many opportunites
for thier code to cause problems with your code.
Andrew's suggestion of running Profiler is probably the best thing to do.
Brian
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:OGTvDp$cEHA.1764@.TK2MSFTNGP10.phx.gbl...
> There really isn't any tool that will do this sort of thing for you other
> than running a constant profiler trace with sp_completed and see which
ones
> are called. Of coarse just because it isn't called for a day or so does
not
> mean it isn't used but it will give you a start and then you can narrow
down[vbcol=seagreen]
> the list.
> --
> Andrew J. Kelly SQL MVP
>
> "Sam" <Sam@.discussions.microsoft.com> wrote in message
> news:6EBFC2B2-6FCC-4826-BCBA-9FFA351F2EF7@.microsoft.com...
our
> many SQL servers and generate a list of how often they are used, and then
> use that info to retire any stored procs that are not being used.
> http://www.hybridx.com but the only problem with that tool is that i need
to
> modify each stored procedure before it will start logging information on
the
> stored proc.
> information in a non-invasive way? Any help would be greatly appreciated.
> Thanks.
>
Subscribe to:
Posts (Atom)