Latvian(1062) as full-text indexing/querying language in SQL2005

Hello.

We're using MSSQL server 2005, here in Riga, Latvia.
I've next question - is latvian (code 1062) language will be supported as full-text indexing language in MSSQL 2005?

Thank you.
? If you have your own stemmer and word breakers yes. But otherwise no. -- Hilary CotterDirector of Text Mining and Database StrategyRelevantNOISE.Com - Dedicated to mining blogs for business intelligence. This posting is my own and doesn't necessarily represent RelevantNoise's positions, strategies or opinions. Looking for a SQL Server replication book?http://www.nwsu.com/0974973602.html Looking for a FAQ on Indexing Services/SQL FTShttp://www.indexserverfaq.com <Helge Shep@.discussions.microsoft..com> wrote in message news:5f561573-aeb9-42b5-a6b7-22790cbf049a@.discussions.microsoft.com...Hello.We're using MSSQL server 2005, here in Riga, Latvia.I've next question - is latvian (code 1062) language will be supported as full-text indexing language in MSSQL 2005? Thank you.

Large SQL update - effect on SQL 2005 transactional replication

I'm a newbie to Replication and recently setup the following.

Publisher and Distributor on the same SQL2005 server, then I've got 7 subscribers(SQL2000 servers) and I'm using push subscriptions. I'm replicating 5 SQl tables which don't have too many changes and these are scheduled to run every 3 hours. In a few days a large one off SQL update with add an additional 10,000 rows to one of the replicated tables. I was wondering what impact this would have on the above setup i.e are there any sort of limitations here. I'm assuming not but thought I would check. I'm thinking it will just cause additional overhead on the server, but the update is being applied when no users will be using the database.

Any feedback greatly appreciated.

Thanks

You shouldn't have any problems, just understand that if you do this in one large transaction, logreader agent won't pick up changes until the transaction has been completed/committed, and the distribution agent will not pick up the changes until after the logreader agent has completed.