MSDE 2BG limit - for just the data file?

Hi -
I'm looking at an archive strategy for an MSDE database.
In ref to the 2GB "database size" limit: anyone know if
this applies to the log file size + data file size, or
just to the data file size?
I need to figure out the point at which archiving needs
to kick in and trim down an in-production database.
Thanks!
Andy
hi Andy,
Andy wrote:
> Hi -
> I'm looking at an archive strategy for an MSDE database.
> In ref to the 2GB "database size" limit: anyone know if
> this applies to the log file size + data file size, or
> just to the data file size?
> I need to figure out the point at which archiving needs
> to kick in and trim down an in-production database.
> Thanks!
> Andy
the 2gb limit only applies to the sum of data files, including primary
(.Mdf) and all eventual secondary (.Ndf) files...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Great, thanks Andrea!
|||Hi
2Gb for the data file, per database.
You could have more than one database.....
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Andy" <anonymous@.discussions.microsoft.com> wrote in message
news:0dbd01c5092b$ac4a6e90$a601280a@.phx.gbl...
> Hi -
> I'm looking at an archive strategy for an MSDE database.
> In ref to the 2GB "database size" limit: anyone know if
> this applies to the log file size + data file size, or
> just to the data file size?
> I need to figure out the point at which archiving needs
> to kick in and trim down an in-production database.
> Thanks!
> Andy

msde 2000 install failes on xp

Hi
I cant install MSDE 2000 on one XP machine
Cant figure out whats wrong
Because log file too large
Download it here
www.deltmar.ee/logfile.zip
Regards;
Mex
hi Mex,
Meelis Lilbok wrote:
> Hi
> I cant install MSDE 2000 on one XP machine
> Cant figure out whats wrong
> Because log file too large
> Download it here
> www.deltmar.ee/logfile.zip
>
the relevant part of the log is
Setup failed to configure the server. Refer to the server error logs and
setup error logs for more information.
Action ended 14:59:46: InstallFinalize. Return value 3.
usually depending on re-intallation on partially cleaned machines..
please have a look at
http://support.microsoft.com/default...99&Product=sql
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.16.0 - DbaMgr ver 0.61.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

MSDE - Not associated with a trusted SQL Server connection

I have just installed MSDE on my PC running WinXP Pro. I set it up to use
mixed mode for security mode. However, when I try to log in to the database
using a user account I created I get the following error:
Login Failed for user 'username'. Reason: Not associated with a trusted SQL
server connection.
I am using DbaMgr 2k to view the database settings. I have provided all
admin level access to this user. However, I just cannot login using a
username. I have tried using the sa account to login and I get the same
error. I can only login using a Trusted NT Connection option. Any ideas what
I should try? When I searched it on the web, the only suggestion I can see
is to make sure the security mode is set to mixed mode, which seems to be
correct in this case.
Any help will be appreciated.
DeepaliHi
You don't say how you are trying to connect to the server? Try the following
from a command prompt
osql -S <Servername> -U <username> -P <Password>
John
"Deepali Garg" wrote:

> I have just installed MSDE on my PC running WinXP Pro. I set it up to use
> mixed mode for security mode. However, when I try to log in to the databas
e
> using a user account I created I get the following error:
> Login Failed for user 'username'. Reason: Not associated with a trusted SQ
L
> server connection.
> I am using DbaMgr 2k to view the database settings. I have provided all
> admin level access to this user. However, I just cannot login using a
> username. I have tried using the sa account to login and I get the same
> error. I can only login using a Trusted NT Connection option. Any ideas wh
at
> I should try? When I searched it on the web, the only suggestion I can see
> is to make sure the security mode is set to mixed mode, which seems to be
> correct in this case.
> Any help will be appreciated.
> Deepali
>
>|||SQL will not use the changes until it has been re-started... The error
seems to be saying it will only use trusted connections... perhaps you
simply need to re-start SQL...
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
"Deepali Garg" <dgarg@.bigpond.net.au> wrote in message
news:mycTd.173155$K7.61651@.news-server.bigpond.net.au...
>I have just installed MSDE on my PC running WinXP Pro. I set it up to use
> mixed mode for security mode. However, when I try to log in to the
> database
> using a user account I created I get the following error:
> Login Failed for user 'username'. Reason: Not associated with a trusted
> SQL
> server connection.
> I am using DbaMgr 2k to view the database settings. I have provided all
> admin level access to this user. However, I just cannot login using a
> username. I have tried using the sa account to login and I get the same
> error. I can only login using a Trusted NT Connection option. Any ideas
> what
> I should try? When I searched it on the web, the only suggestion I can see
> is to make sure the security mode is set to mixed mode, which seems to be
> correct in this case.
> Any help will be appreciated.
> Deepali
>|||Wayne,
Thanks for your help. This is exactly what the problem was. As soon as I
restarted the SQL Server everything worked ok!
Deepali
"Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message
news:eW1ECQnGFHA.3628@.TK2MSFTNGP15.phx.gbl...
> SQL will not use the changes until it has been re-started... The error
> seems to be saying it will only use trusted connections... perhaps you
> simply need to re-start SQL...
> --
> 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
> "Deepali Garg" <dgarg@.bigpond.net.au> wrote in message
> news:mycTd.173155$K7.61651@.news-server.bigpond.net.au...
see[vbcol=seagreen]
be[vbcol=seagreen]
>

MSDE - Not associated with a trusted SQL Server connection

