Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Administration (2000)
 services

Author  Topic 

brendalisalowe
Constraint Violating Yak Guru

269 Posts

Posted - 2004-12-28 : 13:54:43
Does anyone know how to get to the picture on the third paragraph on this website?:

http://www.databasejournal.com/features/mssql/article.php/3441981

Thanks!

Brenda

If it weren't for you guys, where would I be?

nr
SQLTeam MVY

12543 Posts

Posted - 2004-12-28 : 13:57:31
insert the SQL Server media, and select "Upgrade, Add or Remove Components." Click next for "Add Components."

It means run setup.

==========================================
Cursors are useful if you don't know sql.
DTS can be used in a similar way.
Beer is not cold and it isn't fizzy.
Go to Top of Page

brendalisalowe
Constraint Violating Yak Guru

269 Posts

Posted - 2004-12-28 : 13:59:31
Where is this?:

"insert the SQL Server media"

Brenda

If it weren't for you guys, where would I be?
Go to Top of Page

nr
SQLTeam MVY

12543 Posts

Posted - 2004-12-28 : 14:05:14
It's the dvd or whatever that you installed sql server from.

==========================================
Cursors are useful if you don't know sql.
DTS can be used in a similar way.
Beer is not cold and it isn't fizzy.
Go to Top of Page

brendalisalowe
Constraint Violating Yak Guru

269 Posts

Posted - 2004-12-28 : 14:09:14
I don't want to run the setup again. Basically I am trying to figure out how to do full-text search. When I try to set up full-text search, it tells me this:

The selected table has no unique single column index on a column that does not allow NULLS.

I have a PK in the table. Do I have to have another column that doesn't allow NULLS? If so, why?


Brenda

If it weren't for you guys, where would I be?
Go to Top of Page

nr
SQLTeam MVY

12543 Posts

Posted - 2004-12-28 : 14:13:35
Sounds like you have a compound PK.
This needs a single column. If you don't have one you can add a timestamp.

==========================================
Cursors are useful if you don't know sql.
DTS can be used in a similar way.
Beer is not cold and it isn't fizzy.
Go to Top of Page

brendalisalowe
Constraint Violating Yak Guru

269 Posts

Posted - 2004-12-28 : 14:29:14
So as long as I have a column that doesn't allow NULLS, it should work? It still doesn't for me. Any ideas?

Brenda

If it weren't for you guys, where would I be?
Go to Top of Page

nr
SQLTeam MVY

12543 Posts

Posted - 2004-12-28 : 14:37:59
It also needs to have a unique index on it.

>> The selected table has no unique single column index on a column that does not allow NULLS.

==========================================
Cursors are useful if you don't know sql.
DTS can be used in a similar way.
Beer is not cold and it isn't fizzy.
Go to Top of Page

brendalisalowe
Constraint Violating Yak Guru

269 Posts

Posted - 2004-12-28 : 14:55:45
So do something like this?

CREATE UNIQUE INDEX full_text_index
ON tblFeePaid (notes)


Brenda

If it weren't for you guys, where would I be?
Go to Top of Page

nr
SQLTeam MVY

12543 Posts

Posted - 2004-12-28 : 15:01:35
umm - a column called notes usually wouldn't be unique (or not allow nulls) but...

==========================================
Cursors are useful if you don't know sql.
DTS can be used in a similar way.
Beer is not cold and it isn't fizzy.
Go to Top of Page

brendalisalowe
Constraint Violating Yak Guru

269 Posts

Posted - 2004-12-28 : 15:05:15
So apply a unique index to the 2 columns I have as PK?

Brenda

If it weren't for you guys, where would I be?
Go to Top of Page

nr
SQLTeam MVY

12543 Posts

Posted - 2004-12-28 : 15:24:42
>> The selected table has no unique single column index on a column that does not allow NULLS.
>> Sounds like you have a compound PK.
>> This needs a single column. If you don't have one you can add a timestamp.

so no.
And the pk is always supported by an index so it already has one.

==========================================
Cursors are useful if you don't know sql.
DTS can be used in a similar way.
Beer is not cold and it isn't fizzy.
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2004-12-28 : 15:56:55
Brenda,

How about posting the CREATE TABLE statement for your table?

Tara
Go to Top of Page

brendalisalowe
Constraint Violating Yak Guru

269 Posts

Posted - 2004-12-28 : 16:04:20
I've decided to just use a LIKE statement for a query, instead of the full-text search. I think with having 2 columns as the PK, it will be easier. Thanks anyway!

Brenda

If it weren't for you guys, where would I be?
Go to Top of Page

derrickleggett
Pointy Haired Yak DBA

4184 Posts

Posted - 2004-12-28 : 17:44:47
Brenda, that could be extremely slower if the table gets to any kind of a decent size and has a lot of text. Struggle through this one and learn from it. Can you post the CREATE statement?

MeanOldDBA
derrickleggett@hotmail.com

When life gives you a lemon, fire the DBA.
Go to Top of Page

nr
SQLTeam MVY

12543 Posts

Posted - 2004-12-28 : 18:00:16
a like statement and full text search do different things.

I think if you add the timestamp or an identity and index it you won't have a problem.

==========================================
Cursors are useful if you don't know sql.
DTS can be used in a similar way.
Beer is not cold and it isn't fizzy.
Go to Top of Page

brendalisalowe
Constraint Violating Yak Guru

269 Posts

Posted - 2004-12-29 : 11:29:12
Here ya go:

