Hide Database in SQL SErver 2000

Dear All
I have a question on the security control of sql server 2000.
Now I set a specified sql account can access corresponding database only,
however, how can I hide other database that he not allowed to access, as
well as master, tempdb and other system database?
ThanksYou cannot do that in SQL Server 2000 but only in SQL Server 2005
"a" <a@.l.q> wrote in message
news:%23ZK8tMGBGHA.1676@.TK2MSFTNGP09.phx.gbl...
> Dear All
> I have a question on the security control of sql server 2000.
> Now I set a specified sql account can access corresponding database only,
> however, how can I hide other database that he not allowed to access, as
> well as master, tempdb and other system database?
> Thanks
>|||o....thanks
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:uu$cIZIBGHA.1032@.TK2MSFTNGP11.phx.gbl...
> You cannot do that in SQL Server 2000 but only in SQL Server 2005
>
> "a" <a@.l.q> wrote in message
> news:%23ZK8tMGBGHA.1676@.TK2MSFTNGP09.phx.gbl...
only,[vbcol=seagreen]
>

Help:I cannot subscription report

Dear all

I cannot subscription report when I finished setup that the following is the error message

An internal error occurred on the report server. See the error log for more details. (rsInternalError) Get Online Help The specified @.category_id ('101') does not exist.

The SQL agent have already start. I don't know what happen.

Can you look in the SSRS Logs and Event logs and grab some relevant information for us to digest?|||

I have already checked the log but it have any log for it.

How can I do?

Help: Job Failed (Error)

Dear All,
I have a DTS Package. When I run the package manually, it works, but
when it is executed by scheduled job, it always fail.
The error message is :
"Executed as user: <DOMAIN>\<Username>. The step did not generate any
output. Process Exit Code -1073741819. The step failed."
Pls help me to solve it out.
Thanks
Robert LieSee if this helps you understand what's happening:
http://support.microsoft.com/default.aspx?scid=kb;en-us;269074&sd=tech
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Robert Lie" <robert.lie24@.gmail.com> wrote in message
news:easHEE4kFHA.2472@.TK2MSFTNGP15.phx.gbl...
Dear All,
I have a DTS Package. When I run the package manually, it works, but
when it is executed by scheduled job, it always fail.
The error message is :
"Executed as user: <DOMAIN>\<Username>. The step did not generate any
output. Process Exit Code -1073741819. The step failed."
Pls help me to solve it out.
Thanks
Robert Lie

HELP: Installing SQl server databases