I have just installed MSDE on my PC running WinXP Pro. I set it up to use
mixed mode for security mode. However, when I try to log in to the database
using a user account I created I get the following error:
Login Failed for user 'username'. Reason: Not associated with a trusted SQL
server connection.
I am using DbaMgr 2k to view the database settings. I have provided all
admin level access to this user. However, I just cannot login using a
username. I have tried using the sa account to login and I get the same
error. I can only login using a Trusted NT Connection option. Any ideas what
I should try? When I searched it on the web, the only suggestion I can see
is to make sure the security mode is set to mixed mode, which seems to be
correct in this case.
Any help will be appreciated.
Deepali
Hi
You don't say how you are trying to connect to the server? Try the following
from a command prompt
osql -S <Servername> -U <username> -P <Password>
John
"Deepali Garg" wrote:

> I have just installed MSDE on my PC running WinXP Pro. I set it up to use
> mixed mode for security mode. However, when I try to log in to the database
> using a user account I created I get the following error:
> Login Failed for user 'username'. Reason: Not associated with a trusted SQL
> server connection.
> I am using DbaMgr 2k to view the database settings. I have provided all
> admin level access to this user. However, I just cannot login using a
> username. I have tried using the sa account to login and I get the same
> error. I can only login using a Trusted NT Connection option. Any ideas what
> I should try? When I searched it on the web, the only suggestion I can see
> is to make sure the security mode is set to mixed mode, which seems to be
> correct in this case.
> Any help will be appreciated.
> Deepali
>
>
|||SQL will not use the changes until it has been re-started... The error
seems to be saying it will only use trusted connections... perhaps you
simply need to re-start SQL...
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
"Deepali Garg" <dgarg@.bigpond.net.au> wrote in message
news:mycTd.173155$K7.61651@.news-server.bigpond.net.au...
>I have just installed MSDE on my PC running WinXP Pro. I set it up to use
> mixed mode for security mode. However, when I try to log in to the
> database
> using a user account I created I get the following error:
> Login Failed for user 'username'. Reason: Not associated with a trusted
> SQL
> server connection.
> I am using DbaMgr 2k to view the database settings. I have provided all
> admin level access to this user. However, I just cannot login using a
> username. I have tried using the sa account to login and I get the same
> error. I can only login using a Trusted NT Connection option. Any ideas
> what
> I should try? When I searched it on the web, the only suggestion I can see
> is to make sure the security mode is set to mixed mode, which seems to be
> correct in this case.
> Any help will be appreciated.
> Deepali
>
|||Wayne,
Thanks for your help. This is exactly what the problem was. As soon as I
restarted the SQL Server everything worked ok!
Deepali
"Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message
news:eW1ECQnGFHA.3628@.TK2MSFTNGP15.phx.gbl...[vbcol=seagreen]
> SQL will not use the changes until it has been re-started... The error
> seems to be saying it will only use trusted connections... perhaps you
> simply need to re-start SQL...
> --
> 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
> "Deepali Garg" <dgarg@.bigpond.net.au> wrote in message
> news:mycTd.173155$K7.61651@.news-server.bigpond.net.au...
see[vbcol=seagreen]
be
>

MSDE - Not associated with a trusted SQL Server connection

I have just installed MSDE on my PC running WinXP Pro. I set it up to use
mixed mode for security mode. However, when I try to log in to the database
using a user account I created I get the following error:
Login Failed for user 'username'. Reason: Not associated with a trusted SQL
server connection.
I am using DbaMgr 2k to view the database settings. I have provided all
admin level access to this user. However, I just cannot login using a
username. I have tried using the sa account to login and I get the same
error. I can only login using a Trusted NT Connection option. Any ideas what
I should try? When I searched it on the web, the only suggestion I can see
is to make sure the security mode is set to mixed mode, which seems to be
correct in this case.
Any help will be appreciated.
DeepaliHi
You don't say how you are trying to connect to the server? Try the following
from a command prompt
osql -S <Servername> -U <username> -P <Password>
John
"Deepali Garg" wrote:
> I have just installed MSDE on my PC running WinXP Pro. I set it up to use
> mixed mode for security mode. However, when I try to log in to the database
> using a user account I created I get the following error:
> Login Failed for user 'username'. Reason: Not associated with a trusted SQL
> server connection.
> I am using DbaMgr 2k to view the database settings. I have provided all
> admin level access to this user. However, I just cannot login using a
> username. I have tried using the sa account to login and I get the same
> error. I can only login using a Trusted NT Connection option. Any ideas what
> I should try? When I searched it on the web, the only suggestion I can see
> is to make sure the security mode is set to mixed mode, which seems to be
> correct in this case.
> Any help will be appreciated.
> Deepali
>
>|||SQL will not use the changes until it has been re-started... The error
seems to be saying it will only use trusted connections... perhaps you
simply need to re-start SQL...
--
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
"Deepali Garg" <dgarg@.bigpond.net.au> wrote in message
news:mycTd.173155$K7.61651@.news-server.bigpond.net.au...
>I have just installed MSDE on my PC running WinXP Pro. I set it up to use
> mixed mode for security mode. However, when I try to log in to the
> database
> using a user account I created I get the following error:
> Login Failed for user 'username'. Reason: Not associated with a trusted
> SQL
> server connection.
> I am using DbaMgr 2k to view the database settings. I have provided all
> admin level access to this user. However, I just cannot login using a
> username. I have tried using the sa account to login and I get the same
> error. I can only login using a Trusted NT Connection option. Any ideas
> what
> I should try? When I searched it on the web, the only suggestion I can see
> is to make sure the security mode is set to mixed mode, which seems to be
> correct in this case.
> Any help will be appreciated.
> Deepali
>|||Wayne,
Thanks for your help. This is exactly what the problem was. As soon as I
restarted the SQL Server everything worked ok!
Deepali
"Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message
news:eW1ECQnGFHA.3628@.TK2MSFTNGP15.phx.gbl...
> SQL will not use the changes until it has been re-started... The error
> seems to be saying it will only use trusted connections... perhaps you
> simply need to re-start SQL...
> --
> 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
> "Deepali Garg" <dgarg@.bigpond.net.au> wrote in message
> news:mycTd.173155$K7.61651@.news-server.bigpond.net.au...
> >I have just installed MSDE on my PC running WinXP Pro. I set it up to use
> > mixed mode for security mode. However, when I try to log in to the
> > database
> > using a user account I created I get the following error:
> >
> > Login Failed for user 'username'. Reason: Not associated with a trusted
> > SQL
> > server connection.
> >
> > I am using DbaMgr 2k to view the database settings. I have provided all
> > admin level access to this user. However, I just cannot login using a
> > username. I have tried using the sa account to login and I get the same
> > error. I can only login using a Trusted NT Connection option. Any ideas
> > what
> > I should try? When I searched it on the web, the only suggestion I can
see
> > is to make sure the security mode is set to mixed mode, which seems to
be
> > correct in this case.
> >
> > Any help will be appreciated.
> >
> > Deepali
> >
> >
>

