For some reason, when I try to generate a script for Triggers off of a View
using DMO, I get back garbage like:
?VIEW1
That's the complete text coming back, nothing more. I can see it clearly
using MSEM just fine. Any thoughts?
Lee
Can you post your code, so that we can look into it?
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Lee Grissom" <lee dot grissom at quest dot com> wrote in message
news:uyVQJqqdFHA.3932@.TK2MSFTNGP12.phx.gbl...
For some reason, when I try to generate a script for Triggers off of a View
using DMO, I get back garbage like:
?VIEW1
That's the complete text coming back, nothing more. I can see it clearly
using MSEM just fine. Any thoughts?
Lee
|||You mean scripting an INSTEAD OF TRIGGER on a VIEW?
GertD@.SQLDev.Net
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright SQLDev.Net 1991-2005 All rights reserved.
"Lee Grissom" <lee dot grissom at quest dot com> wrote in message
news:uyVQJqqdFHA.3932@.TK2MSFTNGP12.phx.gbl...
> For some reason, when I try to generate a script for Triggers off of a
> View using DMO, I get back garbage like:
> ?VIEW1
> That's the complete text coming back, nothing more. I can see it clearly
> using MSEM just fine. Any thoughts?
> --
> Lee
>
|||This works for me:
CREATE TABLE Person
(
SSN char(11) PRIMARY KEY,
Name nvarchar(100),
Address nvarchar(100),
Birthdate datetime
)
go
CREATE TABLE EmployeeTable
(
EmployeeID int PRIMARY KEY,
SSN char(11) UNIQUE,
Department nvarchar(10),
Salary money,
CONSTRAINT FKEmpPer FOREIGN KEY (SSN)
REFERENCES Person (SSN)
)
go
CREATE VIEW Employee AS
SELECT P.SSN as SSN, Name, Address,
Birthdate, EmployeeID, Department, Salary
FROM Person P, EmployeeTable E
WHERE P.SSN = E.SSN
go
CREATE TABLE PersonDuplicates
(
SSN char(11),
Name nvarchar(100),
Address nvarchar(100),
Birthdate datetime,
InsertSNAME nchar(100),
WhenInserted datetime
)
go
CREATE TRIGGER IO_Trig_INS_Employee ON Employee
INSTEAD OF INSERT
AS
BEGIN
SET NOCOUNT ON
-- Check for duplicate Person. If no duplicate, do an insert.
IF (NOT EXISTS (SELECT P.SSN
FROM Person P, inserted I
WHERE P.SSN = I.SSN))
INSERT INTO Person
SELECT SSN,Name,Address,Birthdate
FROM inserted
ELSE
-- Log attempt to insert duplicate Person row in PersonDuplicates table.
INSERT INTO PersonDuplicates
SELECT SSN,Name,Address,Birthdate,SUSER_SNAME(),GETDATE()
FROM inserted
-- Check for duplicate Employee. If no duplicate, do an insert.
IF (NOT EXISTS (SELECT E.SSN
FROM EmployeeTable E, inserted
WHERE E.SSN = inserted.SSN))
INSERT INTO EmployeeTable
SELECT EmployeeID,SSN, Department, Salary
FROM inserted
ELSE
--If duplicate, change to UPDATE so that there will not
--be a duplicate key violation error.
UPDATE EmployeeTable
SET EmployeeID = I.EmployeeID,
Department = I.Department,
Salary = I.Salary
FROM EmployeeTable E, inserted I
WHERE E.SSN = I.SSN
END
go
using System;
using System.Runtime.InteropServices;
using SQLDMO;
namespace SDN
{
class ScriptInsteadOfTrigger
{
[MTAThread]
static void Main(string[] args)
{
try
{
SQLServer2Class server = new SQLServer2Class();
server.LoginSecure = true;
server.Connect("(local)\\sql80", null, null);
Database2 database = (Database2) server.Databases.Item("testdb", "dbo");
View2 view = (View2) database.Views.Item("Employee", "dbo");
Trigger2 trigger = (Trigger2) view.Triggers.Item("IO_Trig_INS_Employee",
"dbo");
SQLDMO_SCRIPT_TYPE scriptType = SQLDMO_SCRIPT_TYPE.SQLDMOScript_Default;
SQLDMO_SCRIPT2_TYPE script2Type =
SQLDMO_SCRIPT2_TYPE.SQLDMOScript2_Default;
string sql = trigger.Script(scriptType, null, script2Type);
server.DisConnect();
}
catch(System.Runtime.InteropServices.COMException ex)
{
Console.WriteLine(ex);
}
catch(System.Exception ex)
{
Console.WriteLine(ex);
}
}
}
}
GertD@.SQLDev.Net
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright SQLDev.Net 1991-2005 All rights reserved.
"Lee Grissom" <lee dot grissom at quest dot com> wrote in message
news:uyVQJqqdFHA.3932@.TK2MSFTNGP12.phx.gbl...
> For some reason, when I try to generate a script for Triggers off of a
> View using DMO, I get back garbage like:
> ?VIEW1
> That's the complete text coming back, nothing more. I can see it clearly
> using MSEM just fine. Any thoughts?
> --
> Lee
>
Showing posts with label text. Show all posts
Showing posts with label text. Show all posts
Sunday, March 25, 2012
Thursday, March 22, 2012
Can't find log-shipping option
In the text on the link (part 2 - below) - I cannot find the "Transaction
Log Shipping" option Is this an SP4 option only for SQL Server 2000?
http://msdn2.microsoft.com/en-gb/library/ms189071.aspx
Right-click the database you want to use as your primary database in the log
shipping configuration, and then click Properties.
Under Select a page, click Transaction Log Shipping.
Clear the Enable this as a primary database in a log shipping configuration
check box.
Regards,
Jamie
I may be asking the wrong question - Is there a wizard that assists in the
creation of log shipping or is it done strictly with a DTS package?
Regards,
Jamie
"thejamie" wrote:
> In the text on the link (part 2 - below) - I cannot find the "Transaction
> Log Shipping" option Is this an SP4 option only for SQL Server 2000?
> http://msdn2.microsoft.com/en-gb/library/ms189071.aspx
> ----
> Right-click the database you want to use as your primary database in the log
> shipping configuration, and then click Properties.
> Under Select a page, click Transaction Log Shipping.
> Clear the Enable this as a primary database in a log shipping configuration
> check box.
> --
> Regards,
> Jamie
|||Jamie,
the original MSDN2 link you supplied applies to SQL Server 2005, but as you
are tlaking about DTS you must be using SQL Server 2000. In your edition of
sql server, you'll set this up using a maintenance plan. In the first screen
there's a checkbox at the bottom for log shipping.
Rgds,
Paul Ibison
|||Actually, it looks from the description you are giving me that the SQL Server
2000 Standard edition does not support log shipping. We are running both
but are not currently in a position to migrate to 2005.
Regards,
Jamie
"Paul Ibison" wrote:
> Jamie,
> the original MSDN2 link you supplied applies to SQL Server 2005, but as you
> are tlaking about DTS you must be using SQL Server 2000. In your edition of
> sql server, you'll set this up using a maintenance plan. In the first screen
> there's a checkbox at the bottom for log shipping.
> Rgds,
> Paul Ibison
>
>
|||Paul,
I can see from looking at various articles on the web that log shipping is
possible without the enterprise version. Are there sample scripts available
for this (SQL Server 2000)?
Regards,
Jamie
"Paul Ibison" wrote:
> Jamie,
> the original MSDN2 link you supplied applies to SQL Server 2005, but as you
> are tlaking about DTS you must be using SQL Server 2000. In your edition of
> sql server, you'll set this up using a maintenance plan. In the first screen
> there's a checkbox at the bottom for log shipping.
> Rgds,
> Paul Ibison
>
>
|||Jamie - these scripts are in the Backoffice Resource Kit, and are also on
some sites (eg
http://www.sql-server-performance.com/sql_server_log_shipping.asp).
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||I also see that we have not turned on our backup logs option. Is there an
impact on the server if I turn it on?
Regards,
Jamie
"Paul Ibison" wrote:
> Jamie - these scripts are in the Backoffice Resource Kit, and are also on
> some sites (eg
> http://www.sql-server-performance.com/sql_server_log_shipping.asp).
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
>
>
|||This is pretty much standard on a production server. If you only have simple
recovery mode, the DR plan will rely on complete backups only and will
therefore expose you to a large potential data loss. Much better to use FULL
and regular log backups. There will be an impact on the production server as
the log backup will need to access the disk, but this is unavoidable to have
a decent DR plan, and if the backups begin to take too long on the disk, you
can use LiteSpeed
(http://www.quest.com/litespeed_for_sql_server/overview.aspx) or equivalent.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||Paul,
After turning on the option to save the transaction logs, in six short
hours, there was an accumulation of over 10gig of data. I suspect that given
the absense of a wizard, my better choice is the litespeed or a similar tool.
Is there a reason you chose litespeed - there are a couple of other products
reviewed in this month's sql mag... I suspect that I have more to manage
than I can handle at this point.
Regards,
Jamie
"Paul Ibison" wrote:
> This is pretty much standard on a production server. If you only have simple
> recovery mode, the DR plan will rely on complete backups only and will
> therefore expose you to a large potential data loss. Much better to use FULL
> and regular log backups. There will be an impact on the production server as
> the log backup will need to access the disk, but this is unavoidable to have
> a decent DR plan, and if the backups begin to take too long on the disk, you
> can use LiteSpeed
> (http://www.quest.com/litespeed_for_sql_server/overview.aspx) or equivalent.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
>
>
>
|||Jamie,
I looked at a couple and simply went for the market leader on the assumption
that they were less likely to go bust
If you start using this type of tool, the log-shipping will have to be
hand-crafted as SQL Server won't recognise the backup files. This sounds
like a pain, but in reality log shipping is very simple technology and can
easily be created via a series of your own jobs. Using SQLLiteSpeed in this
way is supported as it has extended stored procedures to do the backup and
the restore.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
Log Shipping" option Is this an SP4 option only for SQL Server 2000?
http://msdn2.microsoft.com/en-gb/library/ms189071.aspx
Right-click the database you want to use as your primary database in the log
shipping configuration, and then click Properties.
Under Select a page, click Transaction Log Shipping.
Clear the Enable this as a primary database in a log shipping configuration
check box.
Regards,
Jamie
I may be asking the wrong question - Is there a wizard that assists in the
creation of log shipping or is it done strictly with a DTS package?
Regards,
Jamie
"thejamie" wrote:
> In the text on the link (part 2 - below) - I cannot find the "Transaction
> Log Shipping" option Is this an SP4 option only for SQL Server 2000?
> http://msdn2.microsoft.com/en-gb/library/ms189071.aspx
> ----
> Right-click the database you want to use as your primary database in the log
> shipping configuration, and then click Properties.
> Under Select a page, click Transaction Log Shipping.
> Clear the Enable this as a primary database in a log shipping configuration
> check box.
> --
> Regards,
> Jamie
|||Jamie,
the original MSDN2 link you supplied applies to SQL Server 2005, but as you
are tlaking about DTS you must be using SQL Server 2000. In your edition of
sql server, you'll set this up using a maintenance plan. In the first screen
there's a checkbox at the bottom for log shipping.
Rgds,
Paul Ibison
|||Actually, it looks from the description you are giving me that the SQL Server
2000 Standard edition does not support log shipping. We are running both
but are not currently in a position to migrate to 2005.
Regards,
Jamie
"Paul Ibison" wrote:
> Jamie,
> the original MSDN2 link you supplied applies to SQL Server 2005, but as you
> are tlaking about DTS you must be using SQL Server 2000. In your edition of
> sql server, you'll set this up using a maintenance plan. In the first screen
> there's a checkbox at the bottom for log shipping.
> Rgds,
> Paul Ibison
>
>
|||Paul,
I can see from looking at various articles on the web that log shipping is
possible without the enterprise version. Are there sample scripts available
for this (SQL Server 2000)?
Regards,
Jamie
"Paul Ibison" wrote:
> Jamie,
> the original MSDN2 link you supplied applies to SQL Server 2005, but as you
> are tlaking about DTS you must be using SQL Server 2000. In your edition of
> sql server, you'll set this up using a maintenance plan. In the first screen
> there's a checkbox at the bottom for log shipping.
> Rgds,
> Paul Ibison
>
>
|||Jamie - these scripts are in the Backoffice Resource Kit, and are also on
some sites (eg
http://www.sql-server-performance.com/sql_server_log_shipping.asp).
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||I also see that we have not turned on our backup logs option. Is there an
impact on the server if I turn it on?
Regards,
Jamie
"Paul Ibison" wrote:
> Jamie - these scripts are in the Backoffice Resource Kit, and are also on
> some sites (eg
> http://www.sql-server-performance.com/sql_server_log_shipping.asp).
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
>
>
|||This is pretty much standard on a production server. If you only have simple
recovery mode, the DR plan will rely on complete backups only and will
therefore expose you to a large potential data loss. Much better to use FULL
and regular log backups. There will be an impact on the production server as
the log backup will need to access the disk, but this is unavoidable to have
a decent DR plan, and if the backups begin to take too long on the disk, you
can use LiteSpeed
(http://www.quest.com/litespeed_for_sql_server/overview.aspx) or equivalent.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||Paul,
After turning on the option to save the transaction logs, in six short
hours, there was an accumulation of over 10gig of data. I suspect that given
the absense of a wizard, my better choice is the litespeed or a similar tool.
Is there a reason you chose litespeed - there are a couple of other products
reviewed in this month's sql mag... I suspect that I have more to manage
than I can handle at this point.
Regards,
Jamie
"Paul Ibison" wrote:
> This is pretty much standard on a production server. If you only have simple
> recovery mode, the DR plan will rely on complete backups only and will
> therefore expose you to a large potential data loss. Much better to use FULL
> and regular log backups. There will be an impact on the production server as
> the log backup will need to access the disk, but this is unavoidable to have
> a decent DR plan, and if the backups begin to take too long on the disk, you
> can use LiteSpeed
> (http://www.quest.com/litespeed_for_sql_server/overview.aspx) or equivalent.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
>
>
>
|||Jamie,
I looked at a couple and simply went for the market leader on the assumption
that they were less likely to go bust
If you start using this type of tool, the log-shipping will have to be
hand-crafted as SQL Server won't recognise the backup files. This sounds
like a pain, but in reality log shipping is very simple technology and can
easily be created via a series of your own jobs. Using SQLLiteSpeed in this
way is supported as it has extended stored procedures to do the backup and
the restore.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
Can't find how to add a line feed to a textbox
Hello,
I'm creating a report with a textbox that contains a field from the dataset
and some hard text (something like =First(Fields!MyField.Value) & "
TheTextPart"). This works, but when I try to do a shift+enter (line feed) I
get an error "The value expresxsion for the textbox 'textbox7' contains an
error: [BC30648] String constants must end with a double quote".
Is there any way to add a line feed / carriage return in a text box?
Thanks!
Ricktry this:
=First(Fields!MyField.Value) & vbcrlf & "The Second Line" & vbcrlf &
"The Third Line"|||Brilliant! Thanks Sleepy!
"SleepyLab" <david.blancard@.fairmont.com> wrote in message
news:1187036726.406106.312410@.d55g2000hsg.googlegroups.com...
> try this:
> =First(Fields!MyField.Value) & vbcrlf & "The Second Line" & vbcrlf &
> "The Third Line"
>
I'm creating a report with a textbox that contains a field from the dataset
and some hard text (something like =First(Fields!MyField.Value) & "
TheTextPart"). This works, but when I try to do a shift+enter (line feed) I
get an error "The value expresxsion for the textbox 'textbox7' contains an
error: [BC30648] String constants must end with a double quote".
Is there any way to add a line feed / carriage return in a text box?
Thanks!
Ricktry this:
=First(Fields!MyField.Value) & vbcrlf & "The Second Line" & vbcrlf &
"The Third Line"|||Brilliant! Thanks Sleepy!
"SleepyLab" <david.blancard@.fairmont.com> wrote in message
news:1187036726.406106.312410@.d55g2000hsg.googlegroups.com...
> try this:
> =First(Fields!MyField.Value) & vbcrlf & "The Second Line" & vbcrlf &
> "The Third Line"
>
Tuesday, March 20, 2012
Can't enable Full Text on database
Got a strange problem.
Had a SQL 7.0 Box with FTS on a database. Worked fine except for one quirk
we never tracked down. Starting up the MSSearch Service would fail 1/2 the
time due to timeout. Other 1/2 would take a long time (like sometimes an
hour) to start.
Upgraded to SQL 2000, no SP.
Upgrade went fine, similar startup problems.
Applied SP4.
Got the usual warning about having to recreate indices, etc. Not a problem
since we were releasing new code specifically for SQL 2000 FT.
Now... well it just doesn't work.
For example, if I try to start an index build on a table, I get Error 15601:
Full-Text Search is not enabled for the current database...
Ok, no problem.. try
sp_fulltext_database 'enable'
get
Server: Msg 7635, Level 16, State 1, Procedure sp_fulltext_database, Line 46
The Microsoft Search service cannot be administered under the present user
account
First thought was try to synchronize the passwords (i.e. start/stop SQL
Server, change to local account and then back to the domain account so that
MSSearch can talk to it.)
No Joy.
So, at this point I'm either facing calling Microsoft, or taking the server
offline for a day while I uninstall SQL 2000, reinstall it and re-attach the
databases and hope that works.
Suggestions?
--
Greg D. Moore
President Green Mountain Software
Personal: http://stratton.greenms.com
SQL Server Consulting sql at greenms.com
Hi Greg,
Yep, I remember your SQL 7.0 box & the related FTS problems as FTS in SQL
7.0 was problematic at best...
In regards to error "The Microsoft Search service cannot be administered
under the present user account", have you removed or altered the
BUILTIN\Administrators login? If so, then this breaks FTS as the MSSearch
service uses this account to login into SQL Server. If you cannot add back
this login or cannot alter the login back to all of its default for security
reasons, you can use the following SQL code to enable the localsystem
account to have the proper security as a workaround:
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
See KB article 263712 "INF: How To Prevent Windows NT Administrators From
Administering a Clustered SQL Server" at
http://support.microsoft.com/default...;EN-US;q263712 for details.
Hope that helps,
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"Greg D. Moore (Strider)" <mooregr_deleteth1s@.greenms.com> wrote in message
news:8Ln0f.8178$QE1.857@.newsread2.news.atl.earthli nk.net...
> Got a strange problem.
> Had a SQL 7.0 Box with FTS on a database. Worked fine except for one
> quirk
> we never tracked down. Starting up the MSSearch Service would fail 1/2
> the
> time due to timeout. Other 1/2 would take a long time (like sometimes an
> hour) to start.
> Upgraded to SQL 2000, no SP.
> Upgrade went fine, similar startup problems.
> Applied SP4.
> Got the usual warning about having to recreate indices, etc. Not a
> problem
> since we were releasing new code specifically for SQL 2000 FT.
> Now... well it just doesn't work.
> For example, if I try to start an index build on a table, I get Error
> 15601:
> Full-Text Search is not enabled for the current database...
> Ok, no problem.. try
> sp_fulltext_database 'enable'
> get
> Server: Msg 7635, Level 16, State 1, Procedure sp_fulltext_database, Line
> 46
> The Microsoft Search service cannot be administered under the present user
> account
> First thought was try to synchronize the passwords (i.e. start/stop SQL
> Server, change to local account and then back to the domain account so
> that
> MSSearch can talk to it.)
> No Joy.
> So, at this point I'm either facing calling Microsoft, or taking the
> server
> offline for a day while I uninstall SQL 2000, reinstall it and re-attach
> the
> databases and hope that works.
> Suggestions?
>
>
> --
> --
> Greg D. Moore
> President Green Mountain Software
> Personal: http://stratton.greenms.com
> SQL Server Consulting sql at greenms.com
>
|||"John Kane" <jt-kane@.comcast.net> wrote in message
news:eDz9GhVyFHA.720@.TK2MSFTNGP15.phx.gbl...
> Hi Greg,
> Yep, I remember your SQL 7.0 box & the related FTS problems as FTS in SQL
> 7.0 was problematic at best...
Oh good. :-)
> In regards to error "The Microsoft Search service cannot be administered
> under the present user account", have you removed or altered the
> BUILTIN\Administrators login?
Not that I am aware of.
> If so, then this breaks FTS as the MSSearch
> service uses this account to login into SQL Server. If you cannot add back
> this login or cannot alter the login back to all of its default for
security
> reasons, you can use the following SQL code to enable the localsystem
> account to have the proper security as a workaround:
> 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
Tried this, still no joy.
Did notice the database in question the name dbo was mapped to a login
called MONITOR (one of our internal accounts) instead of sa or
domain\administrator.
I've removed that mapping. So far hasn't helped.
> See KB article 263712 "INF: How To Prevent Windows NT Administrators From
> Administering a Clustered SQL Server" at
> http://support.microsoft.com/default...;EN-US;q263712 for
details.
>
Nothing here stood out.
Thanks though.
> Hope that helps,
> John
> --
> SQL Full Text Search Blog
> http://spaces.msn.com/members/jtkane/
>
> "Greg D. Moore (Strider)" <mooregr_deleteth1s@.greenms.com> wrote in
message[vbcol=seagreen]
> news:8Ln0f.8178$QE1.857@.newsread2.news.atl.earthli nk.net...
an[vbcol=seagreen]
Line[vbcol=seagreen]
user
>
|||Hi Greg,
Hmm... It is possible it is something new &/or affected by SP4. I take it
you upgraded to SP4 directly from RTM, and not RTM to SP3 then to SP4.
Correct? I've not heard of any new FTS related bugs in SP4 that are
directly related to this error. However, there are two FIX kb articles
(http://support.microsoft.com/?kbid=900390 - post-SP4 and
http://support.microsoft.com/default...b;en-us;890043 - post SP3)
that I've blogged about in August, neither are well written IMHO.
The below workaround has in the past resolved this issue, however, in all
cases it was pre-SP4. As this is related to a possible SP4 issue, you might
want to open that support issue with MS PSS SQL Server support... :-(
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"Greg D. Moore (Strider)" <mooregr_deleteth1s@.greenms.com> wrote in message
news:zFP0f.9074$vw6.4605@.newsread1.news.atl.earthl ink.net...
> "John Kane" <jt-kane@.comcast.net> wrote in message
> news:eDz9GhVyFHA.720@.TK2MSFTNGP15.phx.gbl...
> Oh good. :-)
>
> Not that I am aware of.
> security
> Tried this, still no joy.
> Did notice the database in question the name dbo was mapped to a login
> called MONITOR (one of our internal accounts) instead of sa or
> domain\administrator.
> I've removed that mapping. So far hasn't helped.
>
> details.
> Nothing here stood out.
> Thanks though.
> message
> an
> Line
> user
>
Had a SQL 7.0 Box with FTS on a database. Worked fine except for one quirk
we never tracked down. Starting up the MSSearch Service would fail 1/2 the
time due to timeout. Other 1/2 would take a long time (like sometimes an
hour) to start.
Upgraded to SQL 2000, no SP.
Upgrade went fine, similar startup problems.
Applied SP4.
Got the usual warning about having to recreate indices, etc. Not a problem
since we were releasing new code specifically for SQL 2000 FT.
Now... well it just doesn't work.
For example, if I try to start an index build on a table, I get Error 15601:
Full-Text Search is not enabled for the current database...
Ok, no problem.. try
sp_fulltext_database 'enable'
get
Server: Msg 7635, Level 16, State 1, Procedure sp_fulltext_database, Line 46
The Microsoft Search service cannot be administered under the present user
account
First thought was try to synchronize the passwords (i.e. start/stop SQL
Server, change to local account and then back to the domain account so that
MSSearch can talk to it.)
No Joy.
So, at this point I'm either facing calling Microsoft, or taking the server
offline for a day while I uninstall SQL 2000, reinstall it and re-attach the
databases and hope that works.
Suggestions?
--
Greg D. Moore
President Green Mountain Software
Personal: http://stratton.greenms.com
SQL Server Consulting sql at greenms.com
Hi Greg,
Yep, I remember your SQL 7.0 box & the related FTS problems as FTS in SQL
7.0 was problematic at best...
In regards to error "The Microsoft Search service cannot be administered
under the present user account", have you removed or altered the
BUILTIN\Administrators login? If so, then this breaks FTS as the MSSearch
service uses this account to login into SQL Server. If you cannot add back
this login or cannot alter the login back to all of its default for security
reasons, you can use the following SQL code to enable the localsystem
account to have the proper security as a workaround:
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
See KB article 263712 "INF: How To Prevent Windows NT Administrators From
Administering a Clustered SQL Server" at
http://support.microsoft.com/default...;EN-US;q263712 for details.
Hope that helps,
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"Greg D. Moore (Strider)" <mooregr_deleteth1s@.greenms.com> wrote in message
news:8Ln0f.8178$QE1.857@.newsread2.news.atl.earthli nk.net...
> Got a strange problem.
> Had a SQL 7.0 Box with FTS on a database. Worked fine except for one
> quirk
> we never tracked down. Starting up the MSSearch Service would fail 1/2
> the
> time due to timeout. Other 1/2 would take a long time (like sometimes an
> hour) to start.
> Upgraded to SQL 2000, no SP.
> Upgrade went fine, similar startup problems.
> Applied SP4.
> Got the usual warning about having to recreate indices, etc. Not a
> problem
> since we were releasing new code specifically for SQL 2000 FT.
> Now... well it just doesn't work.
> For example, if I try to start an index build on a table, I get Error
> 15601:
> Full-Text Search is not enabled for the current database...
> Ok, no problem.. try
> sp_fulltext_database 'enable'
> get
> Server: Msg 7635, Level 16, State 1, Procedure sp_fulltext_database, Line
> 46
> The Microsoft Search service cannot be administered under the present user
> account
> First thought was try to synchronize the passwords (i.e. start/stop SQL
> Server, change to local account and then back to the domain account so
> that
> MSSearch can talk to it.)
> No Joy.
> So, at this point I'm either facing calling Microsoft, or taking the
> server
> offline for a day while I uninstall SQL 2000, reinstall it and re-attach
> the
> databases and hope that works.
> Suggestions?
>
>
> --
> --
> Greg D. Moore
> President Green Mountain Software
> Personal: http://stratton.greenms.com
> SQL Server Consulting sql at greenms.com
>
|||"John Kane" <jt-kane@.comcast.net> wrote in message
news:eDz9GhVyFHA.720@.TK2MSFTNGP15.phx.gbl...
> Hi Greg,
> Yep, I remember your SQL 7.0 box & the related FTS problems as FTS in SQL
> 7.0 was problematic at best...
Oh good. :-)
> In regards to error "The Microsoft Search service cannot be administered
> under the present user account", have you removed or altered the
> BUILTIN\Administrators login?
Not that I am aware of.
> If so, then this breaks FTS as the MSSearch
> service uses this account to login into SQL Server. If you cannot add back
> this login or cannot alter the login back to all of its default for
security
> reasons, you can use the following SQL code to enable the localsystem
> account to have the proper security as a workaround:
> 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
Tried this, still no joy.
Did notice the database in question the name dbo was mapped to a login
called MONITOR (one of our internal accounts) instead of sa or
domain\administrator.
I've removed that mapping. So far hasn't helped.
> See KB article 263712 "INF: How To Prevent Windows NT Administrators From
> Administering a Clustered SQL Server" at
> http://support.microsoft.com/default...;EN-US;q263712 for
details.
>
Nothing here stood out.
Thanks though.
> Hope that helps,
> John
> --
> SQL Full Text Search Blog
> http://spaces.msn.com/members/jtkane/
>
> "Greg D. Moore (Strider)" <mooregr_deleteth1s@.greenms.com> wrote in
message[vbcol=seagreen]
> news:8Ln0f.8178$QE1.857@.newsread2.news.atl.earthli nk.net...
an[vbcol=seagreen]
Line[vbcol=seagreen]
user
>
|||Hi Greg,
Hmm... It is possible it is something new &/or affected by SP4. I take it
you upgraded to SP4 directly from RTM, and not RTM to SP3 then to SP4.
Correct? I've not heard of any new FTS related bugs in SP4 that are
directly related to this error. However, there are two FIX kb articles
(http://support.microsoft.com/?kbid=900390 - post-SP4 and
http://support.microsoft.com/default...b;en-us;890043 - post SP3)
that I've blogged about in August, neither are well written IMHO.
The below workaround has in the past resolved this issue, however, in all
cases it was pre-SP4. As this is related to a possible SP4 issue, you might
want to open that support issue with MS PSS SQL Server support... :-(
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"Greg D. Moore (Strider)" <mooregr_deleteth1s@.greenms.com> wrote in message
news:zFP0f.9074$vw6.4605@.newsread1.news.atl.earthl ink.net...
> "John Kane" <jt-kane@.comcast.net> wrote in message
> news:eDz9GhVyFHA.720@.TK2MSFTNGP15.phx.gbl...
> Oh good. :-)
>
> Not that I am aware of.
> security
> Tried this, still no joy.
> Did notice the database in question the name dbo was mapped to a login
> called MONITOR (one of our internal accounts) instead of sa or
> domain\administrator.
> I've removed that mapping. So far hasn't helped.
>
> details.
> Nothing here stood out.
> Thanks though.
> message
> an
> Line
> user
>
Sunday, March 11, 2012
Can't delete full text catalog on clustered sql serer 2000
Basically SQL Server has allowed me to create a full text catalog on a drive
which is not part of the cluster's shared resources, and I believe doesn't
exist either (I not familiar with clustering at all).
Now the problem is that it now won't let me remove this full text catalog,
giving me the error that it can't *create* a full text catalog on a disk
which isn't part of the cluster's shared resources. How can I delete it?
Ian.Ian,
Most un-usual! As by design, you should be only able to create FT Catalogs
on the shard drive in a clustered environment. How did you do this? If it
can be reproduced, it should be filed as a bug. Have you tried the
following:
use <your_database_name>
go
exec sp_fulltext_catalog '<Your_FT_Catalog_Name>','drop'
go
If not, try it. If it fails, please post the error that it returns. If it
does fail, you may have to try:
EXEC sp_fulltext_service 'clean_up'
if this too fails, I have some code I can email you directly code (the code
is not for the faint-of-heart) that can get you out of this "catch-22"
situation.
Thanks,
John
--
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"Ian" <Ixpah@.newsgroup.nospam> wrote in message
news:#rqy8sFBFHA.3588@.TK2MSFTNGP11.phx.gbl...
> Basically SQL Server has allowed me to create a full text catalog on a
drive
> which is not part of the cluster's shared resources, and I believe doesn't
> exist either (I not familiar with clustering at all).
> Now the problem is that it now won't let me remove this full text catalog,
> giving me the error that it can't *create* a full text catalog on a disk
> which isn't part of the cluster's shared resources. How can I delete it?
> Ian.
>|||Hello Ian,
To understsand the issue better, I'd like to know the exact steps you
create and delete the full text catalog. What is the exact error message
you encountered?
Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
| From: "Ian" <Ixpah@.newsgroup.nospam>
| Subject: Can't delete full text catalog on clustered sql serer 2000
| Date: Thu, 27 Jan 2005 10:30:33 -0000
| Lines: 11
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
| X-RFC2646: Format=Flowed; Original
| Message-ID: <#rqy8sFBFHA.3588@.TK2MSFTNGP11.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.programming
| NNTP-Posting-Host: host81-137-218-140.in-addr.btopenworld.com
81.137.218.140
| Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXS01.phx.gbl!cpmsftngxa06.phx.gbl!TK2MSFTNGP08
.phx.gbl!TK2MSFTNGP11.phx.gbl
| Xref: cpmsftngxa10.phx.gbl microsoft.public.sqlserver.programming:499844
| X-Tomcat-NG: microsoft.public.sqlserver.programming
|
| Basically SQL Server has allowed me to create a full text catalog on a
drive
| which is not part of the cluster's shared resources, and I believe
doesn't
| exist either (I not familiar with clustering at all).
|
| Now the problem is that it now won't let me remove this full text
catalog,
| giving me the error that it can't *create* a full text catalog on a disk
| which isn't part of the cluster's shared resources. How can I delete it?
|
| Ian.
|
|
||||I used a script which was very similiar (if not the same) as this:
exec sp_fulltext_database 'enable'
exec sp_fulltext_catalog 'popall_ft','create'
exec sp_fulltext_table 'dbo. articles','create','popall_ft','pk__arti
cles'
exec sp_fulltext_column 'dbo.articles','comment','add'
exec sp_fulltext_table 'dbo.articles','activate'
exec sp_fulltext_table 'dbo.articles','start_change_tracking'
exec sp_fulltext_table 'dbo. articles','start_background_updateindex'
Unfortunately I tried disabling/enabling full text search in order to try
and fix this problem and now can't re-enable it due to the following error:
Server: Msg 7627, Level 16, State 1, Procedure sp_fulltext_database, Line 61
Full-text catalog in directory 'e:\mssql\ftdata' for clustered server cannot
be created. Only directories on a disk in the cluster group of the server
can be used.
Ian.
"Peter Yang [MSFT]" <petery@.online.microsoft.com> wrote in message
news:z8KjaoOBFHA.2732@.cpmsftngxa10.phx.gbl...
> Hello Ian,
> To understsand the issue better, I'd like to know the exact steps you
> create and delete the full text catalog. What is the exact error message
> you encountered?
> Regards,
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Partner Support
>
> --
> | From: "Ian" <Ixpah@.newsgroup.nospam>
> | Subject: Can't delete full text catalog on clustered sql serer 2000
> | Date: Thu, 27 Jan 2005 10:30:33 -0000
> | Lines: 11
> | X-Priority: 3
> | X-MSMail-Priority: Normal
> | X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
> | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
> | X-RFC2646: Format=Flowed; Original
> | Message-ID: <#rqy8sFBFHA.3588@.TK2MSFTNGP11.phx.gbl>
> | Newsgroups: microsoft.public.sqlserver.programming
> | NNTP-Posting-Host: host81-137-218-140.in-addr.btopenworld.com
> 81.137.218.140
> | Path:
> cpmsftngxa10.phx.gbl!TK2MSFTNGXS01.phx.gbl!cpmsftngxa06.phx.gbl!TK2MSFTNGP
08
> phx.gbl!TK2MSFTNGP11.phx.gbl
> | Xref: cpmsftngxa10.phx.gbl microsoft.public.sqlserver.programming:499844
> | X-Tomcat-NG: microsoft.public.sqlserver.programming
> |
> | Basically SQL Server has allowed me to create a full text catalog on a
> drive
> | which is not part of the cluster's shared resources, and I believe
> doesn't
> | exist either (I not familiar with clustering at all).
> |
> | Now the problem is that it now won't let me remove this full text
> catalog,
> | giving me the error that it can't *create* a full text catalog on a disk
> | which isn't part of the cluster's shared resources. How can I delete it?
> |
> | Ian.
> |
> |
> |
>|||Hi lan,
Thanks for your posting!
Peter Yang is OOF and I am his backup!
From your descriptions, I understood that you would like to create a
full-text index catalog, which is on a disk on which the SQL Server
resource is not dependant. In SQL Server 2000 virtual server instance, you
will have to add the disk as a dependency to the SQL Server resource in the
Cluster Administrator.
Refer to the Knowledge Base article for more information and how to add the
disk as a dependency
INF: Creating Databases or Changing Disk File Locations on a Shared Cluster
Drive on Which SQL Server 2000 was not Originally Installed
http://support.microsoft.com/?id=295732
Thank you for your patience and corporation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a w
to all
Microsoft technology partners in the United States and Canada.
This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/te...erview/40010469
Others: https://partner.microsoft.com/US/te...upportoverview/
If you are outside the United States, please visit our International
Support page:
http://support.microsoft.com/defaul...rnational.aspx.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||I have *already* created a full text catalog on a drive which isn't part of
the cluster and probably doesn't exist either. This is the problem I'm
experiencing: not able to delete it or enable full text search because of
it.
I think I've worked out a way round the problem of re-enabling full text
search for the database by changing the path column in the
sysfulltextcatalogs table to a clustered resource. Hopefully once ft is
re-enabled I can then either delete the catalog or use it as is.
Ian.
"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:BrTuYlRDFHA.3744@.cpmsftngxa10.phx.gbl...
> Hi lan,
> Thanks for your posting!
> Peter Yang is OOF and I am his backup!
> From your descriptions, I understood that you would like to create a
> full-text index catalog, which is on a disk on which the SQL Server
> resource is not dependant. In SQL Server 2000 virtual server instance, you
> will have to add the disk as a dependency to the SQL Server resource in
> the
> Cluster Administrator.
> Refer to the Knowledge Base article for more information and how to add
> the
> disk as a dependency
> INF: Creating Databases or Changing Disk File Locations on a Shared
> Cluster
> Drive on Which SQL Server 2000 was not Originally Installed
> http://support.microsoft.com/?id=295732
> Thank you for your patience and corporation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
=============
> Business-Critical Phone Support (BCPS) provides you with technical phone
> support at no charge during critical LAN outages or "business down"
> situations. This benefit is available 24 hours a day, 7 days a w to all
> Microsoft technology partners in the United States and Canada.
> This and other support options are available here:
> BCPS:
> https://partner.microsoft.com/US/te...erview/40010469
> Others: https://partner.microsoft.com/US/te...upportoverview/
> If you are outside the United States, please visit our International
> Support page:
> http://support.microsoft.com/defaul...rnational.aspx.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
which is not part of the cluster's shared resources, and I believe doesn't
exist either (I not familiar with clustering at all).
Now the problem is that it now won't let me remove this full text catalog,
giving me the error that it can't *create* a full text catalog on a disk
which isn't part of the cluster's shared resources. How can I delete it?
Ian.Ian,
Most un-usual! As by design, you should be only able to create FT Catalogs
on the shard drive in a clustered environment. How did you do this? If it
can be reproduced, it should be filed as a bug. Have you tried the
following:
use <your_database_name>
go
exec sp_fulltext_catalog '<Your_FT_Catalog_Name>','drop'
go
If not, try it. If it fails, please post the error that it returns. If it
does fail, you may have to try:
EXEC sp_fulltext_service 'clean_up'
if this too fails, I have some code I can email you directly code (the code
is not for the faint-of-heart) that can get you out of this "catch-22"
situation.
Thanks,
John
--
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"Ian" <Ixpah@.newsgroup.nospam> wrote in message
news:#rqy8sFBFHA.3588@.TK2MSFTNGP11.phx.gbl...
> Basically SQL Server has allowed me to create a full text catalog on a
drive
> which is not part of the cluster's shared resources, and I believe doesn't
> exist either (I not familiar with clustering at all).
> Now the problem is that it now won't let me remove this full text catalog,
> giving me the error that it can't *create* a full text catalog on a disk
> which isn't part of the cluster's shared resources. How can I delete it?
> Ian.
>|||Hello Ian,
To understsand the issue better, I'd like to know the exact steps you
create and delete the full text catalog. What is the exact error message
you encountered?
Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
| From: "Ian" <Ixpah@.newsgroup.nospam>
| Subject: Can't delete full text catalog on clustered sql serer 2000
| Date: Thu, 27 Jan 2005 10:30:33 -0000
| Lines: 11
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
| X-RFC2646: Format=Flowed; Original
| Message-ID: <#rqy8sFBFHA.3588@.TK2MSFTNGP11.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.programming
| NNTP-Posting-Host: host81-137-218-140.in-addr.btopenworld.com
81.137.218.140
| Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXS01.phx.gbl!cpmsftngxa06.phx.gbl!TK2MSFTNGP08
.phx.gbl!TK2MSFTNGP11.phx.gbl
| Xref: cpmsftngxa10.phx.gbl microsoft.public.sqlserver.programming:499844
| X-Tomcat-NG: microsoft.public.sqlserver.programming
|
| Basically SQL Server has allowed me to create a full text catalog on a
drive
| which is not part of the cluster's shared resources, and I believe
doesn't
| exist either (I not familiar with clustering at all).
|
| Now the problem is that it now won't let me remove this full text
catalog,
| giving me the error that it can't *create* a full text catalog on a disk
| which isn't part of the cluster's shared resources. How can I delete it?
|
| Ian.
|
|
||||I used a script which was very similiar (if not the same) as this:
exec sp_fulltext_database 'enable'
exec sp_fulltext_catalog 'popall_ft','create'
exec sp_fulltext_table 'dbo. articles','create','popall_ft','pk__arti
cles'
exec sp_fulltext_column 'dbo.articles','comment','add'
exec sp_fulltext_table 'dbo.articles','activate'
exec sp_fulltext_table 'dbo.articles','start_change_tracking'
exec sp_fulltext_table 'dbo. articles','start_background_updateindex'
Unfortunately I tried disabling/enabling full text search in order to try
and fix this problem and now can't re-enable it due to the following error:
Server: Msg 7627, Level 16, State 1, Procedure sp_fulltext_database, Line 61
Full-text catalog in directory 'e:\mssql\ftdata' for clustered server cannot
be created. Only directories on a disk in the cluster group of the server
can be used.
Ian.
"Peter Yang [MSFT]" <petery@.online.microsoft.com> wrote in message
news:z8KjaoOBFHA.2732@.cpmsftngxa10.phx.gbl...
> Hello Ian,
> To understsand the issue better, I'd like to know the exact steps you
> create and delete the full text catalog. What is the exact error message
> you encountered?
> Regards,
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Partner Support
>
> --
> | From: "Ian" <Ixpah@.newsgroup.nospam>
> | Subject: Can't delete full text catalog on clustered sql serer 2000
> | Date: Thu, 27 Jan 2005 10:30:33 -0000
> | Lines: 11
> | X-Priority: 3
> | X-MSMail-Priority: Normal
> | X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
> | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
> | X-RFC2646: Format=Flowed; Original
> | Message-ID: <#rqy8sFBFHA.3588@.TK2MSFTNGP11.phx.gbl>
> | Newsgroups: microsoft.public.sqlserver.programming
> | NNTP-Posting-Host: host81-137-218-140.in-addr.btopenworld.com
> 81.137.218.140
> | Path:
> cpmsftngxa10.phx.gbl!TK2MSFTNGXS01.phx.gbl!cpmsftngxa06.phx.gbl!TK2MSFTNGP
08
> phx.gbl!TK2MSFTNGP11.phx.gbl
> | Xref: cpmsftngxa10.phx.gbl microsoft.public.sqlserver.programming:499844
> | X-Tomcat-NG: microsoft.public.sqlserver.programming
> |
> | Basically SQL Server has allowed me to create a full text catalog on a
> drive
> | which is not part of the cluster's shared resources, and I believe
> doesn't
> | exist either (I not familiar with clustering at all).
> |
> | Now the problem is that it now won't let me remove this full text
> catalog,
> | giving me the error that it can't *create* a full text catalog on a disk
> | which isn't part of the cluster's shared resources. How can I delete it?
> |
> | Ian.
> |
> |
> |
>|||Hi lan,
Thanks for your posting!
Peter Yang is OOF and I am his backup!
From your descriptions, I understood that you would like to create a
full-text index catalog, which is on a disk on which the SQL Server
resource is not dependant. In SQL Server 2000 virtual server instance, you
will have to add the disk as a dependency to the SQL Server resource in the
Cluster Administrator.
Refer to the Knowledge Base article for more information and how to add the
disk as a dependency
INF: Creating Databases or Changing Disk File Locations on a Shared Cluster
Drive on Which SQL Server 2000 was not Originally Installed
http://support.microsoft.com/?id=295732
Thank you for your patience and corporation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a w
to allMicrosoft technology partners in the United States and Canada.
This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/te...erview/40010469
Others: https://partner.microsoft.com/US/te...upportoverview/
If you are outside the United States, please visit our International
Support page:
http://support.microsoft.com/defaul...rnational.aspx.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||I have *already* created a full text catalog on a drive which isn't part of
the cluster and probably doesn't exist either. This is the problem I'm
experiencing: not able to delete it or enable full text search because of
it.
I think I've worked out a way round the problem of re-enabling full text
search for the database by changing the path column in the
sysfulltextcatalogs table to a clustered resource. Hopefully once ft is
re-enabled I can then either delete the catalog or use it as is.
Ian.
"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:BrTuYlRDFHA.3744@.cpmsftngxa10.phx.gbl...
> Hi lan,
> Thanks for your posting!
> Peter Yang is OOF and I am his backup!
> From your descriptions, I understood that you would like to create a
> full-text index catalog, which is on a disk on which the SQL Server
> resource is not dependant. In SQL Server 2000 virtual server instance, you
> will have to add the disk as a dependency to the SQL Server resource in
> the
> Cluster Administrator.
> Refer to the Knowledge Base article for more information and how to add
> the
> disk as a dependency
> INF: Creating Databases or Changing Disk File Locations on a Shared
> Cluster
> Drive on Which SQL Server 2000 was not Originally Installed
> http://support.microsoft.com/?id=295732
> Thank you for your patience and corporation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
=============
> Business-Critical Phone Support (BCPS) provides you with technical phone
> support at no charge during critical LAN outages or "business down"
> situations. This benefit is available 24 hours a day, 7 days a w
to all> Microsoft technology partners in the United States and Canada.
> This and other support options are available here:
> BCPS:
> https://partner.microsoft.com/US/te...erview/40010469
> Others: https://partner.microsoft.com/US/te...upportoverview/
> If you are outside the United States, please visit our International
> Support page:
> http://support.microsoft.com/defaul...rnational.aspx.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
Thursday, March 8, 2012
can't delete a full text catalog
Hello
I've defined a full text catalog that indexes several columns from two tables.
Now I want to erase it and it simply don't let me... using the console it
reports that my catalog has been lost and to use sp_fulltext_catalog to
repopulate or rebuild it...
I tryied so and the error was the same...
i need to erase that useless catalog because it don't work anymore and i
need to do another one with the same name...
how can i get it done?!?!
best regards
Jorge Ribeiro
Can you try to right click on your table in EM, and select Full Text Index
Table, and then select edit. Click through the dialogs until you get the new
catalog creation dialog. Create a new catalog.
This will clear some of this class of errors. If this won't work you will
probably have to use some of the full text procedures and possibly manually
remove some rows from the system tables. Post back here and I'll try to
help you further with this.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Jorge Ribeiro" <JorgeRibeiro@.discussions.microsoft.com> wrote in message
news:F60177EB-6333-4755-A035-202EC62FB27F@.microsoft.com...
> Hello
> I've defined a full text catalog that indexes several columns from two
tables.
> Now I want to erase it and it simply don't let me... using the console it
> reports that my catalog has been lost and to use sp_fulltext_catalog to
> repopulate or rebuild it...
> I tryied so and the error was the same...
> i need to erase that useless catalog because it don't work anymore and i
> need to do another one with the same name...
> how can i get it done?!?!
> best regards
> Jorge Ribeiro
|||Hi
I've done what you sujested (create a new catalog) and the result was the
same... the catalog has been lost and so on...
it didn't create a new catalog and the old one still persists
what can I do now?!?!
thanx
Jorge Ribeiro
"Hilary Cotter" wrote:
> Can you try to right click on your table in EM, and select Full Text Index
> Table, and then select edit. Click through the dialogs until you get the new
> catalog creation dialog. Create a new catalog.
> This will clear some of this class of errors. If this won't work you will
> probably have to use some of the full text procedures and possibly manually
> remove some rows from the system tables. Post back here and I'll try to
> help you further with this.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> "Jorge Ribeiro" <JorgeRibeiro@.discussions.microsoft.com> wrote in message
> news:F60177EB-6333-4755-A035-202EC62FB27F@.microsoft.com...
> tables.
>
>
|||drop the catalog using sp_fulltext_catalog 'catalogname', 'drop'
After you have completed doing this, delete the rows from
sysfulltextcatalogs
Then try to build your catalogs again.
Hilary Cotter
Looking for a SQL Server replication book?
Now available for purchase at:
http://www.nwsu.com/0974973602.html
"Jorge Ribeiro" <JorgeRibeiro@.discussions.microsoft.com> wrote in message
news:C159A27C-6C4F-4743-B532-1FF11E754DA4@.microsoft.com...[vbcol=seagreen]
> Hi
> I've done what you sujested (create a new catalog) and the result was the
> same... the catalog has been lost and so on...
> it didn't create a new catalog and the old one still persists
> what can I do now?!?!
> thanx
> Jorge Ribeiro
>
> "Hilary Cotter" wrote:
Index[vbcol=seagreen]
new[vbcol=seagreen]
will[vbcol=seagreen]
manually[vbcol=seagreen]
message[vbcol=seagreen]
it[vbcol=seagreen]
to[vbcol=seagreen]
i[vbcol=seagreen]
|||i've already done that
i've got an error message
Cannot drop full-text catalog 'cat_intranet_teste_paginas' because it
contains a full-text index.
can i still delete the catalog row from sysfulltextcatalogs?!
will it work?!?!
"Hilary Cotter" wrote:
> drop the catalog using sp_fulltext_catalog 'catalogname', 'drop'
> After you have completed doing this, delete the rows from
> sysfulltextcatalogs
> Then try to build your catalogs again.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> Now available for purchase at:
> http://www.nwsu.com/0974973602.html
>
> "Jorge Ribeiro" <JorgeRibeiro@.discussions.microsoft.com> wrote in message
> news:C159A27C-6C4F-4743-B532-1FF11E754DA4@.microsoft.com...
> Index
> new
> will
> manually
> message
> it
> to
> i
>
>
|||back up your database. Then delete the rows.
Then try to create another catalog, and go back and edit the tables to move
them to the new catalog.
"Jorge Ribeiro" <JorgeRibeiro@.discussions.microsoft.com> wrote in message
news:096B13D9-C590-4B33-A2BF-C076FED64EDC@.microsoft.com...[vbcol=seagreen]
> i've already done that
> i've got an error message
> Cannot drop full-text catalog 'cat_intranet_teste_paginas' because it
> contains a full-text index.
> can i still delete the catalog row from sysfulltextcatalogs?!
> will it work?!?!
> "Hilary Cotter" wrote:
message[vbcol=seagreen]
the[vbcol=seagreen]
the[vbcol=seagreen]
try to[vbcol=seagreen]
two[vbcol=seagreen]
console[vbcol=seagreen]
sp_fulltext_catalog[vbcol=seagreen]
and[vbcol=seagreen]
I've defined a full text catalog that indexes several columns from two tables.
Now I want to erase it and it simply don't let me... using the console it
reports that my catalog has been lost and to use sp_fulltext_catalog to
repopulate or rebuild it...
I tryied so and the error was the same...
i need to erase that useless catalog because it don't work anymore and i
need to do another one with the same name...
how can i get it done?!?!
best regards
Jorge Ribeiro
Can you try to right click on your table in EM, and select Full Text Index
Table, and then select edit. Click through the dialogs until you get the new
catalog creation dialog. Create a new catalog.
This will clear some of this class of errors. If this won't work you will
probably have to use some of the full text procedures and possibly manually
remove some rows from the system tables. Post back here and I'll try to
help you further with this.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Jorge Ribeiro" <JorgeRibeiro@.discussions.microsoft.com> wrote in message
news:F60177EB-6333-4755-A035-202EC62FB27F@.microsoft.com...
> Hello
> I've defined a full text catalog that indexes several columns from two
tables.
> Now I want to erase it and it simply don't let me... using the console it
> reports that my catalog has been lost and to use sp_fulltext_catalog to
> repopulate or rebuild it...
> I tryied so and the error was the same...
> i need to erase that useless catalog because it don't work anymore and i
> need to do another one with the same name...
> how can i get it done?!?!
> best regards
> Jorge Ribeiro
|||Hi
I've done what you sujested (create a new catalog) and the result was the
same... the catalog has been lost and so on...
it didn't create a new catalog and the old one still persists
what can I do now?!?!
thanx
Jorge Ribeiro
"Hilary Cotter" wrote:
> Can you try to right click on your table in EM, and select Full Text Index
> Table, and then select edit. Click through the dialogs until you get the new
> catalog creation dialog. Create a new catalog.
> This will clear some of this class of errors. If this won't work you will
> probably have to use some of the full text procedures and possibly manually
> remove some rows from the system tables. Post back here and I'll try to
> help you further with this.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> "Jorge Ribeiro" <JorgeRibeiro@.discussions.microsoft.com> wrote in message
> news:F60177EB-6333-4755-A035-202EC62FB27F@.microsoft.com...
> tables.
>
>
|||drop the catalog using sp_fulltext_catalog 'catalogname', 'drop'
After you have completed doing this, delete the rows from
sysfulltextcatalogs
Then try to build your catalogs again.
Hilary Cotter
Looking for a SQL Server replication book?
Now available for purchase at:
http://www.nwsu.com/0974973602.html
"Jorge Ribeiro" <JorgeRibeiro@.discussions.microsoft.com> wrote in message
news:C159A27C-6C4F-4743-B532-1FF11E754DA4@.microsoft.com...[vbcol=seagreen]
> Hi
> I've done what you sujested (create a new catalog) and the result was the
> same... the catalog has been lost and so on...
> it didn't create a new catalog and the old one still persists
> what can I do now?!?!
> thanx
> Jorge Ribeiro
>
> "Hilary Cotter" wrote:
Index[vbcol=seagreen]
new[vbcol=seagreen]
will[vbcol=seagreen]
manually[vbcol=seagreen]
message[vbcol=seagreen]
it[vbcol=seagreen]
to[vbcol=seagreen]
i[vbcol=seagreen]
|||i've already done that
i've got an error message
Cannot drop full-text catalog 'cat_intranet_teste_paginas' because it
contains a full-text index.
can i still delete the catalog row from sysfulltextcatalogs?!
will it work?!?!
"Hilary Cotter" wrote:
> drop the catalog using sp_fulltext_catalog 'catalogname', 'drop'
> After you have completed doing this, delete the rows from
> sysfulltextcatalogs
> Then try to build your catalogs again.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> Now available for purchase at:
> http://www.nwsu.com/0974973602.html
>
> "Jorge Ribeiro" <JorgeRibeiro@.discussions.microsoft.com> wrote in message
> news:C159A27C-6C4F-4743-B532-1FF11E754DA4@.microsoft.com...
> Index
> new
> will
> manually
> message
> it
> to
> i
>
>
|||back up your database. Then delete the rows.
Then try to create another catalog, and go back and edit the tables to move
them to the new catalog.
"Jorge Ribeiro" <JorgeRibeiro@.discussions.microsoft.com> wrote in message
news:096B13D9-C590-4B33-A2BF-C076FED64EDC@.microsoft.com...[vbcol=seagreen]
> i've already done that
> i've got an error message
> Cannot drop full-text catalog 'cat_intranet_teste_paginas' because it
> contains a full-text index.
> can i still delete the catalog row from sysfulltextcatalogs?!
> will it work?!?!
> "Hilary Cotter" wrote:
message[vbcol=seagreen]
the[vbcol=seagreen]
the[vbcol=seagreen]
try to[vbcol=seagreen]
two[vbcol=seagreen]
console[vbcol=seagreen]
sp_fulltext_catalog[vbcol=seagreen]
and[vbcol=seagreen]
Subscribe to:
Posts (Atom)