Showing posts with label apply. Show all posts
Showing posts with label apply. Show all posts

Friday, March 23, 2012

Newbie question

Hi,
Can one Full-Text Catalog apply to more than one tables?
e.g. I need Full-Text Catalog in Northwind that needs to apply to
Customers and Categories table, should I create one Catalog for two tables or
one catelog for each table?
what is the difference?
Thanks a lot
Ed
Hi Ed,
Yes, a FT Catalog can have more than one table in it, but the reverse (one
table in more than one FT Catalog) is not true.
For the Northwind example, you can do either, but for a better explanation
on the issues see, the last paragraph in the SQL Server 2000 BOL title
"Full-text Search Recommendations".
Regards,
John
"Ed" <Ed@.discussions.microsoft.com> wrote in message
news:FA3CB9AB-2B76-498C-A9EC-15B76D2F578A@.microsoft.com...
> Hi,
> Can one Full-Text Catalog apply to more than one tables?
> e.g. I need Full-Text Catalog in Northwind that needs to apply to
> Customers and Categories table, should I create one Catalog for two tables
or
> one catelog for each table?
> what is the difference?
> Thanks a lot
> Ed

Wednesday, March 7, 2012

newbie : backup set begins at LSN xxx, ... too late to apply ...

<< The log in this backup set begins at LSN xxx, which is too late to apply
to the database. An earlier log backup that includes LSN yyy can be
restored >>
ok forgive my ignrance here, using the maintenance plan wizards i have
backups in place that fire full db back up every 4 hours or so and back up
the transaction logs every hour.
i have set it up 2 different maint plans - one writes to the server's hard
diskl; the other writes to a network share using UNC path.
full restore from either location works ok; but when trying to do
transaction log restores i get the error message above. i think its
because:
the 2 transaction log backups are firing at the same time and writing to
different locations, so i would have to bounce back and forth between the 2
locations to get the transaction logs restored in proper order, correct?
obviously i should change this, so suggestions would be welcome.
thx
Use only one maintenance plan to either the local HD or the remote share.
HTH
Jerry
"jimbo-black" <passwords.20.jimbo-black@.antichef.net> wrote in message
news:Xns96EFDE4BBEF04jimboblac@.207.115.63.158...
> << The log in this backup set begins at LSN xxx, which is too late to
> apply
> to the database. An earlier log backup that includes LSN yyy can be
> restored >>
> ok forgive my ignrance here, using the maintenance plan wizards i have
> backups in place that fire full db back up every 4 hours or so and back up
> the transaction logs every hour.
> i have set it up 2 different maint plans - one writes to the server's hard
> diskl; the other writes to a network share using UNC path.
> full restore from either location works ok; but when trying to do
> transaction log restores i get the error message above. i think its
> because:
> the 2 transaction log backups are firing at the same time and writing to
> different locations, so i would have to bounce back and forth between the
> 2
> locations to get the transaction logs restored in proper order, correct?
> obviously i should change this, so suggestions would be welcome.
> thx
|||...and optionally copy the backup files to the other location after each backup has been performed.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
news:uFz2fQU0FHA.2652@.TK2MSFTNGP14.phx.gbl...
> Use only one maintenance plan to either the local HD or the remote share.
> HTH
> Jerry
> "jimbo-black" <passwords.20.jimbo-black@.antichef.net> wrote in message
> news:Xns96EFDE4BBEF04jimboblac@.207.115.63.158...
>

newbie : backup set begins at LSN xxx, ... too late to apply ...