msdb.dbo.sysdbmaintplan_history table question

Hi,
I am trying to check that a backup integrity check has verified a log
backup because it is being done over a network drive.
There is an entry verify backup for each backup performed in the
msdb.dbo.sysdbmaintplan_history table. Is the verify backup entry the
correct one I should be looking at to see if RESTORE VERIFYONLY
succeeded ?
My question is how do I tell that a verification found an error?
Thanks
--SamMaint plan executed RESTORE VERIFYONLY. It will produce errors of such are found. Make sure you
handle the job so your are notified if errors occurs.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<wildturtle@.gmail.com> wrote in message news:1147179633.997410.37830@.j73g2000cwa.googlegroups.com...
> Hi,
> I am trying to check that a backup integrity check has verified a log
> backup because it is being done over a network drive.
> There is an entry verify backup for each backup performed in the
> msdb.dbo.sysdbmaintplan_history table. Is the verify backup entry the
> correct one I should be looking at to see if RESTORE VERIFYONLY
> succeeded ?
> My question is how do I tell that a verification found an error?
> Thanks
> --Sam
>|||Thanks for your reply. My problem is the following:
the msdb.dbo.sysdbmaintplan_histor=ADy has two records: "Backup
transaction log" and "Verify Backup". They both have fields
called succeeded, error, and message. my question is, if a RESTORE
VERIFYONLY were to detect corruption, how would that be reflected
in the sysdbmaintplan_histor=ADy table ?
Many Thanks
--Sam|||I don't know, I'm afraid. I'd guess that Maint plans are smart enough to mark the execution as
failed and log the errors returned by RESTORE VERIFYONLY. I don't use maint plans myself, as I
prefer more control over these things. Perhaps you can try, for instance doing the backup to the
"nul" file name?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<wildturtle@.gmail.com> wrote in message
news:1147180762.992024.182010@.u72g2000cwu.googlegroups.com...
Thanks for your reply. My problem is the following:
the msdb.dbo.sysdbmaintplan_histor­y has two records: "Backup
transaction log" and "Verify Backup". They both have fields
called succeeded, error, and message. my question is, if a RESTORE
VERIFYONLY were to detect corruption, how would that be reflected
in the sysdbmaintplan_histor­y table ?
Many Thanks
--Sam

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 restore

Hello --
Using SQL 2000. When performing a trans log restore to our backup SQL box
the server locked up. After I got the server restarted the msdb was marked
'suspect'. I don't have a backup of the msdb. I can still perform
restores, but I get error message about the msdb. Do I need to re-install
SQL on this box? I'm not sure what to do (besides doing msdb backups from
now on). Any help would be appreciated. Thank you.
Hi,
No need to install SQL Server.
Start SQL Server with Trace 3608 from command prompt
SQLSERVER -T3608 -m
Drop or detach the MSDB database and rebuild the MSDB using the installation
script(INSTMSDB.SQL) in the SLQ Server install folder. But after this
you need to create all your sql agent jobs manually. Please ensure that you
do a backup of MSDB database hereafter
One more solution-
Start SQL Server with Trace 3608 from command prompt
SQLSERVER -T3608 -m
From query analyzer Detach MSDB database, copy the files from the CD (in
x86\Data) and then attach this files.
Thanks
Hari
SQL Server MVP
"FRR" <FRR@.discussions.microsoft.com> wrote in message
news:51EACBD9-BB21-4FB6-9C2F-2A5C5B74D083@.microsoft.com...
> Hello --
> Using SQL 2000. When performing a trans log restore to our backup SQL box
> the server locked up. After I got the server restarted the msdb was
> marked
> 'suspect'. I don't have a backup of the msdb. I can still perform
> restores, but I get error message about the msdb. Do I need to re-install
> SQL on this box? I'm not sure what to do (besides doing msdb backups from
> now on). Any help would be appreciated. Thank you.

msdb restore

