Hi Guys
I have developed a new report in reporting services 2005. now i want to
use this report as a template. Where do i store this report in sql
server sub directory so that it is available in the template option
whenever i try to create a new report.
Any help would be great.
PassxSearch for "report.rdl" or report project in your HDD. Because I dont
remember the exact directory infact i have done it lot of times. or may be
just right click on the report and see the property, so that you can get
complete directory.
Amarnath
"Passx" wrote:
> Hi Guys
> I have developed a new report in reporting services 2005. now i want to
> use this report as a template. Where do i store this report in sql
> server sub directory so that it is available in the template option
> whenever i try to create a new report.
> Any help would be great.
>
> Passx
>|||Hi
I tried doing the same thing but was not able to find it. Found one in
vs8 folder. But when i placed my report in that folder was not able to
find that in the report template menu.
Any help would be great.
Passx
Amarnath wrote:
> Search for "report.rdl" or report project in your HDD. Because I dont
> remember the exact directory infact i have done it lot of times. or may be
> just right click on the report and see the property, so that you can get
> complete directory.
> Amarnath
> "Passx" wrote:
> > Hi Guys
> >
> > I have developed a new report in reporting services 2005. now i want to
> > use this report as a template. Where do i store this report in sql
> > server sub directory so that it is available in the template option
> > whenever i try to create a new report.
> >
> > Any help would be great.
> >
> >
> > Passx
> >
> >
Showing posts with label store. Show all posts
Showing posts with label store. Show all posts
Sunday, March 25, 2012
Wednesday, March 21, 2012
Creating a store procedure with output parameter
Hi all,
Could someone give me an example on how to create and execute the store procedure with using output parameter?
In normal, I create the store procedure without using output parameter, and I did it as follow:
CREATE PROC NewEmployee
(ID int(9), Name Varchar (30), hiredate DateTime, etc...)
AS
BEGIN
//my code
END
GO
When i executed it, I would said: Execute NewEmployee 123456789, 'peter mailler', getDate(), etc...
For output parameter:
CREATE PROC NewEmployee
(ID int(9), Name Varchar (30), hiredate DateTime,@.message Varchar(40) out)
AS
BEGIN
insert into Employee .....
//if error encountered
set@.message = "Insertion failure"
END
GO
Exec NewEmployee 123456789, 'peter mailler', getDate(),do I need to input something for the output parameter here?
Anyone could give me an example on how to handle the output parameter within the store procedure coz I am not sure how to handle it?
Many thanks.
Could someone give me an example on how to create and execute the store procedure with using output parameter?
In normal, I create the store procedure without using output parameter, and I did it as follow:
CREATE PROC NewEmployee
(ID int(9), Name Varchar (30), hiredate DateTime, etc...)
AS
BEGIN
//my code
END
GO
When i executed it, I would said: Execute NewEmployee 123456789, 'peter mailler', getDate(), etc...
For output parameter:
CREATE PROC NewEmployee
(ID int(9), Name Varchar (30), hiredate DateTime,@.message Varchar(40) out)
AS
BEGIN
insert into Employee .....
//if error encountered
set@.message = "Insertion failure"
END
GO
Exec NewEmployee 123456789, 'peter mailler', getDate(),do I need to input something for the output parameter here?
Anyone could give me an example on how to handle the output parameter within the store procedure coz I am not sure how to handle it?
Many thanks.
Hi,
when calling EXEC newEmployee... you need ti declarare a parameter, assign it to the call and then you'd get the output value from it.
DECLARE @.msg nvarchar(40);
Exec NewEmployee 123456789, 'peter mailler', getDate(),@.msg;
-- Here you could access @.msg to get what was outputted
Wednesday, March 7, 2012
Creating a Date - or Time - Only Column in SQL Server
I understand that in SQL Svr 2000, all date/time fields store both the date
and the time. Is there a way through a constraint or trigger to force a tabl
e
to store only the date portion or time portion of the entry? For example, a
"DateHeld" field would actually contain only 2/14/2007, rather than
"2/14/2007 12:00:00 AM".
Or is there a better solution? I would rather not have to keep writing
functions to convert these combined date/time values when I want to use them
as just a date or just a time. Thanks! George> and the time. Is there a way through a constraint or trigger to force a
> table
> to store only the date portion or time portion of the entry?
USE tempdb;
GO
CREATE TABLE dbo.foo
(
dt SMALLDATETIME CHECK (DATEADD(DAY, 0, DATEDIFF(DAY, 0, dt)) = dt),
tm DATETIME CHECK (DATEADD(DAY, 0, DATEDIFF(DAY, 0, tm)) = '19000101')
);
SET NOCOUNT ON;
INSERT dbo.foo(dt, tm) SELECT '20070101', '19:34';
GO
-- fails:
INSERT dbo.foo(dt, tm) SELECT '20070101 19:34', '19:34';
GO
-- fails:
INSERT dbo.foo(dt, tm) SELECT '20070101', '19000102 19:34';
GO
-- fails:
INSERT dbo.foo(dt, tm) SELECT '19:34', '20060505';
GO
SELECT * FROM dbo.foo;
GO
DROP TABLE dbo.foo;
GO
> Or is there a better solution? I would rather not have to keep writing
> functions to convert these combined date/time values when I want to use
> them
> as just a date or just a time.
Why don't you let the presentation side of things handle the formatting and
display of the date only or time only value?|||"Aaron Bertrand [SQL Server MVP]" wrote:
> Why don't you let the presentation side of things handle the formatting an
d
> display of the date only or time only value?
>
Well, doing it at the interface end means a lot of repetitious formatting in
different places. I'd rather fix it at the source one time. I just find it
kind of amazing that SQL Server does not support current_date or
current_time, for example.
I presume the original T-SQL stuff at the top is used to build a trigger.
Thanks for the help, Aaron.
and the time. Is there a way through a constraint or trigger to force a tabl
e
to store only the date portion or time portion of the entry? For example, a
"DateHeld" field would actually contain only 2/14/2007, rather than
"2/14/2007 12:00:00 AM".
Or is there a better solution? I would rather not have to keep writing
functions to convert these combined date/time values when I want to use them
as just a date or just a time. Thanks! George> and the time. Is there a way through a constraint or trigger to force a
> table
> to store only the date portion or time portion of the entry?
USE tempdb;
GO
CREATE TABLE dbo.foo
(
dt SMALLDATETIME CHECK (DATEADD(DAY, 0, DATEDIFF(DAY, 0, dt)) = dt),
tm DATETIME CHECK (DATEADD(DAY, 0, DATEDIFF(DAY, 0, tm)) = '19000101')
);
SET NOCOUNT ON;
INSERT dbo.foo(dt, tm) SELECT '20070101', '19:34';
GO
-- fails:
INSERT dbo.foo(dt, tm) SELECT '20070101 19:34', '19:34';
GO
-- fails:
INSERT dbo.foo(dt, tm) SELECT '20070101', '19000102 19:34';
GO
-- fails:
INSERT dbo.foo(dt, tm) SELECT '19:34', '20060505';
GO
SELECT * FROM dbo.foo;
GO
DROP TABLE dbo.foo;
GO
> Or is there a better solution? I would rather not have to keep writing
> functions to convert these combined date/time values when I want to use
> them
> as just a date or just a time.
Why don't you let the presentation side of things handle the formatting and
display of the date only or time only value?|||"Aaron Bertrand [SQL Server MVP]" wrote:
> Why don't you let the presentation side of things handle the formatting an
d
> display of the date only or time only value?
>
Well, doing it at the interface end means a lot of repetitious formatting in
different places. I'd rather fix it at the source one time. I just find it
kind of amazing that SQL Server does not support current_date or
current_time, for example.
I presume the original T-SQL stuff at the top is used to build a trigger.
Thanks for the help, Aaron.
Creating a Date - or Time - Only Column in SQL Server
I understand that in SQL Svr 2000, all date/time fields store both the date
and the time. Is there a way through a constraint or trigger to force a table
to store only the date portion or time portion of the entry? For example, a
"DateHeld" field would actually contain only 2/14/2007, rather than
"2/14/2007 12:00:00 AM".
Or is there a better solution? I would rather not have to keep writing
functions to convert these combined date/time values when I want to use them
as just a date or just a time. Thanks! George> and the time. Is there a way through a constraint or trigger to force a
> table
> to store only the date portion or time portion of the entry?
USE tempdb;
GO
CREATE TABLE dbo.foo
(
dt SMALLDATETIME CHECK (DATEADD(DAY, 0, DATEDIFF(DAY, 0, dt)) = dt),
tm DATETIME CHECK (DATEADD(DAY, 0, DATEDIFF(DAY, 0, tm)) = '19000101')
);
SET NOCOUNT ON;
INSERT dbo.foo(dt, tm) SELECT '20070101', '19:34';
GO
-- fails:
INSERT dbo.foo(dt, tm) SELECT '20070101 19:34', '19:34';
GO
-- fails:
INSERT dbo.foo(dt, tm) SELECT '20070101', '19000102 19:34';
GO
-- fails:
INSERT dbo.foo(dt, tm) SELECT '19:34', '20060505';
GO
SELECT * FROM dbo.foo;
GO
DROP TABLE dbo.foo;
GO
> Or is there a better solution? I would rather not have to keep writing
> functions to convert these combined date/time values when I want to use
> them
> as just a date or just a time.
Why don't you let the presentation side of things handle the formatting and
display of the date only or time only value?|||"Aaron Bertrand [SQL Server MVP]" wrote:
> Why don't you let the presentation side of things handle the formatting and
> display of the date only or time only value?
>
Well, doing it at the interface end means a lot of repetitious formatting in
different places. I'd rather fix it at the source one time. I just find it
kind of amazing that SQL Server does not support current_date or
current_time, for example.
I presume the original T-SQL stuff at the top is used to build a trigger.
Thanks for the help, Aaron.
and the time. Is there a way through a constraint or trigger to force a table
to store only the date portion or time portion of the entry? For example, a
"DateHeld" field would actually contain only 2/14/2007, rather than
"2/14/2007 12:00:00 AM".
Or is there a better solution? I would rather not have to keep writing
functions to convert these combined date/time values when I want to use them
as just a date or just a time. Thanks! George> and the time. Is there a way through a constraint or trigger to force a
> table
> to store only the date portion or time portion of the entry?
USE tempdb;
GO
CREATE TABLE dbo.foo
(
dt SMALLDATETIME CHECK (DATEADD(DAY, 0, DATEDIFF(DAY, 0, dt)) = dt),
tm DATETIME CHECK (DATEADD(DAY, 0, DATEDIFF(DAY, 0, tm)) = '19000101')
);
SET NOCOUNT ON;
INSERT dbo.foo(dt, tm) SELECT '20070101', '19:34';
GO
-- fails:
INSERT dbo.foo(dt, tm) SELECT '20070101 19:34', '19:34';
GO
-- fails:
INSERT dbo.foo(dt, tm) SELECT '20070101', '19000102 19:34';
GO
-- fails:
INSERT dbo.foo(dt, tm) SELECT '19:34', '20060505';
GO
SELECT * FROM dbo.foo;
GO
DROP TABLE dbo.foo;
GO
> Or is there a better solution? I would rather not have to keep writing
> functions to convert these combined date/time values when I want to use
> them
> as just a date or just a time.
Why don't you let the presentation side of things handle the formatting and
display of the date only or time only value?|||"Aaron Bertrand [SQL Server MVP]" wrote:
> Why don't you let the presentation side of things handle the formatting and
> display of the date only or time only value?
>
Well, doing it at the interface end means a lot of repetitious formatting in
different places. I'd rather fix it at the source one time. I just find it
kind of amazing that SQL Server does not support current_date or
current_time, for example.
I presume the original T-SQL stuff at the top is used to build a trigger.
Thanks for the help, Aaron.
Creating a Date - or Time - Only Column in SQL Server
I understand that in SQL Svr 2000, all date/time fields store both the date
and the time. Is there a way through a constraint or trigger to force a table
to store only the date portion or time portion of the entry? For example, a
"DateHeld" field would actually contain only 2/14/2007, rather than
"2/14/2007 12:00:00 AM".
Or is there a better solution? I would rather not have to keep writing
functions to convert these combined date/time values when I want to use them
as just a date or just a time. Thanks! George
> and the time. Is there a way through a constraint or trigger to force a
> table
> to store only the date portion or time portion of the entry?
USE tempdb;
GO
CREATE TABLE dbo.foo
(
dt SMALLDATETIME CHECK (DATEADD(DAY, 0, DATEDIFF(DAY, 0, dt)) = dt),
tm DATETIME CHECK (DATEADD(DAY, 0, DATEDIFF(DAY, 0, tm)) = '19000101')
);
SET NOCOUNT ON;
INSERT dbo.foo(dt, tm) SELECT '20070101', '19:34';
GO
-- fails:
INSERT dbo.foo(dt, tm) SELECT '20070101 19:34', '19:34';
GO
-- fails:
INSERT dbo.foo(dt, tm) SELECT '20070101', '19000102 19:34';
GO
-- fails:
INSERT dbo.foo(dt, tm) SELECT '19:34', '20060505';
GO
SELECT * FROM dbo.foo;
GO
DROP TABLE dbo.foo;
GO
> Or is there a better solution? I would rather not have to keep writing
> functions to convert these combined date/time values when I want to use
> them
> as just a date or just a time.
Why don't you let the presentation side of things handle the formatting and
display of the date only or time only value?
|||"Aaron Bertrand [SQL Server MVP]" wrote:
> Why don't you let the presentation side of things handle the formatting and
> display of the date only or time only value?
>
Well, doing it at the interface end means a lot of repetitious formatting in
different places. I'd rather fix it at the source one time. I just find it
kind of amazing that SQL Server does not support current_date or
current_time, for example.
I presume the original T-SQL stuff at the top is used to build a trigger.
Thanks for the help, Aaron.
and the time. Is there a way through a constraint or trigger to force a table
to store only the date portion or time portion of the entry? For example, a
"DateHeld" field would actually contain only 2/14/2007, rather than
"2/14/2007 12:00:00 AM".
Or is there a better solution? I would rather not have to keep writing
functions to convert these combined date/time values when I want to use them
as just a date or just a time. Thanks! George
> and the time. Is there a way through a constraint or trigger to force a
> table
> to store only the date portion or time portion of the entry?
USE tempdb;
GO
CREATE TABLE dbo.foo
(
dt SMALLDATETIME CHECK (DATEADD(DAY, 0, DATEDIFF(DAY, 0, dt)) = dt),
tm DATETIME CHECK (DATEADD(DAY, 0, DATEDIFF(DAY, 0, tm)) = '19000101')
);
SET NOCOUNT ON;
INSERT dbo.foo(dt, tm) SELECT '20070101', '19:34';
GO
-- fails:
INSERT dbo.foo(dt, tm) SELECT '20070101 19:34', '19:34';
GO
-- fails:
INSERT dbo.foo(dt, tm) SELECT '20070101', '19000102 19:34';
GO
-- fails:
INSERT dbo.foo(dt, tm) SELECT '19:34', '20060505';
GO
SELECT * FROM dbo.foo;
GO
DROP TABLE dbo.foo;
GO
> Or is there a better solution? I would rather not have to keep writing
> functions to convert these combined date/time values when I want to use
> them
> as just a date or just a time.
Why don't you let the presentation side of things handle the formatting and
display of the date only or time only value?
|||"Aaron Bertrand [SQL Server MVP]" wrote:
> Why don't you let the presentation side of things handle the formatting and
> display of the date only or time only value?
>
Well, doing it at the interface end means a lot of repetitious formatting in
different places. I'd rather fix it at the source one time. I just find it
kind of amazing that SQL Server does not support current_date or
current_time, for example.
I presume the original T-SQL stuff at the top is used to build a trigger.
Thanks for the help, Aaron.
Sunday, February 19, 2012
Creating & Maintaining Demo Database
I would like to create a demo database. Here are the specifications.
1. I need an easy way to store the sample data so that the database can
be refreshed after use and put back to its original data.
2. I am constantly making changes to the production database that this
demo is based off of. I would like to have a simple way of keeping the
demo database (table structures and stored procedures) in sync with the
production database without affecting the data (see #1). I worry about
making changes to the production database and forgetting to make the
change in the demo database.
I have some ideas but would love to hear how others have done this sort
of thing.
Thanks in advance,
Debbie
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!1. Back it up and restore it whenever you need to...
2. Every shop handles this type of thing differently, but my personal core
rules are: Never make changes on a production database via Enterprise
Manager, Query Analyzer's UI options, or any other database frontend UI.
Instead, script all changes and check them in to a source control system
(e.g. Visual Source Safe). This keeps a very good audit trail and allows
you to easily roll changes to other databases without scratching your head
and wondering what has changed between versions. Another option is to use a
product like Red Gate's SQL Compare, but I highly recommend you get into the
habit of scripting changes and storing them instead of relying on software
to find the changes after you make them (in other words, be proactive rather
than reactive!)
"Debbie" <anonymous@.email.com> wrote in message
news:ukvh7#K$DHA.1548@.TK2MSFTNGP12.phx.gbl...
> I would like to create a demo database. Here are the specifications.
> 1. I need an easy way to store the sample data so that the database can
> be refreshed after use and put back to its original data.
> 2. I am constantly making changes to the production database that this
> demo is based off of. I would like to have a simple way of keeping the
> demo database (table structures and stored procedures) in sync with the
> production database without affecting the data (see #1). I worry about
> making changes to the production database and forgetting to make the
> change in the demo database.
> I have some ideas but would love to hear how others have done this sort
> of thing.
> Thanks in advance,
> Debbie
> *** Sent via Developersdex http://www.developersdex.com ***
> Don't just participate in USENET...get rewarded for it!|||hello Debbie,
have a look at www.dbghost.com for an outline of a
process which will rid you of any code change management
issues - guarenteed. You can use it with SourceSafe (read
Adams comment) making it a true change management
proposal.
regards,
Mark Baekdal
>--Original Message--
>I would like to create a demo database. Here are the
specifications.
>1. I need an easy way to store the sample data so that
the database can
>be refreshed after use and put back to its original data.
>2. I am constantly making changes to the production
database that this
>demo is based off of. I would like to have a simple way
of keeping the
>demo database (table structures and stored procedures)
in sync with the
>production database without affecting the data (see
#1). I worry about
>making changes to the production database and forgetting
to make the
>change in the demo database.
>I have some ideas but would love to hear how others have
done this sort
>of thing.
>Thanks in advance,
>Debbie
>*** Sent via Developersdex http://www.developersdex.com
***
>Don't just participate in USENET...get rewarded for it!
>.
>
1. I need an easy way to store the sample data so that the database can
be refreshed after use and put back to its original data.
2. I am constantly making changes to the production database that this
demo is based off of. I would like to have a simple way of keeping the
demo database (table structures and stored procedures) in sync with the
production database without affecting the data (see #1). I worry about
making changes to the production database and forgetting to make the
change in the demo database.
I have some ideas but would love to hear how others have done this sort
of thing.
Thanks in advance,
Debbie
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!1. Back it up and restore it whenever you need to...
2. Every shop handles this type of thing differently, but my personal core
rules are: Never make changes on a production database via Enterprise
Manager, Query Analyzer's UI options, or any other database frontend UI.
Instead, script all changes and check them in to a source control system
(e.g. Visual Source Safe). This keeps a very good audit trail and allows
you to easily roll changes to other databases without scratching your head
and wondering what has changed between versions. Another option is to use a
product like Red Gate's SQL Compare, but I highly recommend you get into the
habit of scripting changes and storing them instead of relying on software
to find the changes after you make them (in other words, be proactive rather
than reactive!)
"Debbie" <anonymous@.email.com> wrote in message
news:ukvh7#K$DHA.1548@.TK2MSFTNGP12.phx.gbl...
> I would like to create a demo database. Here are the specifications.
> 1. I need an easy way to store the sample data so that the database can
> be refreshed after use and put back to its original data.
> 2. I am constantly making changes to the production database that this
> demo is based off of. I would like to have a simple way of keeping the
> demo database (table structures and stored procedures) in sync with the
> production database without affecting the data (see #1). I worry about
> making changes to the production database and forgetting to make the
> change in the demo database.
> I have some ideas but would love to hear how others have done this sort
> of thing.
> Thanks in advance,
> Debbie
> *** Sent via Developersdex http://www.developersdex.com ***
> Don't just participate in USENET...get rewarded for it!|||hello Debbie,
have a look at www.dbghost.com for an outline of a
process which will rid you of any code change management
issues - guarenteed. You can use it with SourceSafe (read
Adams comment) making it a true change management
proposal.
regards,
Mark Baekdal
>--Original Message--
>I would like to create a demo database. Here are the
specifications.
>1. I need an easy way to store the sample data so that
the database can
>be refreshed after use and put back to its original data.
>2. I am constantly making changes to the production
database that this
>demo is based off of. I would like to have a simple way
of keeping the
>demo database (table structures and stored procedures)
in sync with the
>production database without affecting the data (see
#1). I worry about
>making changes to the production database and forgetting
to make the
>change in the demo database.
>I have some ideas but would love to hear how others have
done this sort
>of thing.
>Thanks in advance,
>Debbie
>*** Sent via Developersdex http://www.developersdex.com
***
>Don't just participate in USENET...get rewarded for it!
>.
>
Creating & Maintaining Demo Database
I would like to create a demo database. Here are the specifications.
1. I need an easy way to store the sample data so that the database can
be refreshed after use and put back to its original data.
2. I am constantly making changes to the production database that this
demo is based off of. I would like to have a simple way of keeping the
demo database (table structures and stored procedures) in sync with the
production database without affecting the data (see #1). I worry about
making changes to the production database and forgetting to make the
change in the demo database.
I have some ideas but would love to hear how others have done this sort
of thing.
Thanks in advance,
Debbie
*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!1. Back it up and restore it whenever you need to...
2. Every shop handles this type of thing differently, but my personal core
rules are: Never make changes on a production database via Enterprise
Manager, Query Analyzer's UI options, or any other database frontend UI.
Instead, script all changes and check them in to a source control system
(e.g. Visual Source Safe). This keeps a very good audit trail and allows
you to easily roll changes to other databases without scratching your head
and wondering what has changed between versions. Another option is to use a
product like Red Gate's SQL Compare, but I highly recommend you get into the
habit of scripting changes and storing them instead of relying on software
to find the changes after you make them (in other words, be proactive rather
than reactive!)
"Debbie" <anonymous@.email.com> wrote in message
news:ukvh7#K$DHA.1548@.TK2MSFTNGP12.phx.gbl...
> I would like to create a demo database. Here are the specifications.
> 1. I need an easy way to store the sample data so that the database can
> be refreshed after use and put back to its original data.
> 2. I am constantly making changes to the production database that this
> demo is based off of. I would like to have a simple way of keeping the
> demo database (table structures and stored procedures) in sync with the
> production database without affecting the data (see #1). I worry about
> making changes to the production database and forgetting to make the
> change in the demo database.
> I have some ideas but would love to hear how others have done this sort
> of thing.
> Thanks in advance,
> Debbie
> *** Sent via Developersdex http://www.examnotes.net ***
> Don't just participate in USENET...get rewarded for it!|||Thanks for the response.
On the backup/restore solution, I am concerned that when we make changes
to the database, the restore will overwrite any of our changes with the
old version.
Any other ideas will be welcome, I really want to think this through
before turning something over to my sales department.
*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!|||Yes, it will overwrite any changes. So restore, apply your changes, then
back up the new version
"Debbie" <anonymous@.email.com> wrote in message
news:efdRKVL$DHA.268@.TK2MSFTNGP10.phx.gbl...
> Thanks for the response.
> On the backup/restore solution, I am concerned that when we make changes
> to the database, the restore will overwrite any of our changes with the
> old version.
> Any other ideas will be welcome, I really want to think this through
> before turning something over to my sales department.
>
> *** Sent via Developersdex http://www.examnotes.net ***
> Don't just participate in USENET...get rewarded for it!
1. I need an easy way to store the sample data so that the database can
be refreshed after use and put back to its original data.
2. I am constantly making changes to the production database that this
demo is based off of. I would like to have a simple way of keeping the
demo database (table structures and stored procedures) in sync with the
production database without affecting the data (see #1). I worry about
making changes to the production database and forgetting to make the
change in the demo database.
I have some ideas but would love to hear how others have done this sort
of thing.
Thanks in advance,
Debbie
*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!1. Back it up and restore it whenever you need to...
2. Every shop handles this type of thing differently, but my personal core
rules are: Never make changes on a production database via Enterprise
Manager, Query Analyzer's UI options, or any other database frontend UI.
Instead, script all changes and check them in to a source control system
(e.g. Visual Source Safe). This keeps a very good audit trail and allows
you to easily roll changes to other databases without scratching your head
and wondering what has changed between versions. Another option is to use a
product like Red Gate's SQL Compare, but I highly recommend you get into the
habit of scripting changes and storing them instead of relying on software
to find the changes after you make them (in other words, be proactive rather
than reactive!)
"Debbie" <anonymous@.email.com> wrote in message
news:ukvh7#K$DHA.1548@.TK2MSFTNGP12.phx.gbl...
> I would like to create a demo database. Here are the specifications.
> 1. I need an easy way to store the sample data so that the database can
> be refreshed after use and put back to its original data.
> 2. I am constantly making changes to the production database that this
> demo is based off of. I would like to have a simple way of keeping the
> demo database (table structures and stored procedures) in sync with the
> production database without affecting the data (see #1). I worry about
> making changes to the production database and forgetting to make the
> change in the demo database.
> I have some ideas but would love to hear how others have done this sort
> of thing.
> Thanks in advance,
> Debbie
> *** Sent via Developersdex http://www.examnotes.net ***
> Don't just participate in USENET...get rewarded for it!|||Thanks for the response.
On the backup/restore solution, I am concerned that when we make changes
to the database, the restore will overwrite any of our changes with the
old version.
Any other ideas will be welcome, I really want to think this through
before turning something over to my sales department.
*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!|||Yes, it will overwrite any changes. So restore, apply your changes, then
back up the new version
"Debbie" <anonymous@.email.com> wrote in message
news:efdRKVL$DHA.268@.TK2MSFTNGP10.phx.gbl...
> Thanks for the response.
> On the backup/restore solution, I am concerned that when we make changes
> to the database, the restore will overwrite any of our changes with the
> old version.
> Any other ideas will be welcome, I really want to think this through
> before turning something over to my sales department.
>
> *** Sent via Developersdex http://www.examnotes.net ***
> Don't just participate in USENET...get rewarded for it!
Subscribe to:
Posts (Atom)