minimum role/permissions for backup

I have a MS SQL database process that is run from ASP.NET.
I would like to be able to backup the SQL database using either
a full database or transaction log backup immediately before the
process is done. Is this possible with ASP.NET and
what kind of permissions or role would the SQL connection account
need to perfom the backup. I would like to give the account the minimum
permissions needed.
Ed
--
EdThere is a built in SQL Server role called "db_backupoperator".
"Ed" <Ed@.discussions.microsoft.com> wrote in message
news:6EF64E64-B72C-4C84-9AD8-1F9B3072758A@.microsoft.com...
>I have a MS SQL database process that is run from ASP.NET.
> I would like to be able to backup the SQL database using either
> a full database or transaction log backup immediately before the
> process is done. Is this possible with ASP.NET and
> what kind of permissions or role would the SQL connection account
> need to perfom the backup. I would like to give the account the minimum
> permissions needed.
> --
> Ed
> --
> Ed

Migraton from Enterprise to Standard

H
I wan to migrate an SQL Enterprise server system to SQL Standard system
Can somebody guide me throgh the process
Thank
KNDHi,
Is it a SQL2000? If so, refer:
'INF: Effects of Moving a Database from SQL 2000 Enterprise Edition to SQL
2000 Standard Edition'
http://support.microsoft.com/default.aspx?id=268361
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"KND" <anonymous@.discussions.microsoft.com> wrote in message
news:52E54DFE-58E4-4D2B-93AB-49A9CA083F03@.microsoft.com...
> Hi
> I wan to migrate an SQL Enterprise server system to SQL Standard system.
> Can somebody guide me throgh the process?
> Thanks
> KND

Migration of SQL 7.0 package to SQL 2005

Did you try to migrate this package to SQL 2005. The migration process will
migrate the DTS package into SSIS, and encapsulate all functionality it
can't upgrade into mini DTS 2000 packages which will run as subpackages of
the SSIS Package. You can then at your leisure redesign the mini DTS 2000
packages into your SSIS package.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"a" <a@.b.c> wrote in message news:%23smBc8wMHHA.4000@.TK2MSFTNGP06.phx.gbl...
> Hi,
> We are migrating from SQL server 7.0 to SQL server 2005.
> In 7.0 I have made a DTS package that does a complex task on pre-scheduled
> times, started by a SQL job.
> This is a brief description of the complex task:
> -Copy files from several computers in the network to a local "working
> directory"
> -Verify the contents of the files (pre-formatted plain text files)
> -Move files with size or content errors to a different directory
> -Load the files that have no errors into a SQL server table (tblImport)
> -Mark records in tblImport that already exist in tblHistory
> -Gather user information about the files that have been succesfully loaded
> into tblImport
> -Create several reports (plain text files) based on the information in the
> files
> -Print the reports to different printers
> -Add the non-marked records in tblImport to tblHistory
> -Delete the non-marked records in tblImport
> -Send e-mails to several recipients with statistical information about the
> task
> This package is made with a number of activex scripts and SQL tasks.
> Because the server this package is running on now is outdated, I have the
> challenge to make this task work in SQL server 2005.
> The database it is using is already transferred to SQL 2005.
> I have seen that creating packages in 2005 is totally different than
> creating packages in 7.0.
> In SQL 7.0 I can save the packages into a .dts file, but in 2005 I can
> only
> load a .dtsx file.
> To me it is ok if I have to build the package in 2005 from scratch or
> build
> it in a totally different way, just as long as it is not taking me too
> much
> time. A different way could be that I copy and paste the scripts and SQL
> statements into several steps of a 2005 job, with some minor changes, but
> I'm not sure if that is a good solution. Especially when something goes
> wrong, I would like to know exactly where things went wrong and what steps
> have to be executed to finish the job.
> Any help or ideas are appreciated!
>
>
Can you save the dts packages as structured storage and then open them up in
SQL 2000 Package Designed and save them there and then try to use the
migration wizard?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"a" <a@.b.c> wrote in message news:uf19BVxMHHA.5016@.TK2MSFTNGP04.phx.gbl...
> Thanks for your response Hilary.
> Unfortunately the Migration Wizard is unable to connect to SQL 7.0. It
> gives
> me an error saying "This SQL Server version (7.0) is not supported."
>
> Hilary Cotter <hilary.cotter@.gmail.com> wrote in message
> news:O9525GxMHHA.5064@.TK2MSFTNGP04.phx.gbl...
> will
> news:%23smBc8wMHHA.4000@.TK2MSFTNGP06.phx.gbl...
> pre-scheduled
> loaded
> the
> the
> the
> but
> steps
>