Hello --
Using SQL 2000. When performing a trans log restore to our backup SQL box
the server locked up. After I got the server restarted the msdb was marked
'suspect'. I don't have a backup of the msdb. I can still perform
restores, but I get error message about the msdb. Do I need to re-install
SQL on this box? I'm not sure what to do (besides doing msdb backups from
now on). Any help would be appreciated. Thank you.Hi,
No need to install SQL Server.
Start SQL Server with Trace 3608 from command prompt
SQLSERVER -T3608 -m
Drop or detach the MSDB database and rebuild the MSDB using the installation
script(INSTMSDB.SQL) in the SLQ Server install folder. But after this
you need to create all your sql agent jobs manually. Please ensure that you
do a backup of MSDB database hereafter :)
One more solution-
Start SQL Server with Trace 3608 from command prompt
SQLSERVER -T3608 -m
From query analyzer Detach MSDB database, copy the files from the CD (in
x86\Data) and then attach this files.
Thanks
Hari
SQL Server MVP
"FRR" <FRR@.discussions.microsoft.com> wrote in message
news:51EACBD9-BB21-4FB6-9C2F-2A5C5B74D083@.microsoft.com...
> Hello --
> Using SQL 2000. When performing a trans log restore to our backup SQL box
> the server locked up. After I got the server restarted the msdb was
> marked
> 'suspect'. I don't have a backup of the msdb. I can still perform
> restores, but I get error message about the msdb. Do I need to re-install
> SQL on this box? I'm not sure what to do (besides doing msdb backups from
> now on). Any help would be appreciated. Thank you.

msdb restore

Hello --
Using SQL 2000. When performing a trans log restore to our backup SQL box
the server locked up. After I got the server restarted the msdb was marked
'suspect'. I don't have a backup of the msdb. I can still perform
restores, but I get error message about the msdb. Do I need to re-install
SQL on this box? I'm not sure what to do (besides doing msdb backups from
now on). Any help would be appreciated. Thank you.Hi,
No need to install SQL Server.
Start SQL Server with Trace 3608 from command prompt
SQLSERVER -T3608 -m
Drop or detach the MSDB database and rebuild the MSDB using the installation
script(INSTMSDB.SQL) in the SLQ Server install folder. But after this
you need to create all your sql agent jobs manually. Please ensure that you
do a backup of MSDB database hereafter
One more solution-
Start SQL Server with Trace 3608 from command prompt
SQLSERVER -T3608 -m
From query analyzer Detach MSDB database, copy the files from the CD (in
x86\Data) and then attach this files.
Thanks
Hari
SQL Server MVP
"FRR" <FRR@.discussions.microsoft.com> wrote in message
news:51EACBD9-BB21-4FB6-9C2F-2A5C5B74D083@.microsoft.com...
> Hello --
> Using SQL 2000. When performing a trans log restore to our backup SQL box
> the server locked up. After I got the server restarted the msdb was
> marked
> 'suspect'. I don't have a backup of the msdb. I can still perform
> restores, but I get error message about the msdb. Do I need to re-install
> SQL on this box? I'm not sure what to do (besides doing msdb backups from
> now on). Any help would be appreciated. Thank you.

msdb or file system

When I log into Integrated Services on my SQL server, I see [Stored Package] -- File System and MSDB.

When I deploy/import my SSIS packages which should it go under? Is there a difference and if so what the difference?

thanks

HAHAHA! You asked the exact same question as someone else and within something like two hours.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2008865&SiteID=1

Since that question is unanswered, here's the deal.

Where you ultimately choose to store your packages, is up to you. They each do the same thing, but with some differences.

With File System storage, you can simply map a network drive to the server and just copy your packages over to the server. With SQL Server, you need to import into MSDB.

Some like to use File System, but to me, the permissions are harder to work with. Because SSIS does not save passwords, you'll have to use a configuration file to specify passwords for your connection managers. Either that, or you'll have to use EncryptSensitiveWithPassword and then specify a decryption password with the command line.

SQL Server has the same problems unless you tell it to use "SQL Server Roles and Storage" when importing. This is what I choose to use. Access is controlled via SQL Server roles/security.

Search this forum for other ideas regarding file system versus MSDB.|||

LOL

thanks, I'm not a big fan of using the file system for much and due to the permissions within the tool then going through the act of congress to get permissions setup on a network drive to use, isn't worth the hassle.

It would take me longer to get that setup (just from the network side) then it would for me to create a package, test it, import it and roll it out to production and create 10 more.

So I think I'll go the MSDB route.

|||More information:

http://blogs.conchango.com/jamiethomson/archive/2006/02/20/SSIS_3A00_-Deploy-to-file-system-or-SQL-Server.aspx

http://www.sqljunkies.com/WebLog/knight_reign/archive/2005/05/05/13523.aspx|||

thanks, I was just reading the sqljunkies.com one actually.

So far I'm not finding a clear cut answer, I guess it really depends on the person deploying the packages.

its kind of like, what language is better C# or VB.NET? no clear answer, its developer preference.

thanks again

msdb log backup failed

Hello guys,
I am sorry if I insist but I am still having this error about msdb log
file failed.
BACKUP failed to complete the command BACKUP LOG [msdb] TO [systemLo
g]
WITH NOINIT , NOUNLOAD , NAME = N'msdb backup', NOSKIP , STATS =
10, NOFORMAT
I do not understand why.
Could someone help me on solve this problem.
InaHi,
Can you verify the recovery model of MSDB database by executing below
command:-
select databasepropertyex('msdb','recovery')
If the result return SIMPLE then you can not perform a transaction log
backup. Incase if you need to do a log backup then change the recovery
model to FULL using below command
ALTER DATABASE MSDB SET RECOVERY FULL
After to regroup the backup chain; perform a FULL MSDB backup and then then
start the log backup.,
Thanks
Hari
"ina" <roberta.inalbon@.gmail.com> wrote in message
news:1159778124.630986.307670@.h48g2000cwc.googlegroups.com...
> Hello guys,
> I am sorry if I insist but I am still having this error about msdb log
> file failed.
> BACKUP failed to complete the command BACKUP LOG [msdb] TO [system
Log]
> WITH NOINIT , NOUNLOAD , NAME = N'msdb backup', NOSKIP , STATS =
> 10, NOFORMAT
>
> I do not understand why.
> Could someone help me on solve this problem.
> Ina
>|||Thanks Hari,
It was set to simple. I changed as you advice me. One question when I
schedule the schedule log backup do you thing i can do something
between 4 Am until 10 Pm (every hour) because the backup of MSDB is 23
PM ?
ina
Hari Prasad wrote:[vbcol=seagreen]
> Hi,
> Can you verify the recovery model of MSDB database by executing below
> command:-
> select databasepropertyex('msdb','recovery')
> If the result return SIMPLE then you can not perform a transaction log
> backup. Incase if you need to do a log backup then change the recovery
> model to FULL using below command
> ALTER DATABASE MSDB SET RECOVERY FULL
> After to regroup the backup chain; perform a FULL MSDB backup and then the
n
> start the log backup.,
> Thanks
> Hari
>
> "ina" <roberta.inalbon@.gmail.com> wrote in message
> news:1159778124.630986.307670@.h48g2000cwc.googlegroups.com...