Dear all,
One of our application consist of configuring an SQL server database with
user rights to tables and preparing corresponding store procedure.
usually when we do this, we prepare the server in our test environment and
then ship the whole hardware pre configure to customers.
in some cases we do not have the customer server, so we need to do the whole
configuration on site and in cas of errors its hard to find.
is there an easy way to prepare the SQL confisuration database, store
procedure, table rights on a test PC, then do a kind of straight forward
deployement on any server running SQL ?
thanks for your help
regards
SergeHi,
You can create the customer database in your local sql server. Do all the
setups in that new database. backup the database or detach the database.
Copy the backup or MDF and LDF file and take it in a tape. Restore the files
from tape to Customer side server and
do a Database restore or Attach the MDF and LDF.
Incase if you have login an user suid mismacth use the system stored
procedure sp_change_users_login to fix.
This will ensure that all the configurations are avaiable.
Thanks
Hari
SQL Server MVP
"serge calderara" <sergecalderara@.discussions.microsoft.com> wrote in
message news:EDEAF3C8-903B-49D6-8A48-9FD1B71E379F@.microsoft.com...
> Dear all,
> One of our application consist of configuring an SQL server database with
> user rights to tables and preparing corresponding store procedure.
> usually when we do this, we prepare the server in our test environment and
> then ship the whole hardware pre configure to customers.
> in some cases we do not have the customer server, so we need to do the
> whole
> configuration on site and in cas of errors its hard to find.
> is there an easy way to prepare the SQL confisuration database, store
> procedure, table rights on a test PC, then do a kind of straight forward
> deployement on any server running SQL ?
> thanks for your help
> regards
> Serge|||I have seen the method suggested earlier about taking the mdf and ldf and
using sp_attach_Db and in most cases you should be OK ( except for
permissions.) However the risk you are taking is with the file version...
The physical files will only have a limited life span, as MS changes things
usually attach works for one release backwards...
Another way is to generate scripts... These take longer to run, but are
usually safer because basic syntax does not change that often...One thing
you might do is combine the two... In your release, generate the scripts.
Then when you are about to go and setup a db for a user, THEN run the
scripts, and take the resulting mdf and ldf...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"serge calderara" <sergecalderara@.discussions.microsoft.com> wrote in
message news:EDEAF3C8-903B-49D6-8A48-9FD1B71E379F@.microsoft.com...
> Dear all,
> One of our application consist of configuring an SQL server database with
> user rights to tables and preparing corresponding store procedure.
> usually when we do this, we prepare the server in our test environment and
> then ship the whole hardware pre configure to customers.
> in some cases we do not have the customer server, so we need to do the
> whole
> configuration on site and in cas of errors its hard to find.
> is there an easy way to prepare the SQL confisuration database, store
> procedure, table rights on a test PC, then do a kind of straight forward
> deployement on any server running SQL ?
> thanks for your help
> regards
> Serge|||I am a bit confuse as I am new in that part.
let say that my ServerA is my test server in my office on which I prepare
every thing
lets call ServerB the target server on which th final DB will run
Could you please details me which operation to do on which server?
What is the content of those MDF and LDF files ?
How to deploy rights or group from server A to ServerB at the same time
thanks and sorry to disturb
experince will come with the time :-)
serge
"Wayne Snyder" wrote:
> I have seen the method suggested earlier about taking the mdf and ldf and
> using sp_attach_Db and in most cases you should be OK ( except for
> permissions.) However the risk you are taking is with the file version...
> The physical files will only have a limited life span, as MS changes things
> usually attach works for one release backwards...
> Another way is to generate scripts... These take longer to run, but are
> usually safer because basic syntax does not change that often...One thing
> you might do is combine the two... In your release, generate the scripts.
> Then when you are about to go and setup a db for a user, THEN run the
> scripts, and take the resulting mdf and ldf...
>
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "serge calderara" <sergecalderara@.discussions.microsoft.com> wrote in
> message news:EDEAF3C8-903B-49D6-8A48-9FD1B71E379F@.microsoft.com...
> > Dear all,
> >
> > One of our application consist of configuring an SQL server database with
> > user rights to tables and preparing corresponding store procedure.
> >
> > usually when we do this, we prepare the server in our test environment and
> > then ship the whole hardware pre configure to customers.
> >
> > in some cases we do not have the customer server, so we need to do the
> > whole
> > configuration on site and in cas of errors its hard to find.
> >
> > is there an easy way to prepare the SQL confisuration database, store
> > procedure, table rights on a test PC, then do a kind of straight forward
> > deployement on any server running SQL ?
> >
> > thanks for your help
> > regards
> > Serge
>
>|||On ServerA you will prepare the database to be installed, call it DBa. Once
this is complete you have 2 choices. 1) You can dump DBa and use the
resulting dump file, or 2) you can detach DBa and use the MDF and LDF files.
Copy either the dump file or MDF and LDF files to ServerB.
If you selected the database dump option, restore DBa. See Books Online for
the syntax.
If you selected the detach option, attach DBa. Again see Books Online for
the syntax.
As mentioned in one of the earlier posts if you created any data server
logins and database users you will need to fix those up via the
sp_change_users_login stored proc. See Books Online for documentation.
"serge calderara" wrote:
> I am a bit confuse as I am new in that part.
> let say that my ServerA is my test server in my office on which I prepare
> every thing
> lets call ServerB the target server on which th final DB will run
> Could you please details me which operation to do on which server?
> What is the content of those MDF and LDF files ?
> How to deploy rights or group from server A to ServerB at the same time
> thanks and sorry to disturb
> experince will come with the time :-)
> serge
> "Wayne Snyder" wrote:
> > I have seen the method suggested earlier about taking the mdf and ldf and
> > using sp_attach_Db and in most cases you should be OK ( except for
> > permissions.) However the risk you are taking is with the file version...
> > The physical files will only have a limited life span, as MS changes things
> > usually attach works for one release backwards...
> >
> > Another way is to generate scripts... These take longer to run, but are
> > usually safer because basic syntax does not change that often...One thing
> > you might do is combine the two... In your release, generate the scripts.
> > Then when you are about to go and setup a db for a user, THEN run the
> > scripts, and take the resulting mdf and ldf...
> >
> >
> > --
> > Wayne Snyder, MCDBA, SQL Server MVP
> > Mariner, Charlotte, NC
> > www.mariner-usa.com
> > (Please respond only to the newsgroups.)
> >
> > I support the Professional Association of SQL Server (PASS) and it's
> > community of SQL Server professionals.
> > www.sqlpass.org
> >
> > "serge calderara" <sergecalderara@.discussions.microsoft.com> wrote in
> > message news:EDEAF3C8-903B-49D6-8A48-9FD1B71E379F@.microsoft.com...
> > > Dear all,
> > >
> > > One of our application consist of configuring an SQL server database with
> > > user rights to tables and preparing corresponding store procedure.
> > >
> > > usually when we do this, we prepare the server in our test environment and
> > > then ship the whole hardware pre configure to customers.
> > >
> > > in some cases we do not have the customer server, so we need to do the
> > > whole
> > > configuration on site and in cas of errors its hard to find.
> > >
> > > is there an easy way to prepare the SQL confisuration database, store
> > > procedure, table rights on a test PC, then do a kind of straight forward
> > > deployement on any server running SQL ?
> > >
> > > thanks for your help
> > > regards
> > > Serge
> >
> >
> >

Help: error when trying to connect to server using sql server 2005 express

Dear all,

I have installed sql server 2005 Express with SQLADV.exe. But when I open Management Studio Express it has error:

Can not connect to server

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error locating Server/Instance Specified).

I searched on google but did not find any solution. Anyone know about that, please help me.