Migrating to SQL 2005

I am interested in migrating from SQL 2000 to SQL 2005.
Are there some recommended pointers, sites, or steps involved in the process
that you could provide?
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200603/1Robert,
www.microsoft.com/sql is always a good place to look for info such as this.
Here is a link that should get you going.
http://www.microsoft.com/sql/solutions/upgrade/default.mspx
--
Andrew J. Kelly SQL MVP
"Robert R via SQLMonster.com" <u3288@.uwe> wrote in message
news:5d589ba26f68f@.uwe...
>I am interested in migrating from SQL 2000 to SQL 2005.
> Are there some recommended pointers, sites, or steps involved in the
> process
> that you could provide?
> --
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200603/1

Migrating to Report Services

Or rather, migrating to local reports using the Microsoft Report
Services.
We are in the process of planning the next generation of our software,
and among other things we are contemplating which reporting platform
we will use.
Until now we have been using Crystal Report, but it seems to be
getting more and more heavy to work with, plus it is a rather hefty
investment, well it can be.
First a little history:
- Our software will be running on anything from a stand-alone PC with
no connection to the surrounding world, to large-scale "enterprise"
networks with several dozens of clients. As a result our reporting
platform must be able to handle this.
Originally Crystal Report handled this very nicely, in that regard
that we simply installed the runtime libraries on each PC with our
software and a bunch of report files locally. This is model our
customers are used to.
Now I have decided to check out Reporting Services, but I have a bit
of a difficult time wrapping my mind around the concept. Some things
seem very nice and elegant, but others seem somewhat less so. For one
thing, the reports seem a little too simple and no where nearly as
powerful as Crystal Reports.
Now, our database is usually called the same regardless of the
customer, and of course, the layout of the database is always the same
(some customers may have a few custom tables, etc). But internally we
may have any number of databases that is named differently (customer
backups, test databases etc). So I need a way of being able to set the
database "on-the-fly".
What (I think) I need:
- A way of designing local reports and setting the data source at
runtime.
- I do not want to use the web server exclusively.
- Initially I want local reports, but the central reporting server can
be an option.
- I want to be able to mix tabular/matrix and chart reports.
- I want to be able to show group headers and footers, as well as page
headers and footers.
- I want to have full access to all tables in the database, and not
being restricted once I select on table, or entity.
Basically, I want to use the Reporting Service, but I don't want to
loose the freedom in data selection that Crystal Report gives me.According to your description, you need to use both SQL Server Reporting
Services and local report tool, which is bundled with VS2005/8 (VS2003 is
bundled with CrystalReport.NET as local report tool, while VS2005/8 come
with both CrystalReport.NET and MS report tool).
More comments inline.
"ThomasD" <tho.due@.gmail.com> wrote in message
news:4de6bed8-f6bc-4188-afd5-93ac01d49398@.8g2000hse.googlegroups.com...
> Or rather, migrating to local reports using the Microsoft Report
> Services.
> We are in the process of planning the next generation of our software,
> and among other things we are contemplating which reporting platform
> we will use.
> Until now we have been using Crystal Report, but it seems to be
> getting more and more heavy to work with, plus it is a rather hefty
> investment, well it can be.
> First a little history:
> - Our software will be running on anything from a stand-alone PC with
> no connection to the surrounding world, to large-scale "enterprise"
> networks with several dozens of clients. As a result our reporting
> platform must be able to handle this.
> Originally Crystal Report handled this very nicely, in that regard
> that we simply installed the runtime libraries on each PC with our
> software and a bunch of report files locally. This is model our
> customers are used to.
> Now I have decided to check out Reporting Services, but I have a bit
> of a difficult time wrapping my mind around the concept. Some things
> seem very nice and elegant, but others seem somewhat less so. For one
> thing, the reports seem a little too simple and no where nearly as
> powerful as Crystal Reports.
> Now, our database is usually called the same regardless of the
> customer, and of course, the layout of the database is always the same
> (some customers may have a few custom tables, etc). But internally we
> may have any number of databases that is named differently (customer
> backups, test databases etc). So I need a way of being able to set the
> database "on-the-fly".
> What (I think) I need:
> - A way of designing local reports and setting the data source at
> runtime.
If you have VS2005/8, you can do local report with either CrystalReport.NET
or MS report tool. By "Local". If you use SQL Server RS, I'd use MS report
tool in VS for local report, because the report viewer control can render
both local report and report from SQL Server RS. So, you app can seemlessly
dispaly report either from local report or from SQL Server RS without user
knowing the difference.
> - I do not want to use the web server exclusively.
> - Initially I want local reports, but the central reporting server can
> be an option.
> - I want to be able to mix tabular/matrix and chart reports.
> - I want to be able to show group headers and footers, as well as page
> headers and footers.
MS local report is a bit not as fancy as RS report can be.
> - I want to have full access to all tables in the database, and not
> being restricted once I select on table, or entity.
That has little to do with reporting, local or server.
> Basically, I want to use the Reporting Service, but I don't want to
> loose the freedom in data selection that Crystal Report gives me.
Do not know what "Data selection freedom" means here.
With local report, you can connect to whatever data source. If needed, you
can use code do trasform anything into a DataSet/Table of your desired
schema and use it as the report source, I'd think it is complete freedom.
With SQL Server RS, if the report data is difficult to access by reqular
queries, or the data source is not conventinal database, you can write your
own Data Processing Extensions sitting between the reporting processor and
data source. Of course, this requires lots of coding.|||> According to your description, you need to use both SQL Server Reporting
> Services and local report tool, which is bundled with VS2005/8 (VS2003 is
> bundled with CrystalReport.NET as local report tool, while VS2005/8 come
> with both CrystalReport.NET and MS report tool).
We use VS2008. I would like keep the option of using the report server
open, but my primary concern is local reports.
> More comments inline.
Cool. :)
> > - A way of designing local reports and setting the data source at
> > runtime.
> If you have VS2005/8, you can do local report with either CrystalReport.NET
> or MS report tool. By "Local". If you use SQL Server RS, I'd use MS report
> tool in VS for local report, because the report viewer control can render
> both local report and report from SQL Server RS. So, you app can seemlessly
> dispaly report either from local report or from SQL Server RS without user
> knowing the difference.
I finally managed to actually get the report designer working (it is
not easy to handle, when you are used to using Crystal Reports). It
looks very promising, however as it turns out, I have to supply the
data source "manually" when using the report locally. That is fine,
not a problem. However, I would like to use the SQL embedded in the
report, but that seems to be somewhat difficult to get at. So far I
have managed to get it by using XPath, but I can't help thinking that
there must be an easier way.
> MS local report is a bit not as fancy as RS report can be.
True, but I AM making progress in understanding the limitations and
differences.
> > - I want to have full access to all tables in the database, and not
> > being restricted once I select on table, or entity.
> That has little to do with reporting, local or server.
Well, after I "discovered" the report designer in Sql Server Business
Intelligence Development Studio (what a mouthful), I see that. Now I
just need to get a handle on the embedded SQL.
> > Basically, I want to use the Reporting Service, but I don't want to
> > loose the freedom in data selection that Crystal Report gives me.
> Do not know what "Data selection freedom" means here.
SQL. I don't want to be relying on some obscure model. Direct SQL
input is my preferred method of pulling data. Crystal Reports can do
both, and after discover the report designer in BI studio it looks
very promising.
> With local report, you can connect to whatever data source. If needed, you
> can use code do trasform anything into a DataSet/Table of your desired
> schema and use it as the report source, I'd think it is complete freedom.
> With SQL Server RS, if the report data is difficult to access by reqular
> queries, or the data source is not conventinal database, you can write your
> own Data Processing Extensions sitting between the reporting processor and
> data source. Of course, this requires lots of coding.
Coding doesn't scare me, I wouldn't be a software developer otherwise
*grin*
Regards,
Thomas