MSDE 2000 how many users

How many users and transaction can handle MSDE 2000. I have an application w
ith 2 pc and I would like to know if MSDE 2000 would work perfectly on that
environment. I was reading the MSDE documentation and I did not found anythi
ng about it. Any additional information I would appreciate.
Sincerely,
RafaelHi
There is quite alot of information in Books Online which can be downloaded
at
http://www.microsoft.com/downloads/...&displaylang=en
For information on the workload govenor see
http://msdn.microsoft.com/library/d...r />
_0neh.asp
http://msdn.microsoft.com/library/d...r />
_5fs6.asp
For capacity details see
http://msdn.microsoft.com/library/d...br />
8dbn.asp
For features see
http://msdn.microsoft.com/library/d...br />
8dbn.asp
If you have two users each with a single connection, you should be fine. You
throughput may be limited by the specification of the machine that it is
running on.
John
"Rafael Tejera" wrote:

> How many users and transaction can handle MSDE 2000. I have an application with 2
pc and I would like to know if MSDE 2000 would work perfectly on that environment. I
was reading the MSDE documentation and I did not found anything about it. Any addit
ion
al information I would appreciate.
> Sincerely,
>
> Rafael|||Why not use SQL Server 2005 Express Edition?
David
"Rafael Tejera" <rafaeltejera@.hotmail.com> wrote in message news:uDRTNf9iGHA
.836@.TK2MSFTNGP02.phx.gbl...
How many users and transaction can handle MSDE 2000. I have an application w
ith 2 pc and I would like to know if MSDE 2000 would work perfectly on that
environment. I was reading the MSDE documentation and I did not found anythi
ng about it. Any additional information I would appreciate.
Sincerely,
Rafael|||"Rafael Tejera" <rafaeltejera@.hotmail.com> wrote in message
news:uDRTNf9iGHA.836@.TK2MSFTNGP02.phx.gbl...
How many users and transaction can handle MSDE 2000. I have an application
with 2 pc and I would like to know if MSDE 2000 would work perfectly on that
environment. I was reading the MSDE documentation and I did not found
anything about it. Any additional information I would appreciate.
Depends on the PC hosting. Is it at least Win2000 or XP (Pro)?
Then no problem. I have a few clients running a small network all with
MSDE. They have 10 users on their network and only a few are ever in the
app at any time (5) .sql

msdb trascation logging mode

Hi,
I have a production SQL 2000 database with transaction logging turned on
('Full' recovery mode). I backup the transaction log every 15 minutes. In
order to use the point-in-time recovery option, do I also need to have the
'Full' recovery model set on the msdb? I ask this because I assume the msdb
holds information about the transaction log backup taken on the production
database. Without this information, I suspect point-in-time recover will not
be possible. Is my assumption correct?
Regards,
James G.Hi
MSDB is not needed to do point in time recovery. MSDB is just used to keep
the backup information so that Enterprise Manager UI can show you what
backups are available. It is a nice to have.
Point in time recovery needs the database dump and all the transaction log
dumps after that to the time you want to restore to.
Regards
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"James Goodwill" wrote:

> Hi,
> I have a production SQL 2000 database with transaction logging turned on
> ('Full' recovery mode). I backup the transaction log every 15 minutes. In
> order to use the point-in-time recovery option, do I also need to have the
> 'Full' recovery model set on the msdb? I ask this because I assume the msd
b
> holds information about the transaction log backup taken on the production
> database. Without this information, I suspect point-in-time recover will n
ot
> be possible. Is my assumption correct?
> Regards,
> James G.
>
>|||Hi James
The MSDB doesn't have to be in full recovery mode. In fact the MSDB
has no role when you run the restore. If the MSDB would have any role
in the restore then it would be impossible to restore the database on a
different server. All the data that is needed for the point in time
restore is stored in the log backup it self.
Adi|||Hi,
'Full' recovery model set on the msdb?
Ans:- NO NEED
I suspect point-in-time recover will not be possible. Is my assumption
correct?
No. You can do it with out a MSDB tranasction log backup.
MSDB database holds the backup history information. FOR each backup SQL
Server logs an entry into BACKUPSET table in MSDB database.
This is just an information only and will be useful if you use Enterprise
manager to do point in time recovery. Even if you
do not have tis information you can do a recovery based on Transaction log
file date and time. For a time based recovery:-
1. Restore the Full database backup first with Norecovery
2. Restore the logbackup file in sequence based on date and time with
Norecovery till last file
3. Restore the last transaction log backup with RECOVERY and STOPAT option.
Note:-
I am taking the MSDB full database backup daily once only.
Thanks
Hari
SQL Server MVP
"James Goodwill" <james.goodwill@.uk.fujitsu.com> wrote in message
news:DmmHe.10993$SO4.8738@.newsfe4-win.ntli.net...
> Hi,
> I have a production SQL 2000 database with transaction logging turned on
> ('Full' recovery mode). I backup the transaction log every 15 minutes. In
> order to use the point-in-time recovery option, do I also need to have the
> 'Full' recovery model set on the msdb? I ask this because I assume the
> msdb
> holds information about the transaction log backup taken on the production
> database. Without this information, I suspect point-in-time recover will
> not
> be possible. Is my assumption correct?
> Regards,
> James G.
>
>