msdb log backup failed

Hello guys,
I am sorry if I insist but I am still having this error about msdb log
file failed.
BACKUP failed to complete the command BACKUP LOG [msdb] TO [systemLog]
WITH NOINIT , NOUNLOAD , NAME = N'msdb backup', NOSKIP , STATS =
10, NOFORMAT
I do not understand why.
Could someone help me on solve this problem.
Ina
Hi,
Can you verify the recovery model of MSDB database by executing below
command:-
select databasepropertyex('msdb','recovery')
If the result return SIMPLE then you can not perform a transaction log
backup. Incase if you need to do a log backup then change the recovery
model to FULL using below command
ALTER DATABASE MSDB SET RECOVERY FULL
After to regroup the backup chain; perform a FULL MSDB backup and then then
start the log backup.,
Thanks
Hari
"ina" <roberta.inalbon@.gmail.com> wrote in message
news:1159778124.630986.307670@.h48g2000cwc.googlegr oups.com...
> Hello guys,
> I am sorry if I insist but I am still having this error about msdb log
> file failed.
> BACKUP failed to complete the command BACKUP LOG [msdb] TO [systemLog]
> WITH NOINIT , NOUNLOAD , NAME = N'msdb backup', NOSKIP , STATS =
> 10, NOFORMAT
>
> I do not understand why.
> Could someone help me on solve this problem.
> Ina
>
|||Thanks Hari,
It was set to simple. I changed as you advice me. One question when I
schedule the schedule log backup do you thing i can do something
between 4 Am until 10 Pm (every hour) because the backup of MSDB is 23
PM ?
ina
Hari Prasad wrote:[vbcol=seagreen]
> Hi,
> Can you verify the recovery model of MSDB database by executing below
> command:-
> select databasepropertyex('msdb','recovery')
> If the result return SIMPLE then you can not perform a transaction log
> backup. Incase if you need to do a log backup then change the recovery
> model to FULL using below command
> ALTER DATABASE MSDB SET RECOVERY FULL
> After to regroup the backup chain; perform a FULL MSDB backup and then then
> start the log backup.,
> Thanks
> Hari
>
> "ina" <roberta.inalbon@.gmail.com> wrote in message
> news:1159778124.630986.307670@.h48g2000cwc.googlegr oups.com...

msdb log backup failed

Hello guys,
I am sorry if I insist but I am still having this error about msdb log
file failed.
BACKUP failed to complete the command BACKUP LOG [msdb] TO [systemLog]
WITH NOINIT , NOUNLOAD , NAME = N'msdb backup', NOSKIP , STATS = 10, NOFORMAT
I do not understand why.
Could someone help me on solve this problem.
InaHi,
Can you verify the recovery model of MSDB database by executing below
command:-
select databasepropertyex('msdb','recovery')
If the result return SIMPLE then you can not perform a transaction log
backup. Incase if you need to do a log backup then change the recovery
model to FULL using below command
ALTER DATABASE MSDB SET RECOVERY FULL
After to regroup the backup chain; perform a FULL MSDB backup and then then
start the log backup.,
Thanks
Hari
"ina" <roberta.inalbon@.gmail.com> wrote in message
news:1159778124.630986.307670@.h48g2000cwc.googlegroups.com...
> Hello guys,
> I am sorry if I insist but I am still having this error about msdb log
> file failed.
> BACKUP failed to complete the command BACKUP LOG [msdb] TO [systemLog]
> WITH NOINIT , NOUNLOAD , NAME = N'msdb backup', NOSKIP , STATS => 10, NOFORMAT
>
> I do not understand why.
> Could someone help me on solve this problem.
> Ina
>|||Thanks Hari,
It was set to simple. I changed as you advice me. One question when I
schedule the schedule log backup do you thing i can do something
between 4 Am until 10 Pm (every hour) because the backup of MSDB is 23
PM ?
ina
Hari Prasad wrote:
> Hi,
> Can you verify the recovery model of MSDB database by executing below
> command:-
> select databasepropertyex('msdb','recovery')
> If the result return SIMPLE then you can not perform a transaction log
> backup. Incase if you need to do a log backup then change the recovery
> model to FULL using below command
> ALTER DATABASE MSDB SET RECOVERY FULL
> After to regroup the backup chain; perform a FULL MSDB backup and then then
> start the log backup.,
> Thanks
> Hari
>
> "ina" <roberta.inalbon@.gmail.com> wrote in message
> news:1159778124.630986.307670@.h48g2000cwc.googlegroups.com...
> > Hello guys,
> >
> > I am sorry if I insist but I am still having this error about msdb log
> > file failed.
> >
> > BACKUP failed to complete the command BACKUP LOG [msdb] TO [systemLog]
> > WITH NOINIT , NOUNLOAD , NAME = N'msdb backup', NOSKIP , STATS => > 10, NOFORMAT
> >
> >
> > I do not understand why.
> >
> > Could someone help me on solve this problem.
> >
> > Ina
> >

