Backing up Stored Procedure

Hi,
I am using the Backup Wizard with following statement to backup entire DB
from Development Server.
BACKUP DATABASE [Dev_DB] TO [Dev_DB_Backup] WITH INIT , NOUNLOAD ,
NAME = N'Dev_DB Backup',
SKIP , STATS = 10,
NOFORMAT
It doesnot backup the stored procedures developed.
Is there a way to backup the stored procedures as well through scheduled
task or some script to be run at specific time.
TIA
KayAre you sure, the command above store all the data and the object
definitions (which is actually data stored in the system tables) ?
Please make sure and confirm this.
HTH, jens Suessmeyer.|||Systems table data is not required for the time being. But yes it is.
"Jens" <Jens@.sqlserver2005.de> wrote in message
news:1132850534.307481.196070@.g49g2000cwa.googlegroups.com...
> Are you sure, the command above store all the data and the object
> definitions (which is actually data stored in the system tables) ?
> Please make sure and confirm this.
> HTH, jens Suessmeyer.
>sql

Backing up Stored Procedure

Hi,
I am using the Backup Wizard with following statement to backup entire DB
from Development Server.
BACKUP DATABASE [Dev_DB] TO [Dev_DB_Backup] WITH INIT , NOUNLOAD ,
NAME = N'Dev_DB Backup',
SKIP , STATS = 10,
NOFORMAT
It doesnot backup the stored procedures developed.
Is there a way to backup the stored procedures as well through scheduled
task or some script to be run at specific time.
TIA
KayAre you sure, the command above store all the data and the object
definitions (which is actually data stored in the system tables) ?
Please make sure and confirm this.
HTH, jens Suessmeyer.|||Systems table data is not required for the time being. But yes it is.
"Jens" <Jens@.sqlserver2005.de> wrote in message
news:1132850534.307481.196070@.g49g2000cwa.googlegroups.com...
> Are you sure, the command above store all the data and the object
> definitions (which is actually data stored in the system tables) ?
> Please make sure and confirm this.
> HTH, jens Suessmeyer.
>

Backing up Stored Procedure

Hi,
I am using the Backup Wizard with following statement to backup entire DB
from Development Server.
BACKUP DATABASE [Dev_DB] TO [Dev_DB_Backup] WITH INIT , NOUNLOAD ,
NAME = N'Dev_DB Backup',
SKIP , STATS = 10,
NOFORMAT
It doesnot backup the stored procedures developed.
Is there a way to backup the stored procedures as well through scheduled
task or some script to be run at specific time.
TIA
Kay
Are you sure, the command above store all the data and the object
definitions (which is actually data stored in the system tables) ?
Please make sure and confirm this.
HTH, jens Suessmeyer.
|||Systems table data is not required for the time being. But yes it is.
"Jens" <Jens@.sqlserver2005.de> wrote in message
news:1132850534.307481.196070@.g49g2000cwa.googlegr oups.com...
> Are you sure, the command above store all the data and the object
> definitions (which is actually data stored in the system tables) ?
> Please make sure and confirm this.
> HTH, jens Suessmeyer.
>

backing up everything to sql script

is there a way to back up the entire database, data, relations, tables, and
procedures to an sql script? and if so how do i do it? thanksBrian,
> is there a way to back up the entire database, data, relations,
> tables, and procedures to an sql script? and if so how do i do
> it? thanks
Yes, in Enterprise Manager. Right-click on the database, select All
Tasks | Generate SQL Script... from the menu.
Linda|||Brian,
Just one oversite - This does not get you the DATA.
You can back up the data using:
1) A full database backup - also gets you everything else
2) Detach database and file copy mdf, ndf, ldf files (or just stop SQL server rather than detach)
3) bcp
4) dts
5) Access import via odbc ( okay not so easy to get back, but still useful )
With 3) to 5) backup is on a table by table basis.
Regards
AJ
"lindawie" <lindawie@.my-deja.com> wrote in message news:OYUXTpEkDHA.976@.tk2msftngp13.phx.gbl...
> Brian,
> > is there a way to back up the entire database, data, relations,
> > tables, and procedures to an sql script? and if so how do i do
> > it? thanks
> Yes, in Enterprise Manager. Right-click on the database, select All
> Tasks | Generate SQL Script... from the menu.
> Linda
>

avoid warning