msdb trascation logging mode

Hi,
I have a production SQL 2000 database with transaction logging turned on
('Full' recovery mode). I backup the transaction log every 15 minutes. In
order to use the point-in-time recovery option, do I also need to have the
'Full' recovery model set on the msdb? I ask this because I assume the msdb
holds information about the transaction log backup taken on the production
database. Without this information, I suspect point-in-time recover will not
be possible. Is my assumption correct?
Regards,
James G.
Hi
MSDB is not needed to do point in time recovery. MSDB is just used to keep
the backup information so that Enterprise Manager UI can show you what
backups are available. It is a nice to have.
Point in time recovery needs the database dump and all the transaction log
dumps after that to the time you want to restore to.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"James Goodwill" wrote:

> Hi,
> I have a production SQL 2000 database with transaction logging turned on
> ('Full' recovery mode). I backup the transaction log every 15 minutes. In
> order to use the point-in-time recovery option, do I also need to have the
> 'Full' recovery model set on the msdb? I ask this because I assume the msdb
> holds information about the transaction log backup taken on the production
> database. Without this information, I suspect point-in-time recover will not
> be possible. Is my assumption correct?
> Regards,
> James G.
>
>
|||Hi James
The MSDB doesn't have to be in full recovery mode. In fact the MSDB
has no role when you run the restore. If the MSDB would have any role
in the restore then it would be impossible to restore the database on a
different server. All the data that is needed for the point in time
restore is stored in the log backup it self.
Adi
|||Hi,
'Full' recovery model set on the msdb?
Ans:- NO NEED
I suspect point-in-time recover will not be possible. Is my assumption
correct?
No. You can do it with out a MSDB tranasction log backup.
MSDB database holds the backup history information. FOR each backup SQL
Server logs an entry into BACKUPSET table in MSDB database.
This is just an information only and will be useful if you use Enterprise
manager to do point in time recovery. Even if you
do not have tis information you can do a recovery based on Transaction log
file date and time. For a time based recovery:-
1. Restore the Full database backup first with Norecovery
2. Restore the logbackup file in sequence based on date and time with
Norecovery till last file
3. Restore the last transaction log backup with RECOVERY and STOPAT option.
Note:-
I am taking the MSDB full database backup daily once only.
Thanks
Hari
SQL Server MVP
"James Goodwill" <james.goodwill@.uk.fujitsu.com> wrote in message
news:DmmHe.10993$SO4.8738@.newsfe4-win.ntli.net...
> Hi,
> I have a production SQL 2000 database with transaction logging turned on
> ('Full' recovery mode). I backup the transaction log every 15 minutes. In
> order to use the point-in-time recovery option, do I also need to have the
> 'Full' recovery model set on the msdb? I ask this because I assume the
> msdb
> holds information about the transaction log backup taken on the production
> database. Without this information, I suspect point-in-time recover will
> not
> be possible. Is my assumption correct?
> Regards,
> James G.
>
>

msdb trascation logging mode

Hi,
I have a production SQL 2000 database with transaction logging turned on
('Full' recovery mode). I backup the transaction log every 15 minutes. In
order to use the point-in-time recovery option, do I also need to have the
'Full' recovery model set on the msdb? I ask this because I assume the msdb
holds information about the transaction log backup taken on the production
database. Without this information, I suspect point-in-time recover will not
be possible. Is my assumption correct?
Regards,
James G.Hi
MSDB is not needed to do point in time recovery. MSDB is just used to keep
the backup information so that Enterprise Manager UI can show you what
backups are available. It is a nice to have.
Point in time recovery needs the database dump and all the transaction log
dumps after that to the time you want to restore to.
Regards
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"James Goodwill" wrote:
> Hi,
> I have a production SQL 2000 database with transaction logging turned on
> ('Full' recovery mode). I backup the transaction log every 15 minutes. In
> order to use the point-in-time recovery option, do I also need to have the
> 'Full' recovery model set on the msdb? I ask this because I assume the msdb
> holds information about the transaction log backup taken on the production
> database. Without this information, I suspect point-in-time recover will not
> be possible. Is my assumption correct?
> Regards,
> James G.
>
>|||Hi James
The MSDB doesn't have to be in full recovery mode. In fact the MSDB
has no role when you run the restore. If the MSDB would have any role
in the restore then it would be impossible to restore the database on a
different server. All the data that is needed for the point in time
restore is stored in the log backup it self.
Adi|||Hi,
'Full' recovery model set on the msdb?
Ans:- NO NEED
I suspect point-in-time recover will not be possible. Is my assumption
correct?
No. You can do it with out a MSDB tranasction log backup.
--
MSDB database holds the backup history information. FOR each backup SQL
Server logs an entry into BACKUPSET table in MSDB database.
This is just an information only and will be useful if you use Enterprise
manager to do point in time recovery. Even if you
do not have tis information you can do a recovery based on Transaction log
file date and time. For a time based recovery:-
1. Restore the Full database backup first with Norecovery
2. Restore the logbackup file in sequence based on date and time with
Norecovery till last file
3. Restore the last transaction log backup with RECOVERY and STOPAT option.
Note:-
I am taking the MSDB full database backup daily once only.
Thanks
Hari
SQL Server MVP
"James Goodwill" <james.goodwill@.uk.fujitsu.com> wrote in message
news:DmmHe.10993$SO4.8738@.newsfe4-win.ntli.net...
> Hi,
> I have a production SQL 2000 database with transaction logging turned on
> ('Full' recovery mode). I backup the transaction log every 15 minutes. In
> order to use the point-in-time recovery option, do I also need to have the
> 'Full' recovery model set on the msdb? I ask this because I assume the
> msdb
> holds information about the transaction log backup taken on the production
> database. Without this information, I suspect point-in-time recover will
> not
> be possible. Is my assumption correct?
> Regards,
> James G.
>
>

