Thanks
Laurentiu|||HI!! Laurentiu,
Kindly move the thread to Sql Server Data Access Forum.
Thank You
Uminder Khatri|||
The information here is really not sufficient for us to help figure this out. Can you give us some more detail as to what your configuration is?
Are you running .Net 1.1?
What version of SQL Server are you running?
It could quite possibly be that the server is crashing. Can you check out the error logs on the server and see if there's anything suspicious there?
Thanks.
sqlHi all,
I need creat a gannt chart for project server report in SQL reporting service. Is somebody know some good third party tool can help to implement or how to creat by hand?
Thanks in advance!
I use Dundas Chart for Reporting Services and can thoroughly recommend it and it supports Gannt Charts
|||Thanks Jasper! But Dundas chart is a little bit expensive solution for us. It supports SQL 2000 reporting service?|||I downloaded the Dundas Chart for Reporting Services and try to create a Gantt chart. I found it's very difficult to do, as there're many settings on it. Is there any tutorial provided? Thanks!Hi all,
I need creat a gannt chart for project server report in SQL reporting service. Is somebody know some good third party tool can help to implement or how to creat by hand?
Thanks in advance!
I use Dundas Chart for Reporting Services and can thoroughly recommend it and it supports Gannt Charts
|||Thanks Jasper! But Dundas chart is a little bit expensive solution for us. It supports SQL 2000 reporting service?|||I downloaded the Dundas Chart for Reporting Services and try to create a Gantt chart. I found it's very difficult to do, as there're many settings on it. Is there any tutorial provided? Thanks!anyone using ssis ought to consider installing sp1 and the hot fixes.
of course, these should be tested before installing on a server in production.
Also, July update for Books Online is very useful http://www.microsoft.com/downloads/details.aspx?FamilyId=BE6A2C5D-00DF-4220-B133-29C1E0B6585F&displaylang=en -Hi,
We have a NT service built via Visual Basic 6 which fires dts processes on demand according some criteria. Well, on the whole and basically only for the following rule:
-dts process is executed when our service recognize a concrete plain file leaved in a folder. It’s generally generated for a mainframe JCL along with a activator file (.nul file, empty). Each application own a folder and each folder have lots of files as the aforementioned ones. Scheduler for that is an ASP application that lives within a intranet. It also is a monitor and logger
In that schema, keeping on mind that eight out of ten are ETL processes, critical ones and on daily-basis, our question is, how to handle on with this stuff using by sql25k and its powerful SSIS? Migrating such dts packages to SSIS packages is a piece of cake (now no before; thanks Jamie, Michael and other guys for your awesome help) because of its tipology. However our main concern is what the hell to use. Centralized dtsx package running all day long as a service, listening and checking for files? .Net windows application either vb or c#? aspx solution? Set of .vbs interlinked among them?
This is a old post/goal. In spite of we have not defined any deadline for that, what the heck as time goes by is more urgent for us. A restriction: we can’t to programme nothing from our sql25k production cluster physically. Any stuff will be done on workstations.
In terms of cost, no problem at all. We are interested in hear thoughts and point of view about which is the most effective way
Thanks in advance,
I don't like packages running all day, listening for events. The architecture was not designed for that, and we have not tested packages as long running listeners.
I would suggest using SQL Server Agent, with alerts, listening for WMI messages about files arriving. See: http://msdn2.microsoft.com/en-us/library/ms191508.aspx
The alerts can execute SSIS packages using the SQL Agent SSIS subsystem.
Donald
|||Thanks a lot for your answer Donald.sqlHi friends
i work with sql server 2005 express(Management Studio)
can i use full text search service with that edition of sql server?
and how i can use that.
thank u.![Smile [:)]](http://pics.10026.com/?src=/emoticons/emotion-1.gif)
The Full-Text Search feature is not available in SQL Server 2005 Express.
HTH,
Ryan
thank u for ur answering.
so which edition of sql server support that?
|||
fahima wrote:
so which edition of sql server support that?
The Workgroup, Standard, and Enterprise editions all support Full-text Search.
HTH,
Ryan
ok
is it hard to work with service?
|||
is it hard to work with service?
Do you mean is it difficult to get Full-text Search to work? I've never played with Full-text Search, but here's an article that should give you a better understanding of it:Understanding SQL Server Full-Text Indexing.
HTH,
Ryan
the Express Edition does in fact have full text search feature available. to get this you need to download a different file, SQL Server with Advance services -http://msdn.microsoft.com/vstudio/express/sql/compare/default.aspx
Not sure if this was released since the last post here - just though i would answer seeing as i was floating around.
regards
Hello and thank you for your assistance.
I have two instances of SQL Server 2000 Enterprise Edition (SP4) database running on Windows 2000 Enterprise server. The default instance is dev and a named instance for QA. Full-text search is enabled for dev and is functioning properly.
@.@.Version:
Microsoft SQL Server 2000 - 8.00.2040 (Intel X86) May 13 2005 18:33:17 Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
I am trying to enable full text search in the QA instance with this command: "sp_fulltext_database 'enable' ", but I am receiving the error "Server: Msg 7635 The Microsoft Search service cannot be administered under the present user account.
I can find any reference to what account it needs to run under. Can you provide me with info on why I am getting this message?
This is a common error with SQL Server 2000 Full-text Search (FTS) and the MSSearch service and there can be a few root reasons for it.
1. Did this error occur after a service pack upgrade? If so - review the files and folders under \FTDATA (in the sql server installed instance folder) against what is on your SQL Server 2000 CD. If you find any difference - copy the missing or different file from the CD to the problem server.
2. Have you removed the BUILTIN\Administrators login? If so - either add it back in or execute the sp_grantlogin from the code below as the MSSearch service requires this level of access to the MSSQLServer service.
3. Check these:
317746 PRB: SQL Server Full-Text Search Does Not Populate Catalogs
http://support.microsoft.com/kb/317746
277549 PRB: Unable to Build Full-Text Catalog After You Modify MSSQLServer Logon Account Through Control Panel
http://support.microsoft.com/kb/277549
4. Can you run this script and post the results back?
use master
go
SELLECT @.@.version
go
-- many need to set on "show advanced options"
sp_configure 'default full-text language'
go
SELECT FullTextServiceProperty('ResourceUsage') as MSSearch_Resource_Usage
go
xp_logininfo 'BUILTIN\ADMINISTRATORS', 'members'
go
-- if you have removed the BUILTIN\Administrators login, run:
exec sp_grantlogin N'NT Authority\System'
exec sp_defaultdb N'NT Authority\System', N'master'
exec sp_defaultlanguage N'NT Authority\System','us_english'
exec sp_addsrvrolemember N'NT Authority\System', sysadmin
5. And just to cover all the bases, when you changed the MSSQLServer startup account, did you do it via Win2K's Component Services? If so, could you "re-change" it via the Enterprise Manager's server property security tab?
Filip Skakun
|||Filip,
Thank you so much for your response. To answer your questions; No we haven't added any service packs recently. Yes, we do have the Builtin/Administer removed and the NT Authority has all the required privileges. Keep in mind that the default instance was working just fine.
Since the MSSQL$Inst2/FTData directory didn't exist; I suspect that FullText search was not installed with the second instance. None the less, I re-installed fulltext search (see http://support.microsoft.com/kb/827449). After doing this I no longer received the "Cannot be administered under the present account" error and the FTData directory was created for the second instance. But, at this point Full text search didn't work for both instances. I wasn't receiving any errors, but the catalogs were not getting populated. We later found that the switch in the KB article was incorrect for our servers. The article had us run "ftsetup.exe SQLServer$Instance 1 0 0 0" (incorrect). After we ran "ftsetup.exe SQLServer$Instance 0 1 0 0 0" (correct) FullText search began to function correctly for both instances.
To be honest, I don't think I had to reinstall everything. I believe I could have gotten away with just running ftsetup.exe for the second instance.
|||I am glad you got it working,
Regards,
Filip
Hello and thank you for your assistance.
I have two instances of SQL Server 2000 Enterprise Edition (SP4) database running on Windows 2000 Enterprise server. The default instance is dev and a named instance for QA. Full-text search is enabled for dev and is functioning properly.
@.@.Version:
Microsoft SQL Server 2000 - 8.00.2040 (Intel X86) May 13 2005 18:33:17 Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
I am trying to enable full text search in the QA instance with this command: "sp_fulltext_database 'enable' ", but I am receiving the error "Server: Msg 7635 The Microsoft Search service cannot be administered under the present user account.
I can find any reference to what account it needs to run under. Can you provide me with info on why I am getting this message?
This is a common error with SQL Server 2000 Full-text Search (FTS) and the MSSearch service and there can be a few root reasons for it.
1. Did this error occur after a service pack upgrade? If so - review the files and folders under \FTDATA (in the sql server installed instance folder) against what is on your SQL Server 2000 CD. If you find any difference - copy the missing or different file from the CD to the problem server.
2. Have you removed the BUILTIN\Administrators login? If so - either add it back in or execute the sp_grantlogin from the code below as the MSSearch service requires this level of access to the MSSQLServer service.
3. Check these:
317746 PRB: SQL Server Full-Text Search Does Not Populate Catalogs
http://support.microsoft.com/kb/317746
277549 PRB: Unable to Build Full-Text Catalog After You Modify MSSQLServer Logon Account Through Control Panel
http://support.microsoft.com/kb/277549
4. Can you run this script and post the results back?
use master
go
SELLECT @.@.version
go
-- many need to set on "show advanced options"
sp_configure 'default full-text language'
go
SELECT FullTextServiceProperty('ResourceUsage') as MSSearch_Resource_Usage
go
xp_logininfo 'BUILTIN\ADMINISTRATORS', 'members'
go
-- if you have removed the BUILTIN\Administrators login, run:
exec sp_grantlogin N'NT Authority\System'
exec sp_defaultdb N'NT Authority\System', N'master'
exec sp_defaultlanguage N'NT Authority\System','us_english'
exec sp_addsrvrolemember N'NT Authority\System', sysadmin
5. And just to cover all the bases, when you changed the MSSQLServer startup account, did you do it via Win2K's Component Services? If so, could you "re-change" it via the Enterprise Manager's server property security tab?
Filip Skakun
|||Filip,
Thank you so much for your response. To answer your questions; No we haven't added any service packs recently. Yes, we do have the Builtin/Administer removed and the NT Authority has all the required privileges. Keep in mind that the default instance was working just fine.
Since the MSSQL$Inst2/FTData directory didn't exist; I suspect that FullText search was not installed with the second instance. None the less, I re-installed fulltext search (see http://support.microsoft.com/kb/827449). After doing this I no longer received the "Cannot be administered under the present account" error and the FTData directory was created for the second instance. But, at this point Full text search didn't work for both instances. I wasn't receiving any errors, but the catalogs were not getting populated. We later found that the switch in the KB article was incorrect for our servers. The article had us run "ftsetup.exe SQLServer$Instance 1 0 0 0" (incorrect). After we ran "ftsetup.exe SQLServer$Instance 0 1 0 0 0" (correct) FullText search began to function correctly for both instances.
To be honest, I don't think I had to reinstall everything. I believe I could have gotten away with just running ftsetup.exe for the second instance.
|||I am glad you got it working,
Regards,
Filip
Hello and thank you for your assistance.
I have two instances of SQL Server 2000 Enterprise Edition (SP4) database running on Windows 2000 Enterprise server. The default instance is dev and a named instance for QA. Full-text search is enabled for dev and is functioning properly.
@.@.Version:
Microsoft SQL Server 2000 - 8.00.2040 (Intel X86) May 13 2005 18:33:17 Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
I am trying to enable full text search in the QA instance with this command: "sp_fulltext_database 'enable' ", but I am receiving the error "Server: Msg 7635 The Microsoft Search service cannot be administered under the present user account.
I can find any reference to what account it needs to run under. Can you provide me with info on why I am getting this message?
This is a common error with SQL Server 2000 Full-text Search (FTS) and the MSSearch service and there can be a few root reasons for it.
1. Did this error occur after a service pack upgrade? If so - review the files and folders under \FTDATA (in the sql server installed instance folder) against what is on your SQL Server 2000 CD. If you find any difference - copy the missing or different file from the CD to the problem server.
2. Have you removed the BUILTIN\Administrators login? If so - either add it back in or execute the sp_grantlogin from the code below as the MSSearch service requires this level of access to the MSSQLServer service.
3. Check these:
317746 PRB: SQL Server Full-Text Search Does Not Populate Catalogs
http://support.microsoft.com/kb/317746
277549 PRB: Unable to Build Full-Text Catalog After You Modify MSSQLServer Logon Account Through Control Panel
http://support.microsoft.com/kb/277549
4. Can you run this script and post the results back?
use master
go
SELLECT @.@.version
go
-- many need to set on "show advanced options"
sp_configure 'default full-text language'
go
SELECT FullTextServiceProperty('ResourceUsage') as MSSearch_Resource_Usage
go
xp_logininfo 'BUILTIN\ADMINISTRATORS', 'members'
go
-- if you have removed the BUILTIN\Administrators login, run:
exec sp_grantlogin N'NT Authority\System'
exec sp_defaultdb N'NT Authority\System', N'master'
exec sp_defaultlanguage N'NT Authority\System','us_english'
exec sp_addsrvrolemember N'NT Authority\System', sysadmin
5. And just to cover all the bases, when you changed the MSSQLServer startup account, did you do it via Win2K's Component Services? If so, could you "re-change" it via the Enterprise Manager's server property security tab?
Filip Skakun
|||Filip,
Thank you so much for your response. To answer your questions; No we haven't added any service packs recently. Yes, we do have the Builtin/Administer removed and the NT Authority has all the required privileges. Keep in mind that the default instance was working just fine.
Since the MSSQL$Inst2/FTData directory didn't exist; I suspect that FullText search was not installed with the second instance. None the less, I re-installed fulltext search (see http://support.microsoft.com/kb/827449). After doing this I no longer received the "Cannot be administered under the present account" error and the FTData directory was created for the second instance. But, at this point Full text search didn't work for both instances. I wasn't receiving any errors, but the catalogs were not getting populated. We later found that the switch in the KB article was incorrect for our servers. The article had us run "ftsetup.exe SQLServer$Instance 1 0 0 0" (incorrect). After we ran "ftsetup.exe SQLServer$Instance 0 1 0 0 0" (correct) FullText search began to function correctly for both instances.
To be honest, I don't think I had to reinstall everything. I believe I could have gotten away with just running ftsetup.exe for the second instance.
|||I am glad you got it working,
Regards,
Filip
I am conducting performance tuning & optimization of a SQL2K5 database. The server has Full-Text Search Service enabled and running. However, I don't believe the applications are actually using this Service and I am considering disabling it to conserve resources since apps are performing high transactions that are consuming significant resources (memory, CPU).
How much of a performance cost does Full-Text search service impose on the server and is this a recommended way of conserving resource consumption if the Service is not being used or needed by the application?
I haven't found much in Technet, KB or MSDN to address this topic.
Thanks,
Phil
If the FTS is not being used then you must disable it in order to get the system resources back on track.
One thing is sure that FTS has been optimized in SQL 2005 as compared to SQL 2000 version as it refers http://msdn2.microsoft.com/en-us/library/ms345119.aspx here. IMHO you need to disable if you are not using at all on the application.
I expect that since the catalog used to populate, but will no longer populate, this must have something to do with the data added to the table recently.
Do these symptoms match any known issues? What should I do to debug this issue? I'm stuck.
Please help. Thank you.
Dave McCall? Do the gatherer logs reveal anything? -- 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 <Dave McCall@.discussions.microsoft.com> wrote in message news:b6cf47d2-6c0a-4c82-a9f9-42f1d2b71454@.discussions.microsoft.com...I have a SQL Server 2000 database with the latest service pack (3?). For some time, I've had full-text indexing working. Eventually, one of my full-text catalogs failed to populate. After a rebuild, I still couldn't populate it. I dropped it and recreated several catalogs. Eventually, I was able to get all of the original tables into a full-text catalog that populates except one. The offending table has less than 4000 rows in it. It is now in its own catalog which refuses to populate. I can't find any errors in the Application Log that correspond to this catalog population failing.I expect that since the catalog used to populate, but will no longer populate, this must have something to do with the data added to the table recently.Do these symptoms match any known issues? What should I do to debug this issue? I'm stuck.Please help. Thank you.Dave McCall
