full text incremental population

Hi!
Is there any possibility to populate indexes for inserted rows only
(or not to updated rows)
Regards
MaxOn Apr 4, 10:27 am, maxl...@.gmail.com wrote:
> Hi!
> Is there any possibility to populate indexes for inserted rows only
> (or not to updated rows)
> Regards
> Max
pls... if anyone has came up with same problem. share your knowledge

full text incremental population

Hi!
Is there any possibility to populate indexes for inserted rows only
(or not to updated rows)
Regards
Max
On Apr 4, 10:27 am, maxl...@.gmail.com wrote:
> Hi!
> Is there any possibility to populate indexes for inserted rows only
> (or not to updated rows)
> Regards
> Max
pls... if anyone has came up with same problem. share your knowledge

Full Text - Trusted account

Hello,
When I run an incremental/full job for a full text
catalog on win 2k , SQL 2K sp3a cluster server, i am
getting this in the SQL error log
Login failed for user domain\servername$
We recently removed the local admin group having syadmin
access to the server.
I changed the Job owner to the SQL Startup account, even
then it is using the above login. Why is that ?
I couldnt be able to grant the login access as i am not
able to see in the list of users...
Where is this login, can i change something to fix ?
Thanks
- Saravana
can you add this account to the system administrator role?
if not exists (select * from master.dbo.syslogins where loginname = N'NT
Authority\System')
exec sp_grantlogin N'NT Authority\System'
exec sp_defaultdb N'NT Authority\System', N'master'
exec sp_defaultlanguage N'NT Authority\System', N'us_english'
GO
exec sp_addsrvrolemember N'NT Authority\System', sysadmin
GO
"SK" <anonymous@.discussions.microsoft.com> wrote in message
news:1420b01c41808$d9e0f460$a601280a@.phx.gbl...
> Hello,
> When I run an incremental/full job for a full text
> catalog on win 2k , SQL 2K sp3a cluster server, i am
> getting this in the SQL error log
> Login failed for user domain\servername$
> We recently removed the local admin group having syadmin
> access to the server.
> I changed the Job owner to the SQL Startup account, even
> then it is using the above login. Why is that ?
> I couldnt be able to grant the login access as i am not
> able to see in the list of users...
> Where is this login, can i change something to fix ?
> Thanks
> - Saravana
>

Full and Incremental Backup Question

1) We are doing Weekly Full & DAILY night incremental backup of TL using Veritas Backup Manager to Tape.

One day I took Incremental Backup of TL file manually using studio and deleted the backup file.

Will I able to restore completed if something happens on next day ? Is automated backup takes care of Incremental backup from last night instead of manual interim backup ?

What is the recommendation ? If automated backup is enabled, we should not do manual backup ?

2) In Full Recovery Modek , If I do full backup , Does it backup Transactional Log also or only Datafiles ?

Thanks

Full Backup makes a copy of all database objects and data, including any changes that occur while the Backup is running.

Differential Backup makes a copy of all changes since the last Full Backup.

There is NO 'Incremental Backup'. That is accomplished using the Transaction Log Backup.

If you make a Full Backup on Sunday, and Differential Backups every night, then you will be able to restore your database to its condition when the last differential backup was made. Any datachanges since the Differential backup may be at risk.

Transaction Log Backups make a copy of all changes to the database since the last Full Backup OR the last Transaction Log Backup. IF your Recovery model is set for 'Full', or 'Bulk Logged', and you are making Transaction Log Backups, then you 'should' be able to recover up until a moment before the data corruption event.

|||

We are doing weekly full backup for all databases & daily incremental other than system databases.

Is weekly full backup of System databases good enough to restore from failure ?

|||

In a 'static' environment, weekly backups for the system databases may be just fine. The only significant loss would be the Job History since the last msdb backup. (By static, I mean no new logins, no new Jobs, no new databases, etc.

In a developing environment, more frequent backups of system database will help prevent the loss of any changes to system settings, logins, jobs, job history, etc.

|||It is always hard to tell if a backup strategy is sufficient for your needs, as this depends on how much data loss you are willing to allow, how much money you can spend on your backup strategy, how the backups interfer with the productive system, how long the recovery process can be, etc. First of all I would start by defining how much data loss you can afford. if you don′t care about a one day loss, you can leave it up to one full backup (But remember that even this backup could be destroyed for some reason), if you need more backup and more data availbility you will have to scale it through differential and transactionlog backups.

Jens K. Suessmeyer.

http://www.sqlserver2005.de