check this link http://blogs.msdn.com/sql_protocols/archive/2006/09/30/SQL-Server-2005-Remote-Connectivity-Issue-TroubleShooting.aspx

there are few things to be done to access database engine

(a) Remote connection to be enabled

(b) Create exception if firewall is enabled on this srever

(c) start SQL Browser service

(d) check the protocols

Madhu

|||

Dear Madhu K Nair,

I just use my local computer to test, how can I check for protocol and should I do it. Now I just use my computer to create a website and database in my computer too.

|||

check this http://support.microsoft.com/kb/914277

Madhu

|||

Please check my blog for this:

http://blogs.msdn.com/sql_protocols/archive/2007/05/13/sql-network-interfaces-error-26-error-locating-server-instance-specified.aspx

Help: Error Log

Dear all,
After I checked the SQL Server Log i found error like this:
1. Error: 17883, Severity: 1, State: 0
What does it mean?
2. Login failed for user 'sa'.
Almost every minute this error occured.
Does someone know what's happening to my SQL Server?
Thanks
Robert Lie
Robert,
1. This message means your scheduler appears to be hung. See the following
for more info:
New concurrency and scheduling diagnostics added to SQL Server
http://support.microsoft.com/kb/319892/
2. This means something is trying to login to SQL Server (and failing). Run
SQL Profiler to see what this is. Whatever it is, it shouldn't be using the
sa account.
Mark.
"Robert Lie" wrote:

> Dear all,
> After I checked the SQL Server Log i found error like this:
> 1. Error: 17883, Severity: 1, State: 0
> What does it mean?
> 2. Login failed for user 'sa'.
> Almost every minute this error occured.
> Does someone know what's happening to my SQL Server?
> Thanks
> Robert Lie
>

Help: Error Log

Dear all,
After I checked the SQL Server Log i found error like this:
1. Error: 17883, Severity: 1, State: 0
What does it mean?
2. Login failed for user 'sa'.
Almost every minute this error occured.
Does someone know what's happening to my SQL Server?
Thanks
Robert LieRobert,
1. This message means your scheduler appears to be hung. See the following
for more info:
New concurrency and scheduling diagnostics added to SQL Server
http://support.microsoft.com/kb/319892/
2. This means something is trying to login to SQL Server (and failing). Run
SQL Profiler to see what this is. Whatever it is, it shouldn't be using the
sa account.
Mark.
"Robert Lie" wrote:

> Dear all,
> After I checked the SQL Server Log i found error like this:
> 1. Error: 17883, Severity: 1, State: 0
> What does it mean?
> 2. Login failed for user 'sa'.
> Almost every minute this error occured.
> Does someone know what's happening to my SQL Server?
> Thanks
> Robert Lie
>

Help: Error Log

Dear all,
After I checked the SQL Server Log i found error like this:
1. Error: 17883, Severity: 1, State: 0
What does it mean?
2. Login failed for user 'sa'.
Almost every minute this error occured.
Does someone know what's happening to my SQL Server?
Thanks
Robert LieRobert,
1. This message means your scheduler appears to be hung. See the following
for more info:
New concurrency and scheduling diagnostics added to SQL Server
http://support.microsoft.com/kb/319892/
2. This means something is trying to login to SQL Server (and failing). Run
SQL Profiler to see what this is. Whatever it is, it shouldn't be using the
sa account.
Mark.
"Robert Lie" wrote:
> Dear all,
> After I checked the SQL Server Log i found error like this:
> 1. Error: 17883, Severity: 1, State: 0
> What does it mean?
> 2. Login failed for user 'sa'.
> Almost every minute this error occured.
> Does someone know what's happening to my SQL Server?
> Thanks
> Robert Lie
>

Help: Can I load all table content to the memory during SQL server Startup?

Dear Sir,
I use SQL 2000 server. I want to load all the table content to the
memory the SQL server startup.
How can I do that?
My computer has 2 G RAM. The total space of the databse is 1G.
I have set the mininum memory is 1G (in dynamic configue SQL memory) in SQL
server and check the "Reserved physical memory for SQL server". But no all
data load into the memory during SQL server startup.
I just know that if I write a SQL statement to request records, these
records will be load into memory.
SO, I think it is not a good method to select all tables once after the SQL
server just startup.
Thank you for your help!
--
Regards,
Anthony LamAssuming you really want to do this, create a stored procedure which reads the rows and mark it as a
startup proc (sp_procoption).
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as ugroup=microsoft.public.sqlserver
"AA" <anthony@.jadeflex.com> wrote in message news:%23ARNLe$gDHA.3272@.tk2msftngp13.phx.gbl...
> Dear Sir,
> I use SQL 2000 server. I want to load all the table content to the
> memory the SQL server startup.
> How can I do that?
> My computer has 2 G RAM. The total space of the databse is 1G.
> I have set the mininum memory is 1G (in dynamic configue SQL memory) in SQL
> server and check the "Reserved physical memory for SQL server". But no all
> data load into the memory during SQL server startup.
> I just know that if I write a SQL statement to request records, these
> records will be load into memory.
> SO, I think it is not a good method to select all tables once after the SQL
> server just startup.
> Thank you for your help!
> --
> Regards,
> Anthony Lam
>