MSDB database

I have under SQL Server 2000 Standard Version with SP3a on Windows 2000 SP4
a Database Maintenance plan to backup transaction logs of all databases
hourly.
This job has been frequently failing, and the reason is that on the MSDB
database, the Recovery option has for some mysterious reason frequently been
reset from FULL to SIMPLE, and in order to get transaction logs backing up,
it needs to be set to FULL.
anyone has any ideas why/what process, etc. would reset the recovery option
from FULL to SIMPLE?> I have under SQL Server 2000 Standard Version with SP3a on Windows 2000
SP4
> a Database Maintenance plan to backup transaction logs of all databases
> hourly.
Backing up the transaction logs from all databases seems like overkill.
What is the point, e.g. for tempdb?

> anyone has any ideas why/what process, etc. would reset the recovery
option
> from FULL to SIMPLE?
This is the way SQL Server works.
http://www.support.microsoft.com/?id=257856
If you really want to back up msdb every hour, then you can make a task in
your job to temporarily set the recovery model to FULL. However this won't
accomplish much as the transaction logs won't be complete (and maybe not
even usable, depending on how you plan to use them).
If you want the behavior to be different, you can let Microsoft know how you
feel: sqlwish@.microsoft.com
Aaron Bertrand
SQL Server MVP|||Aaron Bertrand - MVP wrote:

> option
> This is the way SQL Server works.
> http://www.support.microsoft.com/?id=257856
>
that link is interesting. sort of contradicts the line from BOL "All recove
ry
models are supported for model, msdb and distribution." since full recovery
on
msdb only works until sqlagent is restarted.
i always prefer to have a dbmp for user databases and one for system databas
es.
in the system one, i don't back up transaction logs.
i think it's sort of goofy that the transaction log backup from a dbmp will
try
to backup the logs for db's in simple recovery and then generate errors. i'
ve
written a script that skips simple recovery db's for the log backups, why ca
n't
microsoft implement it in the dbmp jobs?

MSDB database

I have under SQL Server 2000 Standard Version with SP3a on Windows 2000 SP4
a Database Maintenance plan to backup transaction logs of all databases
hourly.
This job has been frequently failing, and the reason is that on the MSDB
database, the Recovery option has for some mysterious reason frequently been
reset from FULL to SIMPLE, and in order to get transaction logs backing up,
it needs to be set to FULL.
anyone has any ideas why/what process, etc. would reset the recovery option
from FULL to SIMPLE?> I have under SQL Server 2000 Standard Version with SP3a on Windows 2000
SP4
> a Database Maintenance plan to backup transaction logs of all databases
> hourly.
Backing up the transaction logs from all databases seems like overkill.
What is the point, e.g. for tempdb?
> anyone has any ideas why/what process, etc. would reset the recovery
option
> from FULL to SIMPLE?
This is the way SQL Server works.
http://www.support.microsoft.com/?id=257856
If you really want to back up msdb every hour, then you can make a task in
your job to temporarily set the recovery model to FULL. However this won't
accomplish much as the transaction logs won't be complete (and maybe not
even usable, depending on how you plan to use them).
If you want the behavior to be different, you can let Microsoft know how you
feel: sqlwish@.microsoft.com
--
Aaron Bertrand
SQL Server MVP|||Aaron Bertrand - MVP wrote:
> > anyone has any ideas why/what process, etc. would reset the recovery
> option
> > from FULL to SIMPLE?
> This is the way SQL Server works.
> http://www.support.microsoft.com/?id=257856
>
that link is interesting. sort of contradicts the line from BOL "All recovery
models are supported for model, msdb and distribution." since full recovery on
msdb only works until sqlagent is restarted.
i always prefer to have a dbmp for user databases and one for system databases.
in the system one, i don't back up transaction logs.
i think it's sort of goofy that the transaction log backup from a dbmp will try
to backup the logs for db's in simple recovery and then generate errors. i've
written a script that skips simple recovery db's for the log backups, why can't
microsoft implement it in the dbmp jobs?