We use a script in our build process to create a database. A single
script creates entire database, including stored procedures. We
occasionally
get a warning message "cannot create entry in sysdepends as .....
the procedure will still be created". I believe this is a harmless
warning
and happens because of the order of creation of stord procedure. Is
there a way to disable this warning.
See "set ansi_warnings" in BOL.
use northwind
go
set ansi_warnings off
go
create procedure proc1
as
select * from t1
go
set ansi_warnings on
go
drop procedure proc1
go
AMB
"Data Cruncher" wrote:

> We use a script in our build process to create a database. A single
> script creates entire database, including stored procedures. We
> occasionally
> get a warning message "cannot create entry in sysdepends as .....
> the procedure will still be created". I believe this is a harmless
> warning
> and happens because of the order of creation of stord procedure. Is
> there a way to disable this warning.
>
|||Sorry,
It seems that this option does not help.
AMB
"Alejandro Mesa" wrote:
[vbcol=seagreen]
> See "set ansi_warnings" in BOL.
> use northwind
> go
> set ansi_warnings off
> go
> create procedure proc1
> as
> select * from t1
> go
> set ansi_warnings on
> go
> drop procedure proc1
> go
>
> AMB
> "Data Cruncher" wrote:
|||I don't think there's a way to shut off the warning outside of
creating your script with sub procs being compiled before the
calling procs.
For all intents and purposes, it's harmless for the reason
you stated. Of course, it's not harmless if the main procedure,
in fact, doesn't get created!
"Data Cruncher" <dcruncher4@.netscape.net> wrote in message
news:1116249702.395329.63480@.g47g2000cwa.googlegro ups.com...
> We use a script in our build process to create a database. A single
> script creates entire database, including stored procedures. We
> occasionally
> get a warning message "cannot create entry in sysdepends as .....
> the procedure will still be created". I believe this is a harmless
> warning
> and happens because of the order of creation of stord procedure. Is
> there a way to disable this warning.
>

avoid warning

We use a script in our build process to create a database. A single
script creates entire database, including stored procedures. We
occasionally
get a warning message "cannot create entry in sysdepends as .....
the procedure will still be created". I believe this is a harmless
warning
and happens because of the order of creation of stord procedure. Is
there a way to disable this warning.See "set ansi_warnings" in BOL.
use northwind
go
set ansi_warnings off
go
create procedure proc1
as
select * from t1
go
set ansi_warnings on
go
drop procedure proc1
go
AMB
"Data Cruncher" wrote:
> We use a script in our build process to create a database. A single
> script creates entire database, including stored procedures. We
> occasionally
> get a warning message "cannot create entry in sysdepends as .....
> the procedure will still be created". I believe this is a harmless
> warning
> and happens because of the order of creation of stord procedure. Is
> there a way to disable this warning.
>|||Sorry,
It seems that this option does not help.
AMB
"Alejandro Mesa" wrote:
> See "set ansi_warnings" in BOL.
> use northwind
> go
> set ansi_warnings off
> go
> create procedure proc1
> as
> select * from t1
> go
> set ansi_warnings on
> go
> drop procedure proc1
> go
>
> AMB
> "Data Cruncher" wrote:
> > We use a script in our build process to create a database. A single
> > script creates entire database, including stored procedures. We
> > occasionally
> > get a warning message "cannot create entry in sysdepends as .....
> > the procedure will still be created". I believe this is a harmless
> > warning
> > and happens because of the order of creation of stord procedure. Is
> > there a way to disable this warning.
> >
> >|||I don't think there's a way to shut off the warning outside of
creating your script with sub procs being compiled before the
calling procs.
For all intents and purposes, it's harmless for the reason
you stated. Of course, it's not harmless if the main procedure,
in fact, doesn't get created!
"Data Cruncher" <dcruncher4@.netscape.net> wrote in message
news:1116249702.395329.63480@.g47g2000cwa.googlegroups.com...
> We use a script in our build process to create a database. A single
> script creates entire database, including stored procedures. We
> occasionally
> get a warning message "cannot create entry in sysdepends as .....
> the procedure will still be created". I believe this is a harmless
> warning
> and happens because of the order of creation of stord procedure. Is
> there a way to disable this warning.
>

avoid warning

We use a script in our build process to create a database. A single
script creates entire database, including stored procedures. We
occasionally
get a warning message "cannot create entry in sysdepends as .....
the procedure will still be created". I believe this is a harmless
warning
and happens because of the order of creation of stord procedure. Is
there a way to disable this warning.See "set ansi_warnings" in BOL.
use northwind
go
set ansi_warnings off
go
create procedure proc1
as
select * from t1
go
set ansi_warnings on
go
drop procedure proc1
go
AMB
"Data Cruncher" wrote:

> We use a script in our build process to create a database. A single
> script creates entire database, including stored procedures. We
> occasionally
> get a warning message "cannot create entry in sysdepends as .....
> the procedure will still be created". I believe this is a harmless
> warning
> and happens because of the order of creation of stord procedure. Is
> there a way to disable this warning.
>|||Sorry,
It seems that this option does not help.
AMB
"Alejandro Mesa" wrote:
[vbcol=seagreen]
> See "set ansi_warnings" in BOL.
> use northwind
> go
> set ansi_warnings off
> go
> create procedure proc1
> as
> select * from t1
> go
> set ansi_warnings on
> go
> drop procedure proc1
> go
>
> AMB
> "Data Cruncher" wrote:
>|||I don't think there's a way to shut off the warning outside of
creating your script with sub procs being compiled before the
calling procs.
For all intents and purposes, it's harmless for the reason
you stated. Of course, it's not harmless if the main procedure,
in fact, doesn't get created!
"Data Cruncher" <dcruncher4@.netscape.net> wrote in message
news:1116249702.395329.63480@.g47g2000cwa.googlegroups.com...
> We use a script in our build process to create a database. A single
> script creates entire database, including stored procedures. We
> occasionally
> get a warning message "cannot create entry in sysdepends as .....
> the procedure will still be created". I believe this is a harmless
> warning
> and happens because of the order of creation of stord procedure. Is
> there a way to disable this warning.
>

Autosize reportviewer control

I want the reportviewer to display the report exactly over the entire screen. If I try to use "width=100%", the report viewer control expands beyond the screen area making us to scroll to view the "View Report" button. However, in the report manager, the same report gets displayed exactly occupying the screen size no matter what resolution the screen size is.

How is it done?

Thanks.

You may be running into doctype issues in your html. Xhtml interprets percentage width and height differently than traditional html. If you are using xhtml, try removing the xhtml doctype specification from the beginning of your html file.|||

Hi cvajre

I have same problem. did you find a solution?

Thanks..

|||

Hi,

I think by setting the width we can control the size of the reportviewer control not the report data itself.

By setting the width to 100%, we can arrange the width of the area which includes the parameters, the view report button, paging control, export and the print controls. Not the report area. I mean we can not configure the width of the Reserved.ReportViewerWebControl.axd.

One way of doing this can be using the Layout properties of the report. But you can use fix width then, not a percentage usage can be configured here.

One idea is using XSLT to transform the output data as html within a table of width 100%.

Eralper

Autosize reportviewer control

I want the reportviewer to display the report exactly over the entire screen. If I try to use "width=100%", the report viewer control expands beyond the screen area making us to scroll to view the "View Report" button. However, in the report manager, the same report gets displayed exactly occupying the screen size no matter what resolution the screen size is.

How is it done?

Thanks.

You may be running into doctype issues in your html. Xhtml interprets percentage width and height differently than traditional html. If you are using xhtml, try removing the xhtml doctype specification from the beginning of your html file.|||

Hi cvajre

I have same problem. did you find a solution?

Thanks..

|||

Hi,

I think by setting the width we can control the size of the reportviewer control not the report data itself.

By setting the width to 100%, we can arrange the width of the area which includes the parameters, the view report button, paging control, export and the print controls. Not the report area. I mean we can not configure the width of the Reserved.ReportViewerWebControl.axd.

One way of doing this can be using the Layout properties of the report. But you can use fix width then, not a percentage usage can be configured here.

One idea is using XSLT to transform the output data as html within a table of width 100%.

Eralper

Autosize reportviewer control

I want the reportviewer to display the report exactly over the entire screen. If I try to use "width=100%", the report viewer control expands beyond the screen area making us to scroll to view the "View Report" button. However, in the report manager, the same report gets displayed exactly occupying the screen size no matter what resolution the screen size is.

How is it done?

Thanks.

You may be running into doctype issues in your html. Xhtml interprets percentage width and height differently than traditional html. If you are using xhtml, try removing the xhtml doctype specification from the beginning of your html file.|||

Hi cvajre

I have same problem. did you find a solution?

Thanks..

|||

Hi,

I think by setting the width we can control the size of the reportviewer control not the report data itself.

By setting the width to 100%, we can arrange the width of the area which includes the parameters, the view report button, paging control, export and the print controls. Not the report area. I mean we can not configure the width of the Reserved.ReportViewerWebControl.axd.

One way of doing this can be using the Layout properties of the report. But you can use fix width then, not a percentage usage can be configured here.

One idea is using XSLT to transform the output data as html within a table of width 100%.

Eralper