CREATE TABLE [tblCapRec] (
[CaseNumber] [char] (10) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL ,
[PartNumber] [smallint] NOT NULL ,
[Status] [smallint] NULL ,
[LastName] [varchar] (50) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[FirstName] [varchar] (50) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[Others] [varchar] (50) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[SSN] [char] (11) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[OtherSSN] [char] (11) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[OtherNotes] [text] COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[Email] [varchar] (50) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[InGDB] [bit] NULL ,
[DocsOrdered] [bit] NULL ,
[DocsHere] [bit] NULL ,
[AppHere] [bit] NULL ,
[Ubum] [bit] NULL ,
[Suspended] [bit] NULL ,
[Trace] [bit] NULL ,
[SentToHUD] [bit] NULL ,
[SpanishCase] [bit] NULL ,
[MailAddress] [varchar] (60) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[MailAddress2] [varchar] (60) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[MailCity] [varchar] (50) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[MailState] [char] (2) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[MailZipCode] [varchar] (10) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[CareOf] [varchar] (60) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[HomePhone] [varchar] (14) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[WorkPhone] [varchar] (14) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[CellPhone] [varchar] (14) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[FaxPhone] [varchar] (14) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[OtherPhone] [varchar] (14) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[SpousePhone] [varchar] (14) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[SpouseWork] [varchar] (14) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[SpouseCell] [varchar] (14) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[SpouseOther] [varchar] (14) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[PropAddress] [varchar] (60) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[PropCity] [varchar] (50) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[PropState] [char] (2) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[PropZipCode] [varchar] (10) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[Updated] [datetime] NULL ,
[MailKey] [smallint] NULL ,
[MailedFirst] [datetime] NULL ,
[FirstRcvd] [datetime] NULL ,
[AppSent] [datetime] NULL ,
[AppSent2] [datetime] NULL ,
[AppSent3] [datetime] NULL ,
[AppSent4] [datetime] NULL ,
[AppSent5] [datetime] NULL ,
[OrderedDocs] [datetime] NULL ,
[AppRcvd] [datetime] NULL ,
[Paid] [datetime] NULL ,
[FirstBillSent] [datetime] NULL ,
[SecondBillSent] [datetime] NULL ,
[FinalBillSent] [datetime] NULL ,
[FeePaid] [datetime] NULL ,
[MortgageAmt] [float] NULL ,
[PaidUpFront] [float] NULL ,
[EndorseDate] [datetime] NULL ,
[Term] [int] NULL ,
[MatureDate] [datetime] NULL ,
[EncumDate] [datetime] NULL ,
[HoldingMor] [int] NULL ,
[ServingMor] [int] NULL ,
[RcvdFromOld] [bit] NULL ,
[RcvdFromRegular] [bit] NULL ,
[RcvdFromRtn] [bit] NULL ,
[RcvdFrom2s] [bit] NULL ,
[RcvdText] [text] COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[RefundAmt] [float] NULL ,
[RateCharged] [float] NULL ,
[FeeAmount] [float] NULL ,
[AfterFee] [float] NULL ,
[AmtPaid] [float] NULL ,
[LateFees] [float] NULL ,
[RemainingDue] [float] NULL ,
[Contract] [image] NULL ,
[TFC] [image] NULL ,
[Application] [image] NULL ,
[Docs] [image] NULL ,
[Other] [image] NULL ,
[Notes] [text] COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[Sold] [bit] NULL ,
[Refinanced] [bit] NULL ,
[Foreclosed] [bit] NULL ,
[ApproxDate] [datetime] NULL ,
[DiffName] [varchar] (50) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[OtherPeople] [varchar] (50) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[PropCounty] [varchar] (50) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[DocsOther] [varchar] (100) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[TraceDate] [datetime] NULL ,
[Operator] [varchar] (50) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[Cashed] [bit] NULL ,
[Returned] [bit] NULL ,
[NoInfo] [bit] NULL ,
[DateSusp] [datetime] NULL ,
[ReasonSusp] [varchar] (100) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[Certifier] [varchar] (50) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[HaveSuspLtrYes] [bit] NULL ,
[HaveSuspLtrNo] [bit] NULL ,
[RegularBilling] [bit] NULL ,
[Final] [bit] NULL ,
[TSI] [bit] NULL ,
[Credit] [bit] NULL ,
[PaymentNotes] [varchar] (200) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[PaymentDue] [datetime] NULL ,
CONSTRAINT [PK_tblCapRec] PRIMARY KEY CLUSTERED
(
[CaseNumber],
[PartNumber]
) ON [PRIMARY]
) ON [PRIMARY] TEXTIMAGE_ON [PRIMARY]
GO


Sorry it is so huge. Where do I go from here? Thanks for all your help!

Brenda

If it weren't for you guys, where would I be?
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2004-12-29 : 12:06:48
I'm confused. You posted the DDL for tblCapRec, but above you've got this:

CREATE UNIQUE INDEX full_text_index
ON tblFeePaid (notes)


So which table are you doing this for?

And have you considered not prefixing your table names with tbl? That's the number one no no in database naming standards.

Tara
Go to Top of Page

brendalisalowe
Constraint Violating Yak Guru

269 Posts

Posted - 2004-12-29 : 12:10:14
Why is prefixing your table names with tbl a no no?

I need to do it for tblCapRec and tblFeePaid, but they have the same format.

Brenda

If it weren't for you guys, where would I be?
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2004-12-29 : 12:14:01
Which columns do you want to use LIKE for?

Tara
Go to Top of Page

brendalisalowe
Constraint Violating Yak Guru

269 Posts

Posted - 2004-12-29 : 12:15:22
The NOTES column. Thanks Tara...again!

Brenda

If it weren't for you guys, where would I be?
Go to Top of Page
    Next Page

- Advertisement -