msdb database size

My SQL Server 2005 SP2 msdb database is 230 GB. I tried shrinking it several
times and nothing changes. The log file is 1 mb. How can I tell what is
using up this space?USE msdb;
GO
SELECT TOP 10 OBJECT_NAME(id), *
FROM sys.sysindexes
WHERE indid IN (0,1)
ORDER BY used DESC;
--or
SELECT TOP 10 OBJECT_NAME([object_id]), *
FROM sys.dm_db_partition_stats
WHERE index_id IN (0,1)
ORDER BY in_row_reserved_page_count DESC;
"SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
news:771E4963-D5B2-4CEB-9209-00FF3B5F75A4@.microsoft.com...
> My SQL Server 2005 SP2 msdb database is 230 GB. I tried shrinking it
> several
> times and nothing changes. The log file is 1 mb. How can I tell what is
> using up this space?|||Aaron,
Thank you. I ran the second query and got an object with this name:
queue_messages_391672443
I cannot find this object in the tables...
"Aaron Bertrand [SQL Server MVP]" wrote:
> USE msdb;
> GO
> SELECT TOP 10 OBJECT_NAME(id), *
> FROM sys.sysindexes
> WHERE indid IN (0,1)
> ORDER BY used DESC;
> --or
> SELECT TOP 10 OBJECT_NAME([object_id]), *
> FROM sys.dm_db_partition_stats
> WHERE index_id IN (0,1)
> ORDER BY in_row_reserved_page_count DESC;
>
> "SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
> news:771E4963-D5B2-4CEB-9209-00FF3B5F75A4@.microsoft.com...
> > My SQL Server 2005 SP2 msdb database is 230 GB. I tried shrinking it
> > several
> > times and nothing changes. The log file is 1 mb. How can I tell what is
> > using up this space?
>
>|||Probably marked as a system table. This will generate a query that will
show you 10 sample rows from the table.
SELECT 'SELECT TOP 10 * FROM '
+ OBJECT_SCHEMA_NAME(object_id)
+ '.[' + name + ']'
FROM sys.all_objects
WHERE name = 'queue_messages_391672443';
Is it possible you are using service broker or event/query notifications and
messages are being placed on the queue but not sent out?
"SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
news:6F5B5B70-F929-4D5D-8A28-34E3BF84D098@.microsoft.com...
> Aaron,
> Thank you. I ran the second query and got an object with this name:
> queue_messages_391672443
> I cannot find this object in the tables...
> "Aaron Bertrand [SQL Server MVP]" wrote:
>> USE msdb;
>> GO
>> SELECT TOP 10 OBJECT_NAME(id), *
>> FROM sys.sysindexes
>> WHERE indid IN (0,1)
>> ORDER BY used DESC;
>> --or
>> SELECT TOP 10 OBJECT_NAME([object_id]), *
>> FROM sys.dm_db_partition_stats
>> WHERE index_id IN (0,1)
>> ORDER BY in_row_reserved_page_count DESC;
>>
>> "SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
>> news:771E4963-D5B2-4CEB-9209-00FF3B5F75A4@.microsoft.com...
>> > My SQL Server 2005 SP2 msdb database is 230 GB. I tried shrinking it
>> > several
>> > times and nothing changes. The log file is 1 mb. How can I tell what
>> > is
>> > using up this space?
>>|||I cannot find this table. The script returned a SQL statement with table
name that does not exist. We're not using service broker. What can we do to
stop the message and clear up them up?
"Aaron Bertrand [SQL Server MVP]" wrote:
> Probably marked as a system table. This will generate a query that will
> show you 10 sample rows from the table.
>
> SELECT 'SELECT TOP 10 * FROM '
> + OBJECT_SCHEMA_NAME(object_id)
> + '.[' + name + ']'
> FROM sys.all_objects
> WHERE name = 'queue_messages_391672443';
>
> Is it possible you are using service broker or event/query notifications and
> messages are being placed on the queue but not sent out?
>
>
>
> "SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
> news:6F5B5B70-F929-4D5D-8A28-34E3BF84D098@.microsoft.com...
> > Aaron,
> > Thank you. I ran the second query and got an object with this name:
> > queue_messages_391672443
> >
> > I cannot find this object in the tables...
> >
> > "Aaron Bertrand [SQL Server MVP]" wrote:
> >
> >> USE msdb;
> >> GO
> >>
> >> SELECT TOP 10 OBJECT_NAME(id), *
> >> FROM sys.sysindexes
> >> WHERE indid IN (0,1)
> >> ORDER BY used DESC;
> >>
> >> --or
> >>
> >> SELECT TOP 10 OBJECT_NAME([object_id]), *
> >> FROM sys.dm_db_partition_stats
> >> WHERE index_id IN (0,1)
> >> ORDER BY in_row_reserved_page_count DESC;
> >>
> >>
> >>
> >> "SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
> >> news:771E4963-D5B2-4CEB-9209-00FF3B5F75A4@.microsoft.com...
> >> > My SQL Server 2005 SP2 msdb database is 230 GB. I tried shrinking it
> >> > several
> >> > times and nothing changes. The log file is 1 mb. How can I tell what
> >> > is
> >> > using up this space?
> >>
> >>
> >>
>
>|||>I cannot find this table. The script returned a SQL statement with table
> name that does not exist. We're not using service broker. What can we do
> to
> stop the message and clear up them up?
Well if you "can't find the table" it's going to be hard for any of us to
suggest a way to "clear up" anything... maybe you should turn on Profiler
and watch for any T-SQL events that involve an object name like that... then
that might point you to some application you have running that is doing this
to you.
A|||Aaron,
Thank you for your assistance. I seem to be getting nowhere in getting to
the bottom of what is causing this. I don't know how Service Broker works
and whether it is responsible.
I'm running Profiler now and I am not getting anything. How do I view the
sys tables?
"Aaron Bertrand [SQL Server MVP]" wrote:
> >I cannot find this table. The script returned a SQL statement with table
> > name that does not exist. We're not using service broker. What can we do
> > to
> > stop the message and clear up them up?
> Well if you "can't find the table" it's going to be hard for any of us to
> suggest a way to "clear up" anything... maybe you should turn on Profiler
> and watch for any T-SQL events that involve an object name like that... then
> that might point you to some application you have running that is doing this
> to you.
> A
>
>|||> I'm running Profiler now and I am not getting anything. How do I view the
> sys tables?
There are tons of sys tables. Can you be more specific? What *EXACTLY* did
the query I sent earlier return? And what happened when you ran the output?
SELECT 'SELECT TOP 10 * FROM '
+ OBJECT_SCHEMA_NAME(object_id)
+ '.[' + name + ']'
FROM sys.all_objects
WHERE name = 'queue_messages_391672443';|||It generates this sql statement as output:
SELECT TOP 10 * FROM sys.[queue_messages_391672443]
"Aaron Bertrand [SQL Server MVP]" wrote:
> > I'm running Profiler now and I am not getting anything. How do I view the
> > sys tables?
> There are tons of sys tables. Can you be more specific? What *EXACTLY* did
> the query I sent earlier return? And what happened when you ran the output?
> SELECT 'SELECT TOP 10 * FROM '
> + OBJECT_SCHEMA_NAME(object_id)
> + '.[' + name + ']'
> FROM sys.all_objects
> WHERE name = 'queue_messages_391672443';
>
>|||And I'll ask again, what happens when you run *THAT* query?
"SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
news:EFEE4A62-F1A4-4171-81CC-D804033AD2E3@.microsoft.com...
> It generates this sql statement as output:
> SELECT TOP 10 * FROM sys.[queue_messages_391672443]|||Thanks Aaron,
I get an error:
Msg 208, Level 16, State 1, Line 1
Invalid object name 'sys.queue_messages_391672443'.
"Aaron Bertrand [SQL Server MVP]" wrote:
> And I'll ask again, what happens when you run *THAT* query?
>
> "SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
> news:EFEE4A62-F1A4-4171-81CC-D804033AD2E3@.microsoft.com...
> > It generates this sql statement as output:
> > SELECT TOP 10 * FROM sys.[queue_messages_391672443]
>
>|||I don't know, gremlins? Can you try running that query as sa or another
sysadmin? Maybe you can't select from it because you don't have privileges.
"SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
news:9FAB03FA-9A5D-455B-BC15-DDB1A7036A73@.microsoft.com...
> Thanks Aaron,
> I get an error:
> Msg 208, Level 16, State 1, Line 1
> Invalid object name 'sys.queue_messages_391672443'.
>
> "Aaron Bertrand [SQL Server MVP]" wrote:
>> And I'll ask again, what happens when you run *THAT* query?
>>
>> "SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
>> news:EFEE4A62-F1A4-4171-81CC-D804033AD2E3@.microsoft.com...
>> > It generates this sql statement as output:
>> > SELECT TOP 10 * FROM sys.[queue_messages_391672443]
>>|||With the help from Micrsoft, the culprit turned out to be a login
notification service that had gotten turned on (still a mysterie). The
service broker type service usese an internal table called LoginQueue that
was expanding by leaps and bound as result of login events. Since there was
no place for the notifications to be sent or received, the queue continued to
grow. We had to write a program to "receive messages" for 86 million
messages. Once the program received all the message we could then delete the
service and the associated internal table. Shrinking the database reclaimed
all the space.
Aaron, I really apreciate your involvement. Becaue of your query, we're
able to get Microsoft focused on how to identify the source and deal with it.
"Aaron Bertrand [SQL Server MVP]" wrote:
> I don't know, gremlins? Can you try running that query as sa or another
> sysadmin? Maybe you can't select from it because you don't have privileges.
>
> "SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
> news:9FAB03FA-9A5D-455B-BC15-DDB1A7036A73@.microsoft.com...
> > Thanks Aaron,
> > I get an error:
> > Msg 208, Level 16, State 1, Line 1
> > Invalid object name 'sys.queue_messages_391672443'.
> >
> >
> > "Aaron Bertrand [SQL Server MVP]" wrote:
> >
> >> And I'll ask again, what happens when you run *THAT* query?
> >>
> >>
> >>
> >> "SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
> >> news:EFEE4A62-F1A4-4171-81CC-D804033AD2E3@.microsoft.com...
> >> > It generates this sql statement as output:
> >> > SELECT TOP 10 * FROM sys.[queue_messages_391672443]
> >>
> >>
> >>
>
>