Help: Backup Question

Dear All,
Does anyone can help me up to answer the question below:
=============
You are the administrator of a SQL Server 2000 computer The server
contains a database named Sales that has two data files and one
transaction log file. Each data file is located on its own hard disk and
exists in its own filegroup. You perform full database, differential,
and transaction log backups on a regular basis. All backups made during
a single week are striped across three disk backup devices. A portion of
the header information for the current week's backups is shown in the
following table
BackupName BackupType BackupFinishDate
Sales_db_20000625 1 2000-06-25 21 57 04.000
Sales_tl_20000626_1 2 2000-06-26 11 04 22.000
Sales_tl_20000626_2 2 2000-06-26 15 06 33.000
Sales_df_20000626 5 2000-06-26 21 15 48.000
Sales_tl_20000627_1 2 2000-06-27 11 03 39.000
Sales_tl_20000627_2 2 2000-06-27 15 04 59.000
Sales_df_20000627 5 2000-06-27 21 31 13.000
Sales_tl_20000628_1 2 2000-06-28 11 05 16.000
On June 28, 2000, at 1:47 P M , the hard disk that contains the PRIMARY
filegroup fails. You want to recover as much data as possible. What
should you do? (Each correct answer presents part of the solution,
Choose all that apply)
A. Backup the transaction log by using the NO_LOG option
B. Backup the transaction log by using the NO_TRUNCATE option
C. Restore the most recent full database backup
D. Restore the most recent differential backup
E. Restore all differential backups in sequence
F. Restore all transaction log backups in sequence
G. Restore all transaction logs since the most recent differential backup
===================
Thanks
Robert Lie
Robert,
I will say:
B, C, D, G (with no recovery) and then restore the backup done in option B
with RECOVERY.
AMB
"Robert Lie" wrote:

> Dear All,
> Does anyone can help me up to answer the question below:
>
> =============
> You are the administrator of a SQL Server 2000 computer The server
> contains a database named Sales that has two data files and one
> transaction log file. Each data file is located on its own hard disk and
> exists in its own filegroup. You perform full database, differential,
> and transaction log backups on a regular basis. All backups made during
> a single week are striped across three disk backup devices. A portion of
> the header information for the current week's backups is shown in the
> following table
> BackupName BackupType BackupFinishDate
> Sales_db_20000625 1 2000-06-25 21 57 04.000
> Sales_tl_20000626_1 2 2000-06-26 11 04 22.000
> Sales_tl_20000626_2 2 2000-06-26 15 06 33.000
> Sales_df_20000626 5 2000-06-26 21 15 48.000
> Sales_tl_20000627_1 2 2000-06-27 11 03 39.000
> Sales_tl_20000627_2 2 2000-06-27 15 04 59.000
> Sales_df_20000627 5 2000-06-27 21 31 13.000
> Sales_tl_20000628_1 2 2000-06-28 11 05 16.000
>
> On June 28, 2000, at 1:47 P M , the hard disk that contains the PRIMARY
> filegroup fails. You want to recover as much data as possible. What
> should you do? (Each correct answer presents part of the solution,
> Choose all that apply)
> A. Backup the transaction log by using the NO_LOG option
> B. Backup the transaction log by using the NO_TRUNCATE option
> C. Restore the most recent full database backup
> D. Restore the most recent differential backup
> E. Restore all differential backups in sequence
> F. Restore all transaction log backups in sequence
> G. Restore all transaction logs since the most recent differential backup
> ===================
>
> Thanks
> Robert Lie
>
|||Dear Alejandro Mesa,
Can you explain to me what's the meaning of number at the "Backup Type"
column?
Thanks
Robert Lie
Alejandro Mesa wrote:[vbcol=seagreen]
> Robert,
> I will say:
> B, C, D, G (with no recovery) and then restore the backup done in option B
> with RECOVERY.
>
> AMB
> "Robert Lie" wrote:
>
|||Hi,
Backup types: -
1 = Database
2 = Transaction Log
4 = File
5 = Differential Database
6 = Differential File
Thanks
Hari
SQL Server MVP
"Robert Lie" <robert.lie24@.gmail.com> wrote in message
news:eu3vQsfYFHA.4036@.tk2msftngp13.phx.gbl...[vbcol=seagreen]
> Dear Alejandro Mesa,
> Can you explain to me what's the meaning of number at the "Backup Type"
> column?
> Thanks
> Robert Lie
> Alejandro Mesa wrote:
|||I guess it is:
1 - db backup
2 - transaction log backup
5 - db differential backup.
Example:
use northwind
go
alter database northwind set recovery bulk_logged
go
backup database northwind to disk = 'c:\temp\nw.bak'
go
backup database northwind to disk = 'c:\temp\nw_diff.bak' with differential
go
backup log northwind to disk = 'c:\temp\nw_log.bak'
go
restore HEADERONLY from disk = 'c:\temp\nw.bak'
go
restore HEADERONLY from disk = 'c:\temp\nw_diff.bak'
go
restore HEADERONLY from disk = 'c:\temp\nw_log.bak'
go
alter database northwind set recovery simple
go
exec master..xp_cmdshell 'del c:\temp\nw*.bak'
go
AMB
"Robert Lie" wrote:

> Dear Alejandro Mesa,
> Can you explain to me what's the meaning of number at the "Backup Type"
> column?
> Thanks
> Robert Lie
> Alejandro Mesa wrote:
>
|||Instead of keep asking all the questions from the tests, it might be better
if you start reading some litterature about MS SQL Server. A good and easy
place to start, would be to read Books On Line - that's a great ressource to
start with....
Regards
Steen
Robert Lie wrote:[vbcol=seagreen]
> Dear Alejandro Mesa,
> Can you explain to me what's the meaning of number at the "Backup
> Type" column?
> Thanks
> Robert Lie
> Alejandro Mesa wrote:

Help: Backup Question

Dear All,
Does anyone can help me up to answer the question below:
=============
You are the administrator of a SQL Server 2000 computer The server
contains a database named Sales that has two data files and one
transaction log file. Each data file is located on its own hard disk and
exists in its own filegroup. You perform full database, differential,
and transaction log backups on a regular basis. All backups made during
a single week are striped across three disk backup devices. A portion of
the header information for the current week's backups is shown in the
following table
BackupName BackupType BackupFinishDate
Sales_db_20000625 1 2000-06-25 21 57 04.000
Sales_tl_20000626_1 2 2000-06-26 11 04 22.000
Sales_tl_20000626_2 2 2000-06-26 15 06 33.000
Sales_df_20000626 5 2000-06-26 21 15 48.000
Sales_tl_20000627_1 2 2000-06-27 11 03 39.000
Sales_tl_20000627_2 2 2000-06-27 15 04 59.000
Sales_df_20000627 5 2000-06-27 21 31 13.000
Sales_tl_20000628_1 2 2000-06-28 11 05 16.000
On June 28, 2000, at 1:47 P M , the hard disk that contains the PRIMARY
filegroup fails. You want to recover as much data as possible. What
should you do? (Each correct answer presents part of the solution,
Choose all that apply)
A. Backup the transaction log by using the NO_LOG option
B. Backup the transaction log by using the NO_TRUNCATE option
C. Restore the most recent full database backup
D. Restore the most recent differential backup
E. Restore all differential backups in sequence
F. Restore all transaction log backups in sequence
G. Restore all transaction logs since the most recent differential backup
===================
Thanks
Robert LieRobert,
I will say:
B, C, D, G (with no recovery) and then restore the backup done in option B
with RECOVERY.
AMB
"Robert Lie" wrote:

> Dear All,
> Does anyone can help me up to answer the question below:
>
> =============
> You are the administrator of a SQL Server 2000 computer The server
> contains a database named Sales that has two data files and one
> transaction log file. Each data file is located on its own hard disk and
> exists in its own filegroup. You perform full database, differential,
> and transaction log backups on a regular basis. All backups made during
> a single week are striped across three disk backup devices. A portion of
> the header information for the current week's backups is shown in the
> following table
> BackupName BackupType BackupFinishDate
> Sales_db_20000625 1 2000-06-25 21 57 04.000
> Sales_tl_20000626_1 2 2000-06-26 11 04 22.000
> Sales_tl_20000626_2 2 2000-06-26 15 06 33.000
> Sales_df_20000626 5 2000-06-26 21 15 48.000
> Sales_tl_20000627_1 2 2000-06-27 11 03 39.000
> Sales_tl_20000627_2 2 2000-06-27 15 04 59.000
> Sales_df_20000627 5 2000-06-27 21 31 13.000
> Sales_tl_20000628_1 2 2000-06-28 11 05 16.000
>
> On June 28, 2000, at 1:47 P M , the hard disk that contains the PRIMARY
> filegroup fails. You want to recover as much data as possible. What
> should you do? (Each correct answer presents part of the solution,
> Choose all that apply)
> A. Backup the transaction log by using the NO_LOG option
> B. Backup the transaction log by using the NO_TRUNCATE option
> C. Restore the most recent full database backup
> D. Restore the most recent differential backup
> E. Restore all differential backups in sequence
> F. Restore all transaction log backups in sequence
> G. Restore all transaction logs since the most recent differential backup
> ===================
>
> Thanks
> Robert Lie
>|||Dear Alejandro Mesa,
Can you explain to me what's the meaning of number at the "Backup Type"
column?
Thanks
Robert Lie
Alejandro Mesa wrote:[vbcol=seagreen]
> Robert,
> I will say:
> B, C, D, G (with no recovery) and then restore the backup done in option B
> with RECOVERY.
>
> AMB
> "Robert Lie" wrote:
>|||Hi,
Backup types: -
1 = Database
2 = Transaction Log
4 = File
5 = Differential Database
6 = Differential File
Thanks
Hari
SQL Server MVP
"Robert Lie" <robert.lie24@.gmail.com> wrote in message
news:eu3vQsfYFHA.4036@.tk2msftngp13.phx.gbl...[vbcol=seagreen]
> Dear Alejandro Mesa,
> Can you explain to me what's the meaning of number at the "Backup Type"
> column?
> Thanks
> Robert Lie
> Alejandro Mesa wrote:|||I guess it is:
1 - db backup
2 - transaction log backup
5 - db differential backup.
Example:
use northwind
go
alter database northwind set recovery bulk_logged
go
backup database northwind to disk = 'c:\temp\nw.bak'
go
backup database northwind to disk = 'c:\temp\nw_diff.bak' with differential
go
backup log northwind to disk = 'c:\temp\nw_log.bak'
go
restore HEADERONLY from disk = 'c:\temp\nw.bak'
go
restore HEADERONLY from disk = 'c:\temp\nw_diff.bak'
go
restore HEADERONLY from disk = 'c:\temp\nw_log.bak'
go
alter database northwind set recovery simple
go
exec master..xp_cmdshell 'del c:\temp\nw*.bak'
go
AMB
"Robert Lie" wrote:

> Dear Alejandro Mesa,
> Can you explain to me what's the meaning of number at the "Backup Type"
> column?
> Thanks
> Robert Lie
> Alejandro Mesa wrote:
>|||Instead of keep asking all the questions from the tests, it might be better
if you start reading some litterature about MS SQL Server. A good and easy
place to start, would be to read Books On Line - that's a great ressource to
start with....
Regards
Steen
Robert Lie wrote:[vbcol=seagreen]
> Dear Alejandro Mesa,
> Can you explain to me what's the meaning of number at the "Backup
> Type" column?
> Thanks
> Robert Lie
> Alejandro Mesa wrote:

Help: Backup Question

Dear All,
Does anyone can help me up to answer the question below:
============= You are the administrator of a SQL Server 2000 computer The server
contains a database named Sales that has two data files and one
transaction log file. Each data file is located on its own hard disk and
exists in its own filegroup. You perform full database, differential,
and transaction log backups on a regular basis. All backups made during
a single week are striped across three disk backup devices. A portion of
the header information for the current week's backups is shown in the
following table
BackupName BackupType BackupFinishDate
Sales_db_20000625 1 2000-06-25 21 57 04.000
Sales_tl_20000626_1 2 2000-06-26 11 04 22.000
Sales_tl_20000626_2 2 2000-06-26 15 06 33.000
Sales_df_20000626 5 2000-06-26 21 15 48.000
Sales_tl_20000627_1 2 2000-06-27 11 03 39.000
Sales_tl_20000627_2 2 2000-06-27 15 04 59.000
Sales_df_20000627 5 2000-06-27 21 31 13.000
Sales_tl_20000628_1 2 2000-06-28 11 05 16.000
On June 28, 2000, at 1:47 P M , the hard disk that contains the PRIMARY
filegroup fails. You want to recover as much data as possible. What
should you do? (Each correct answer presents part of the solution,
Choose all that apply)
A. Backup the transaction log by using the NO_LOG option
B. Backup the transaction log by using the NO_TRUNCATE option
C. Restore the most recent full database backup
D. Restore the most recent differential backup
E. Restore all differential backups in sequence
F. Restore all transaction log backups in sequence
G. Restore all transaction logs since the most recent differential backup
===================
Thanks
Robert LieRobert,
I will say:
B, C, D, G (with no recovery) and then restore the backup done in option B
with RECOVERY.
AMB
"Robert Lie" wrote:
> Dear All,
> Does anyone can help me up to answer the question below:
>
> =============> You are the administrator of a SQL Server 2000 computer The server
> contains a database named Sales that has two data files and one
> transaction log file. Each data file is located on its own hard disk and
> exists in its own filegroup. You perform full database, differential,
> and transaction log backups on a regular basis. All backups made during
> a single week are striped across three disk backup devices. A portion of
> the header information for the current week's backups is shown in the
> following table
> BackupName BackupType BackupFinishDate
> Sales_db_20000625 1 2000-06-25 21 57 04.000
> Sales_tl_20000626_1 2 2000-06-26 11 04 22.000
> Sales_tl_20000626_2 2 2000-06-26 15 06 33.000
> Sales_df_20000626 5 2000-06-26 21 15 48.000
> Sales_tl_20000627_1 2 2000-06-27 11 03 39.000
> Sales_tl_20000627_2 2 2000-06-27 15 04 59.000
> Sales_df_20000627 5 2000-06-27 21 31 13.000
> Sales_tl_20000628_1 2 2000-06-28 11 05 16.000
>
> On June 28, 2000, at 1:47 P M , the hard disk that contains the PRIMARY
> filegroup fails. You want to recover as much data as possible. What
> should you do? (Each correct answer presents part of the solution,
> Choose all that apply)
> A. Backup the transaction log by using the NO_LOG option
> B. Backup the transaction log by using the NO_TRUNCATE option
> C. Restore the most recent full database backup
> D. Restore the most recent differential backup
> E. Restore all differential backups in sequence
> F. Restore all transaction log backups in sequence
> G. Restore all transaction logs since the most recent differential backup
> ===================>
> Thanks
> Robert Lie
>|||Dear Alejandro Mesa,
Can you explain to me what's the meaning of number at the "Backup Type"
column?
Thanks
Robert Lie
Alejandro Mesa wrote:
> Robert,
> I will say:
> B, C, D, G (with no recovery) and then restore the backup done in option B
> with RECOVERY.
>
> AMB
> "Robert Lie" wrote:
>
>>Dear All,
>>Does anyone can help me up to answer the question below:
>>
>>=============>>You are the administrator of a SQL Server 2000 computer The server
>>contains a database named Sales that has two data files and one
>>transaction log file. Each data file is located on its own hard disk and
>>exists in its own filegroup. You perform full database, differential,
>>and transaction log backups on a regular basis. All backups made during
>>a single week are striped across three disk backup devices. A portion of
>>the header information for the current week's backups is shown in the
>>following table
>>BackupName BackupType BackupFinishDate
>>Sales_db_20000625 1 2000-06-25 21 57 04.000
>>Sales_tl_20000626_1 2 2000-06-26 11 04 22.000
>>Sales_tl_20000626_2 2 2000-06-26 15 06 33.000
>>Sales_df_20000626 5 2000-06-26 21 15 48.000
>>Sales_tl_20000627_1 2 2000-06-27 11 03 39.000
>>Sales_tl_20000627_2 2 2000-06-27 15 04 59.000
>>Sales_df_20000627 5 2000-06-27 21 31 13.000
>>Sales_tl_20000628_1 2 2000-06-28 11 05 16.000
>>
>>On June 28, 2000, at 1:47 P M , the hard disk that contains the PRIMARY
>>filegroup fails. You want to recover as much data as possible. What
>>should you do? (Each correct answer presents part of the solution,
>>Choose all that apply)
>>A. Backup the transaction log by using the NO_LOG option
>>B. Backup the transaction log by using the NO_TRUNCATE option
>>C. Restore the most recent full database backup
>>D. Restore the most recent differential backup
>>E. Restore all differential backups in sequence
>>F. Restore all transaction log backups in sequence
>>G. Restore all transaction logs since the most recent differential backup
>>===================>>
>>Thanks
>>Robert Lie|||I guess it is:
1 - db backup
2 - transaction log backup
5 - db differential backup.
Example:
use northwind
go
alter database northwind set recovery bulk_logged
go
backup database northwind to disk = 'c:\temp\nw.bak'
go
backup database northwind to disk = 'c:\temp\nw_diff.bak' with differential
go
backup log northwind to disk = 'c:\temp\nw_log.bak'
go
restore HEADERONLY from disk = 'c:\temp\nw.bak'
go
restore HEADERONLY from disk = 'c:\temp\nw_diff.bak'
go
restore HEADERONLY from disk = 'c:\temp\nw_log.bak'
go
alter database northwind set recovery simple
go
exec master..xp_cmdshell 'del c:\temp\nw*.bak'
go
AMB
"Robert Lie" wrote:
> Dear Alejandro Mesa,
> Can you explain to me what's the meaning of number at the "Backup Type"
> column?
> Thanks
> Robert Lie
> Alejandro Mesa wrote:
> > Robert,
> >
> > I will say:
> >
> > B, C, D, G (with no recovery) and then restore the backup done in option B
> > with RECOVERY.
> >
> >
> > AMB
> >
> > "Robert Lie" wrote:
> >
> >
> >>Dear All,
> >>
> >>Does anyone can help me up to answer the question below:
> >>
> >>
> >>=============> >>You are the administrator of a SQL Server 2000 computer The server
> >>contains a database named Sales that has two data files and one
> >>transaction log file. Each data file is located on its own hard disk and
> >>exists in its own filegroup. You perform full database, differential,
> >>and transaction log backups on a regular basis. All backups made during
> >>a single week are striped across three disk backup devices. A portion of
> >>the header information for the current week's backups is shown in the
> >>following table
> >>
> >>BackupName BackupType BackupFinishDate
> >>Sales_db_20000625 1 2000-06-25 21 57 04.000
> >>Sales_tl_20000626_1 2 2000-06-26 11 04 22.000
> >>Sales_tl_20000626_2 2 2000-06-26 15 06 33.000
> >>Sales_df_20000626 5 2000-06-26 21 15 48.000
> >>Sales_tl_20000627_1 2 2000-06-27 11 03 39.000
> >>Sales_tl_20000627_2 2 2000-06-27 15 04 59.000
> >>Sales_df_20000627 5 2000-06-27 21 31 13.000
> >>Sales_tl_20000628_1 2 2000-06-28 11 05 16.000
> >>
> >>
> >>On June 28, 2000, at 1:47 P M , the hard disk that contains the PRIMARY
> >>filegroup fails. You want to recover as much data as possible. What
> >>should you do? (Each correct answer presents part of the solution,
> >>Choose all that apply)
> >>
> >>A. Backup the transaction log by using the NO_LOG option
> >>B. Backup the transaction log by using the NO_TRUNCATE option
> >>C. Restore the most recent full database backup
> >>D. Restore the most recent differential backup
> >>E. Restore all differential backups in sequence
> >>F. Restore all transaction log backups in sequence
> >>G. Restore all transaction logs since the most recent differential backup
> >>
> >>===================> >>
> >>
> >>Thanks
> >>
> >>Robert Lie
> >>
>|||Hi,
Backup types: -
1 = Database
2 = Transaction Log
4 = File
5 = Differential Database
6 = Differential File
Thanks
Hari
SQL Server MVP
"Robert Lie" <robert.lie24@.gmail.com> wrote in message
news:eu3vQsfYFHA.4036@.tk2msftngp13.phx.gbl...
> Dear Alejandro Mesa,
> Can you explain to me what's the meaning of number at the "Backup Type"
> column?
> Thanks
> Robert Lie
> Alejandro Mesa wrote:
>> Robert,
>> I will say:
>> B, C, D, G (with no recovery) and then restore the backup done in option
>> B with RECOVERY.
>>
>> AMB
>> "Robert Lie" wrote:
>>
>>Dear All,
>>Does anyone can help me up to answer the question below:
>>
>>=============>>You are the administrator of a SQL Server 2000 computer The server
>>contains a database named Sales that has two data files and one
>>transaction log file. Each data file is located on its own hard disk and
>>exists in its own filegroup. You perform full database, differential, and
>>transaction log backups on a regular basis. All backups made during a
>>single week are striped across three disk backup devices. A portion of
>>the header information for the current week's backups is shown in the
>>following table
>>BackupName BackupType BackupFinishDate
>>Sales_db_20000625 1 2000-06-25 21 57 04.000
>>Sales_tl_20000626_1 2 2000-06-26 11 04 22.000
>>Sales_tl_20000626_2 2 2000-06-26 15 06 33.000
>>Sales_df_20000626 5 2000-06-26 21 15 48.000
>>Sales_tl_20000627_1 2 2000-06-27 11 03 39.000
>>Sales_tl_20000627_2 2 2000-06-27 15 04 59.000
>>Sales_df_20000627 5 2000-06-27 21 31 13.000
>>Sales_tl_20000628_1 2 2000-06-28 11 05 16.000
>>
>>On June 28, 2000, at 1:47 P M , the hard disk that contains the PRIMARY
>>filegroup fails. You want to recover as much data as possible. What
>>should you do? (Each correct answer presents part of the solution, Choose
>>all that apply)
>>A. Backup the transaction log by using the NO_LOG option
>>B. Backup the transaction log by using the NO_TRUNCATE option
>>C. Restore the most recent full database backup
>>D. Restore the most recent differential backup
>>E. Restore all differential backups in sequence
>>F. Restore all transaction log backups in sequence
>>G. Restore all transaction logs since the most recent differential
>>backup
>>===================>>
>>Thanks
>>Robert Lie|||Instead of keep asking all the questions from the tests, it might be better
if you start reading some litterature about MS SQL Server. A good and easy
place to start, would be to read Books On Line - that's a great ressource to
start with....
Regards
Steen
Robert Lie wrote:
> Dear Alejandro Mesa,
> Can you explain to me what's the meaning of number at the "Backup
> Type" column?
> Thanks
> Robert Lie
> Alejandro Mesa wrote:
>> Robert,
>> I will say:
>> B, C, D, G (with no recovery) and then restore the backup done in
>> option B with RECOVERY.
>>
>> AMB
>> "Robert Lie" wrote:
>>
>> Dear All,
>> Does anyone can help me up to answer the question below:
>>
>> =============>> You are the administrator of a SQL Server 2000 computer The server
>> contains a database named Sales that has two data files and one
>> transaction log file. Each data file is located on its own hard
>> disk and exists in its own filegroup. You perform full database,
>> differential, and transaction log backups on a regular basis. All
>> backups made
>> during a single week are striped across three disk backup devices. A
>> portion of the header information for the current week's backups is
>> shown in the following table
>> BackupName BackupType BackupFinishDate
>> Sales_db_20000625 1 2000-06-25 21 57 04.000
>> Sales_tl_20000626_1 2 2000-06-26 11 04 22.000
>> Sales_tl_20000626_2 2 2000-06-26 15 06 33.000
>> Sales_df_20000626 5 2000-06-26 21 15 48.000
>> Sales_tl_20000627_1 2 2000-06-27 11 03 39.000
>> Sales_tl_20000627_2 2 2000-06-27 15 04 59.000
>> Sales_df_20000627 5 2000-06-27 21 31 13.000
>> Sales_tl_20000628_1 2 2000-06-28 11 05 16.000
>>
>> On June 28, 2000, at 1:47 P M , the hard disk that contains the
>> PRIMARY filegroup fails. You want to recover as much data as
>> possible. What should you do? (Each correct answer presents part of
>> the solution, Choose all that apply)
>> A. Backup the transaction log by using the NO_LOG option
>> B. Backup the transaction log by using the NO_TRUNCATE option
>> C. Restore the most recent full database backup
>> D. Restore the most recent differential backup
>> E. Restore all differential backups in sequence
>> F. Restore all transaction log backups in sequence
>> G. Restore all transaction logs since the most recent differential
>> backup ===================>>
>> Thanks
>> Robert Lie