|
Hi,
I am facing some problems related to french characters. One of the character "₣" is not supported by sql server 2005. rest of the french characters is suppoeted by sql server 2005.
When ever i tried to insert data or run a select query it returns as a question mark "?".
Full text search is provided on table for search functionality.
Select doc_id,1 from DocumentMaster Where 1=1
AND (CONTAINS(Document_Filename, '"*Œ*"') OR CONTAINS(Document_Filename_French, '"*Œ*"'))
AND (CONTAINS(Document_Filename, '"*œ*"') OR CONTAINS(Document_Filename_French, '"*œ*"'))
AND (CONTAINS(Document_Filename, '"*€*"') OR CONTAINS(Document_Filename_French, '"*€*"'))
AND (CONTAINS(Document_Filename, '"*?*"') OR CONTAINS(Document_Filename_French, '"*?*"'))
i have read in couple of the site that the data type of the colum should be nvarchar or ntext for french characters to support. I even that. but then also it is not supporting the "₣" french character. Rest french character it is supporting.
please suggest any solution.
Regards,
Pranav Dave
|
|
|
|
|
Hi,
I don;t know the F-like character your message shows, and which you call a "french character".
What is its name?
Can you show us some words containing it?
do you know its unicode number?
are there things you can do with it successfully?
|
|
|
|
|
Luc Pattyn wrote: What is its name?
"French Franc", a deprecated monetary unit
Luc Pattyn wrote: are there things you can do with it successfully?
Compare beer-prices with aged Frenchmen?
I are Troll 
|
|
|
|
|
Eddy Vluggen wrote: "French Franc"
really? doesn't look anything like the symbol here[^], which is Unicode U+20A3 and should pose no problem at all.
|
|
|
|
|
Luc Pattyn wrote: really?
Yup, they're the same
Well, ehr.. the example doesn't look like that picture, but like the font that it shows below. Scroll down on that link that you sent me and the same symbol should be there in the table "Java Data". It might be that your browser is (temporarily?) set to something different than UTF-8? Or you're using a different font-set, that could also explain it's different appearance.
It shouldn't pose a problem like you said. Then again, it doesn't behave like the 'other' special characters. If I omit the N-prefix in the INSERT statement, then it will indeed put a questionmark in there. Not so for that crazy 'Œ' symbol.
I are Troll
|
|
|
|
|
yup.
the 'Œ' character (and eszet 'ß' and most accented characters used in Western languages) is part of code page 1252, whereas the French Franc and most other (possibly obsolete) monetary symbols are not.
|
|
|
|
|
Luc Pattyn wrote: the 'Œ' character (and eszet 'ß' and most accented characters used in Western languages) is part of code page 1252, whereas the French Franc and most other (possibly obsolete) monetary symbols are not.
Not even the need for a CHCP 1252, since it gets stuffed into a unicode field.
Question seems answered though, I'll wait for the repost 
I are Troll
|
|
|
|
|
Try this one;
DECLARE @TestTable AS TABLE (
TestCol NVARCHAR(2) COLLATE Latin1_General_BIN
)
INSERT INTO @TestTable VALUES (N'₣')
INSERT INTO @TestTable VALUES (N'Œ')
SELECT * FROM @TestTableCheck whether the column that you're storing data into is really accepting unicode-text, make sure the collation is set correctly, and check whether you're passing unicode or ascii as a parameter
--edit--
pranavcool wrote: i have read in couple of the site that the data type of the colum should be nvarchar or ntext for french characters to support.
That is correct. Unfortunatly, there's other places where things can go wrong. Even the value of the string that you're inspecting in the debugger is displayed using a font. The task would be to verify that SQL Server works correctly, and then to find the source of the error.
pranavcool wrote: When ever i tried to insert data or run a select query it returns as a question mark "?".
I'm guessing that this is due to the Management Studio, since you're probably not on DOS using isql. Try a small console-application, you'll see that SQL Server correctly saves and retrieves the character. That is, using the standard SqlCommand and SqlConnection.
You're not displaying the result/seeing the '?' in a browser by any chance?
Are you using MONO? Or an ODBC-driver?
I are Troll
modified on Monday, December 28, 2009 12:34 PM
|
|
|
|
|
Hi,
There was a small problem with our app where it allowed users to enter white-space only characters in one of the data fields. So now I'm trying to clean this up.
A colleague of mine sent me this unusual SQL query to find the whitespaces. The script looks like this:
SELECT tblId, ASCII(tblField1) AS 'ASCII Code', tblField1
FROM Table1
WHERE ASCII(LEFT(tblField1,1)) = 32
This query returned 40 rows.
Now, when I try either of the following:
SELECT tblId, ASCII(tblField1) AS 'ASCII Code', tblField1
FROM Table1
WHERE tblField1 = ' ' -- with a single whitespace
or
SELECT tblId, ASCII(tblField1) AS 'ASCII Code', tblField1
FROM Table1
WHERE tblField1 = '' -- empty string
The above 2 queries return 200,000+ rows.
Why is this so?
Rafferty
modified on Sunday, December 27, 2009 10:23 PM
|
|
|
|
|
Hi,
the first query selects all rows where tblField1 holds a string with a first character equal to a space.
the other two require the entire tblField1 to equal something that probably gets trimmed down to an empty string, hence returning all rows with that field empty. That obviously is quite a different query.
IMO the more elegant query would use
...WHERE tblField1 LIKE ' %'
using a single space and the wildcard character %.
|
|
|
|
|
So the = operator does not check for exact string equality... I knew before that = is case insensitive but to think that it also trims the string!
Is LIKE the more preferable conditional operator then?
Is there a performance difference between = and LIKE?
Say for example WHERE tblField1 = 'something' vs. WHERE tblField1 LIKE 'something'
Rafferty
|
|
|
|
|
1.
I'm not sure, I think it stripped the spaces, got an empty constant, and returned all records.
2.
LIKE makes most sense when it contains a wildcard, and = does not accept wildcards; without wildcards databases can take big advantage of indexing, with wildcards they can't, so most often LIKE is much slower.
|
|
|
|
|
So using LIKE will not use the database indexing even if there are no wildcards in the passed string?
Rafferty
|
|
|
|
|
I don't know what goes on inside a specific database, that is up to the guys implementing all of it; it may or may not be documented, and it might depend on circumstances, such as available memory and disk space. The simple rule is: use LIKE if you need a wildcard, and expect it to be slower.
If you need more, look for the documentation and perform your own experiments (on sufficiently large data sets).
|
|
|
|
|
hm... maybe I'll do some experimenting when I find the time.
Thanks for your help!
Rafferty
|
|
|
|
|
You're welcome.
|
|
|
|
|
Microsoft SQLServer will use indexes (if available) when you use the like statement without wildcards. Even if you do use wildcards, SQL will use indexes if possible. if you compare to a string witch starts with a wildcard, SQL will NOT use indexes.
Wout Louwers
|
|
|
|
|
Wow this is very useful!
Thanks a lot! 
Rafferty
|
|
|
|
|
Something is wrong...in ansi sql databases:
The rows returned in the first query will be equal to or greater than the second.
All of the rows in the second will be included in the first.
The rows returned in the third query will never be in the first or second.
Need to figure this out before thinking about indexes and wildcards.
I would change the second qry as such: WHERE tblField1 = char(32)
just to be sure because-
select ascii(' ') --this equals 9
select ascii(' ') --this equals 32
Create and put data in your Table1 and test if you are not convinced.
|
|
|
|
|
Hi, I am trying to construct a query statement that allows me to retrieve what’s known as “Bullish Divergence” in stock investing signals. It occurs when stock price reaches to a new high level, surpassing a previous price peak, while a certain strength indicator on the same date fails to surpass the strength indicator of the previous peak. This would suggest the stock price is over-valued.
The logic is to first find all the stocks whose prices have reached new highs on 11/24/2009 within the past 10 days, and if their RSI figures fail to be greater than the RSI figures of the previous peaks, then we have a bullish divergence.
I currently have the following query statement, which returns an error message saying “Subquery returned more than 1 value and cannot be used when subquery follows <, >, >=, <=, =”. Could anyone please help me with this?  I would be very thankful as I’ve spent hours trying to get it to work. Thanks!!
SELECT Date, Ticker, Price, RSI
FROM Table
WHERE (Price =
(SELECT MAX(Price) AS Expr1
FROM Table AS t2
WHERE (Table.Ticker = Ticker) AND (Date BETWEEN DATEADD(day, - 10, '11/24/2009')
AND '11/24/2009'))) AND (Date = '11/24/2009') AND
(RSI <
(SELECT RSI
FROM Table AS t3
WHERE (Price =
(SELECT MAX(Price) AS Expr1
FROM Table AS t4
WHERE (t3.Ticker = Ticker) AND (Date BETWEEN DATEADD(day,
-10, '11/23/2009') AND '11/23/2009')))))
modified on Tuesday, December 29, 2009 8:38 PM
|
|
|
|
|
You are trying to get value with subquery which return more then one row and that is why you get error,but to solve this try to use TOP 1 or post your query to see where is problem.
I Love T-SQL
"Don't torture yourself,let the life to do it for you."
If my post helps you kindly save my time by voting my post.
www.aktualiteti.com
|
|
|
|
|
Unfortunately I was not able to post my query without failing to submit a new thread/post, not sure why. That's why I've post my query in another forum and I've put a link in the first post. Could you please help me out? Thanks!!
|
|
|
|
|
Can anyone please help me? I still can't figure out how to write this....
|
|
|
|
|
Hi
I have problem re-installing SQL 2008 Express. The problem I am getting is even though I can double click on the icon, but when I check the install, I see that there is an error message on the register keys. The error message says that a "prior installations register keys cannot be modified, please check installation to fix error". Unfortunately, I cannot find on MSDN's website on where to find the appropriate fix. Yes, I did have a prior installation, but I removed it Add and Remove Programs, thinking this would give me a clean removal in order to fix another problem.
Can anyone, please advise me on this problem in order that I may install SQL 2008 Express?
Thanks
|
|
|
|
|
I ran into the problem trying to install it the first time; apparently it didn't like having a preious version on the machine (2005). I tried several times a week for a few months to solve it, but never found a solution. After removing the 2005 version, it started whining about corrupted performance counters. And though there is a link to a manual (and extremely tedious) method of cleaning this up for the 2005 version, no such article existed at the time that had a procedure that works for the 2008 version. Hopefully that has been corrected by now, but I doubt it.
I eventually gave up trying, installed it on my server instead, and with help from several kind CPians managed to make the server installation visible to the client.
Another problem that doesn't sound like it applies to this situation exactly, but may bite you later, is that a number of users have found it impossible to install SS 2008 after installing Visual Studio. The reported fix for that was to install the SQL Server first, then install Visual Studio.
If you do find a solution, please write up a procedure and publish it as an article. I'm sure a lot of CP members will find it useful!
"A Journey of a Thousand Rest Stops Begins with a Single Movement"
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