MSDB and MASTER DB

Im using MS SQL2000 and have and replication scheme with log
shipping. Is posible replicate by log shipping or transactional
replication schemes this DBs
Thanks
I'm not sure what the question is really here - the subject seems so
different to the body text
If you want to know the pros and cons of transactional replication vs log
shipping, please see this article:
http://www.replicationanswers.com/Standby.asp
If you are looking to set up a combination of log shipping and replication,
then please tell us a little more...
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
|||Both system db's are in simple mode. Microsoft recommends backing the msdb
database up and shipping it. While it is possible to restore a master
database to another server, Microsoft recommends you transfer objects to the
standby server.
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
<gnp1977@.gmail.com> wrote in message
news:1173280868.971366.142840@.c51g2000cwc.googlegr oups.com...
Im using MS SQL2000 and have and replication scheme with log
shipping. Is posible replicate by log shipping or transactional
replication schemes this DBs
Thanks
|||Hi, thanks for the answer, I need transfer the content of two DB to a
standby server...One of this have 35mb and the other have 13GB.
What method is the better? Transactional or Log Shipping?
And other thing, de DBs MASTER and MSDB can be replicated to the
stand by server, I need this because is a Continuity of Bussines site.
Thanks
|||For these volumes I would use transactional replication if possible. For the
master and msdb databases, what sort of objects are you moving?
In master your linked servers and logins live. Do these change much? There
is a SQL DTS/SSIS job which will transfer the logins. Your msdb databsae
will contain DTS packages and jobs. These can be scripted/exported and sent
to the standby server.
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
<gnp1977@.gmail.com> wrote in message
news:1173296916.452161.294790@.n33g2000cwc.googlegr oups.com...
Hi, thanks for the answer, I need transfer the content of two DB to a
standby server...One of this have 35mb and the other have 13GB.
What method is the better? Transactional or Log Shipping?
And other thing, de DBs MASTER and MSDB can be replicated to the
stand by server, I need this because is a Continuity of Bussines site.
Thanks