<< The log in this backup set begins at LSN xxx, which is too late to apply
to the database. An earlier log backup that includes LSN yyy can be
restored >>
ok forgive my ignrance here, using the maintenance plan wizards i have
backups in place that fire full db back up every 4 hours or so and back up
the transaction logs every hour.
i have set it up 2 different maint plans - one writes to the server's hard
diskl; the other writes to a network share using UNC path.
full restore from either location works ok; but when trying to do
transaction log restores i get the error message above. i think its
because:
the 2 transaction log backups are firing at the same time and writing to
different locations, so i would have to bounce back and forth between the 2
locations to get the transaction logs restored in proper order, correct?
obviously i should change this, so suggestions would be welcome.
thxUse only one maintenance plan to either the local HD or the remote share.
HTH
Jerry
"jimbo-black" <passwords.20.jimbo-black@.antichef.net> wrote in message
news:Xns96EFDE4BBEF04jimboblac@.207.115.63.158...
> << The log in this backup set begins at LSN xxx, which is too late to
> apply
> to the database. An earlier log backup that includes LSN yyy can be
> restored >>
> ok forgive my ignrance here, using the maintenance plan wizards i have
> backups in place that fire full db back up every 4 hours or so and back up
> the transaction logs every hour.
> i have set it up 2 different maint plans - one writes to the server's hard
> diskl; the other writes to a network share using UNC path.
> full restore from either location works ok; but when trying to do
> transaction log restores i get the error message above. i think its
> because:
> the 2 transaction log backups are firing at the same time and writing to
> different locations, so i would have to bounce back and forth between the
> 2
> locations to get the transaction logs restored in proper order, correct?
> obviously i should change this, so suggestions would be welcome.
> thx|||...and optionally copy the backup files to the other location after each backup has been performed.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
news:uFz2fQU0FHA.2652@.TK2MSFTNGP14.phx.gbl...
> Use only one maintenance plan to either the local HD or the remote share.
> HTH
> Jerry
> "jimbo-black" <passwords.20.jimbo-black@.antichef.net> wrote in message
> news:Xns96EFDE4BBEF04jimboblac@.207.115.63.158...
>> << The log in this backup set begins at LSN xxx, which is too late to apply
>> to the database. An earlier log backup that includes LSN yyy can be
>> restored >>
>> ok forgive my ignrance here, using the maintenance plan wizards i have
>> backups in place that fire full db back up every 4 hours or so and back up
>> the transaction logs every hour.
>> i have set it up 2 different maint plans - one writes to the server's hard
>> diskl; the other writes to a network share using UNC path.
>> full restore from either location works ok; but when trying to do
>> transaction log restores i get the error message above. i think its
>> because:
>> the 2 transaction log backups are firing at the same time and writing to
>> different locations, so i would have to bounce back and forth between the 2
>> locations to get the transaction logs restored in proper order, correct?
>> obviously i should change this, so suggestions would be welcome.
>> thx
>

newbie : backup set begins at LSN xxx, ... too late to apply ...

<< The log in this backup set begins at LSN xxx, which is too late to apply
to the database. An earlier log backup that includes LSN yyy can be
restored >>
ok forgive my ignrance here, using the maintenance plan wizards i have
backups in place that fire full db back up every 4 hours or so and back up
the transaction logs every hour.
i have set it up 2 different maint plans - one writes to the server's hard
diskl; the other writes to a network share using UNC path.
full restore from either location works ok; but when trying to do
transaction log restores i get the error message above. i think its
because:
the 2 transaction log backups are firing at the same time and writing to
different locations, so i would have to bounce back and forth between the 2
locations to get the transaction logs restored in proper order, correct?
obviously i should change this, so suggestions would be welcome.
thxUse only one maintenance plan to either the local HD or the remote share.
HTH
Jerry
"jimbo-black" <passwords.20.jimbo-black@.antichef.net> wrote in message
news:Xns96EFDE4BBEF04jimboblac@.207.115.63.158...
> << The log in this backup set begins at LSN xxx, which is too late to
> apply
> to the database. An earlier log backup that includes LSN yyy can be
> restored >>
> ok forgive my ignrance here, using the maintenance plan wizards i have
> backups in place that fire full db back up every 4 hours or so and back up
> the transaction logs every hour.
> i have set it up 2 different maint plans - one writes to the server's hard
> diskl; the other writes to a network share using UNC path.
> full restore from either location works ok; but when trying to do
> transaction log restores i get the error message above. i think its
> because:
> the 2 transaction log backups are firing at the same time and writing to
> different locations, so i would have to bounce back and forth between the
> 2
> locations to get the transaction logs restored in proper order, correct?
> obviously i should change this, so suggestions would be welcome.
> thx|||...and optionally copy the backup files to the other location after each ba
ckup has been performed.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
news:uFz2fQU0FHA.2652@.TK2MSFTNGP14.phx.gbl...
> Use only one maintenance plan to either the local HD or the remote share.
> HTH
> Jerry
> "jimbo-black" <passwords.20.jimbo-black@.antichef.net> wrote in message
> news:Xns96EFDE4BBEF04jimboblac@.207.115.63.158...
>