msdb and log shipping question

Hi,
We have set up an log shipping for DatabaseA between Server1 and Server2.
Now that log shipping was canceled and the DatabaseA in Server2 was also
deleted.
Is there any info still kept in the Server2 regarding to the log shipping
and DatabaseA?
I built a new log shipping plan but it was no good cause the transaction
didn't copy to the Server2, while other log shipping for other databases
were OK.
Thanks for help.
JasonHi Jason
Have you looked at http://msdn2.microsoft.com/en-us/library/ms187045.aspx
John
"Jason Huang" wrote:

> Hi,
> We have set up an log shipping for DatabaseA between Server1 and Server2.
> Now that log shipping was canceled and the DatabaseA in Server2 was also
> deleted.
> Is there any info still kept in the Server2 regarding to the log shipping
> and DatabaseA?
> I built a new log shipping plan but it was no good cause the transaction
> didn't copy to the Server2, while other log shipping for other databases
> were OK.
> Thanks for help.
>
> Jason
>
>|||If you did not remove the Log Shipping according to the procedure then the
jobs of old Log Shipping must be left in the Jobs node under SQL Server
Agent. You better purge them.
After deletion of the DatabaseA from the Server2, did you restore a copy of
the DatabaseA on the Server1 on Server2 in a STANDBY or NORECOVERY recovery
state?
You can check the history of the jobs that are created for the new Log
Shipping to find the exact error. There are three jobs created for Log
Shipping. One of them is for backing up the transaction log on the primary
server and the second is to copy it to some place and the last one is to
restore that copied transaction log file to the secondary server. Check
their job histories accordingly to find a track of the error.
Ekrem nsoy
"Jason Huang" <JasonHuang8888@.hotmail.com> wrote in message
news:OhOaSWbTIHA.4272@.TK2MSFTNGP06.phx.gbl...
> Hi,
> We have set up an log shipping for DatabaseA between Server1 and Server2.
> Now that log shipping was canceled and the DatabaseA in Server2 was also
> deleted.
> Is there any info still kept in the Server2 regarding to the log shipping
> and DatabaseA?
> I built a new log shipping plan but it was no good cause the transaction
> didn't copy to the Server2, while other log shipping for other databases
> were OK.
> Thanks for help.
>
> Jason
>

msdb and log shipping question

Hi,
We have set up an log shipping for DatabaseA between Server1 and Server2.
Now that log shipping was canceled and the DatabaseA in Server2 was also
deleted.
Is there any info still kept in the Server2 regarding to the log shipping
and DatabaseA?
I built a new log shipping plan but it was no good cause the transaction
didn't copy to the Server2, while other log shipping for other databases
were OK.
Thanks for help.
Jason
Hi Jason
Have you looked at http://msdn2.microsoft.com/en-us/library/ms187045.aspx
John
"Jason Huang" wrote:

> Hi,
> We have set up an log shipping for DatabaseA between Server1 and Server2.
> Now that log shipping was canceled and the DatabaseA in Server2 was also
> deleted.
> Is there any info still kept in the Server2 regarding to the log shipping
> and DatabaseA?
> I built a new log shipping plan but it was no good cause the transaction
> didn't copy to the Server2, while other log shipping for other databases
> were OK.
> Thanks for help.
>
> Jason
>
>
|||If you did not remove the Log Shipping according to the procedure then the
jobs of old Log Shipping must be left in the Jobs node under SQL Server
Agent. You better purge them.
After deletion of the DatabaseA from the Server2, did you restore a copy of
the DatabaseA on the Server1 on Server2 in a STANDBY or NORECOVERY recovery
state?
You can check the history of the jobs that are created for the new Log
Shipping to find the exact error. There are three jobs created for Log
Shipping. One of them is for backing up the transaction log on the primary
server and the second is to copy it to some place and the last one is to
restore that copied transaction log file to the secondary server. Check
their job histories accordingly to find a track of the error.
Ekrem nsoy
"Jason Huang" <JasonHuang8888@.hotmail.com> wrote in message
news:OhOaSWbTIHA.4272@.TK2MSFTNGP06.phx.gbl...
> Hi,
> We have set up an log shipping for DatabaseA between Server1 and Server2.
> Now that log shipping was canceled and the DatabaseA in Server2 was also
> deleted.
> Is there any info still kept in the Server2 regarding to the log shipping
> and DatabaseA?
> I built a new log shipping plan but it was no good cause the transaction
> didn't copy to the Server2, while other log shipping for other databases
> were OK.
> Thanks for help.
>
> Jason
>