|
hi,im having trouble for acsending order of my own language. Do i have to write a program for this ascending order or is it possible we can use query builder to create this sorting?
here my language letters in A to F.
?
?
?
?
?
?
it would be great if you can give me an idea too.
so much of happy ending...
|
|
|
|
|
Please rephrase your question. It makes no sense.
"The clue train passed his station without stopping." - John Simmons / outlaw programmer
"Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon
|
|
|
|
|
IT SEEMS I MADE NO SENSE PHRASES IN RECENTLY POST. MY WORD IS PLEASE MAKE IT SENSE AS MUCH AS POSSIBLE. TIMES AND TIDES WAIT FOR NO SOUL .
im trying to make database application in our language, name was dhivehi, which supports in XP too. and its totally different from any other languages which has to be written in right to left. i was having trouble with sorting ascending order of this language letters in MICROSOFT SQL 2005.
my question is:
- Do i have to write a separate program or
- in SQL Query builder I can do sorting order?
anyone help me with an best and top level suggestion would be great indeed.
so much of happy ending...
|
|
|
|
|
I think you are asking about changing the collation.
See this link here:
Clickety[^]
Regards
Guy
You always pass failure on the way to success.
|
|
|
|
|
Not sure if this should go under OS/Admin board or not but this seems to be the closest...
Anyway, I found out that the following is taking up 40MB... not a lot of space but ...
L:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Template Data\mssqlsystemresource.mdf
Is that normal? What's this?
Thanks
devy
|
|
|
|
|
My handy copy of the book with possibly the longest name all year, "Inside Microsoft SQL Server 2005: The Storage Engine" says that the mssqlsystemresource database is used to store executable system objects. It was created to allow very fast and safe upgrades simply by being replaced. Older versions of SQL Server had to run scripts during upgrades to modify the contents of system stored procedures in the master database.
If you want to see inside it, stop SQL Server, make a copy of the file and log file, then attach the copy using a new name.
See also "Resource Database" in Books Online/MSDN Library.
DoEvents: Generating unexpected recursion since 1991
|
|
|
|
|
I've never run into a case or have seen this happen, but does anyone know what will happen if an auto number reaches the limit of INTEGER?
|
|
|
|
|
If you're dealing with Microsoft Access, then the range for the autonumber is between
-2,147,483,648 and 2,147,483,647
So, it's highly unlikely you'll exhaust the autonumber field. One calculation I saw elsewhere, that I verified myself, shows that even if you added a record every second of every day of every year, it would take a little over 68 years to go from 1 to 2,147,483,647 in the autonumber field.
If you do manage to exhaust the field (due to some program error that starts adding fields uncontrollably), it probably will wrap around and start at -2,147,483,648.
I hope this helps.
|
|
|
|
|
Hi evrybuddy
my boss says that TinyInt is better in performance that Bit when u need to use a boolean field. well I dont agree to that,
I've been trying to get some info on this over google but couldnt find any . I dont have the SQL2005 books online at the moment. Can any one plz comment on that. Please give some technical comment on this.
Many thanks!
Rocky
You can't climb up a ladder with your hands in your pockets.
|
|
|
|
|
Rocky# wrote: dont have the SQL2005 books online at the moment.
The clue's in the name - SQL Books Online. If you can post a message on CodeProject, you can get to SQL Books Online.
Anyway, your boss sounds like an idiot. Bit fields have a specific purpose - to store true/false values. The Tinyintt data type stores values between 0 and 255. If you were to use tinyint instead of bit, you would have to add constraints to ensure data entry was constrained to 0 and 1.
Paul Marfleet
"No, his mind is not for rent
To any God or government"
Tom Sawyer - Rush
|
|
|
|
|
Agreed.
Don't try and second-guess your subsystems. If you are storing a boolean value then use a boolean data type.
If for some strange reason, the tinyint type is faster (I strongly doubt this - its probably fairytales from the "stored procs are faster" crowd) it will be so marginal it's nothing to worry about. Also you won't be guaranteed that you have picked the best data type for the job if MS changes anything in SQL server.
Seriously. Don't second-guess your subsystems. Don't second-guess the compiler. In both cases the people that wrote them are a hell of a lot smarter and better engineers than your boss. 
|
|
|
|
|
Mark Churchill wrote: Don't try and second-guess your subsystems. If you are storing a boolean value then use a boolean data type.
Mark Churchill wrote: the people that wrote them are a hell of a lot smarter and better engineers than your boss.
yea I agree with you 100%
Thanks!
Rocky
You can't climb up a ladder with your hands in your pockets.
|
|
|
|
|
pmarfleet wrote: Anyway, your boss sounds like an idiot
ahhh I was thinking abt showing this conversation to my boss... 
pmarfleet wrote: If you were to use tinyint instead of bit, you would have to add constraints to ensure data entry was constrained to 0 and 1.
that's exactly what I was thinking and offcourse it can't imporve efficiency if you have constraints on...
Many thanks for ur response. Cheers...
Rocky
You can't climb up a ladder with your hands in your pockets.
|
|
|
|
|
The server will have to do a tiny, tiny bit more work to isolate the bit value from the byte it's stored in, but this is just a mask and shift which the processor will have no trouble with, a couple of cycles probably at most. The time taken to do this will be absolutely dwarfed by the time necessary to pull the data from main memory into the processor's cache.
Bit columns have the disadvantage that they can't be included in an index, but generally they are not very selective (having only two values) and would make poor indexes anyway; even if you could build it, the query optimizer would probably not use it.
DoEvents: Generating unexpected recursion since 1991
|
|
|
|
|
I have some software that relies on an MS Access database, both to supply the parameters for various tests and to store the results of those tests. This software is rapidly undergoing revision, however, and each new revision often has a change in the defintion of the database that is supplied with the software.
For current customers, I want to be able to supply the update without losing any of their existing data. Typically, I do not delete fields from tables, or tables from the database (nor do I change names of fields or tables), so all changes are additions, necessary additions as the scope of the program changes.
Now, I can "hard code" in the creation of tables or addition of fields to each new revision, but I'd rather have some automated method of creating tables and adding fields, as needed. Right now, I can detect and respond to a new version of the software, but I'm seeking the most efficient response to the version change. Here is my idea, along with some questions.
1) Get number of tables in newer version of database and compare to previous version-add tables as needed
Is there a SQL command that will return the data table count?
2) Scan through each table to detect if there are any changes in the table definition for each table...add fields, as needed
Any suggestions would be appreciated.
|
|
|
|
|
Hi
Please provide a solution for this issue 
My Report consists of a matrix and table . I Kept the matrix inside the table because i need to calculate subgroups total as well as Grand Total using the group i provided inside the table . The issue when i tried to render the report to Excel it shows "Data Regions within table/matrix cells are ignored." I dont know how to solve it . When i google it . It says that its a Microsoft SSRS limitation . Anyway i could solve it any help will be appreciated
|
|
|
|
|
i m also getting same error, any idea? 
|
|
|
|
|
|
SreejithAchutan wrote: return dbtObj.GetColumnValue(sqlstatement, "UnitId").ToString();
SreejithAchutan wrote: if the user login had no unitid thn exception in sql is seen.How i overcome it
Look at your logic. What happens if GetColumnValue returns null? What does ToString() have to operate on?
You have to handle the case that GetColumnValue() may return null and not attempt to perform a ToString() operation on it.
Also your SQL prone to attack. You have not defended yourself against SQL Injection Attacks. Please read SQL Injection Attacks and Tips on How to Prevent Them[^]
SreejithAchutan wrote: I want it urgently.
Finally, this irritates people. Do not say that you want an answer urgently. I don't care if it is true, it makes you look selfish that you demand attention before others. If it really is urgent then you will be willing to pay for support and since this is a free volunteer service you will get help when people have time to help you.
|
|
|
|
|
ToString() is to convert the retrieved column into string...In getcolumn value null condition is checking but an exception of object reference is not set is returned.How i overcome it...
|
|
|
|
|
First, don't delete your original question - That is considered extremely rude.
SreejithAchutan wrote: ToString() is to convert the retrieved column into string...In getcolumn value null condition is checking but an exception of object reference is not set is returned.How i overcome it...
I know what ToString() does! Or rather I know what you think it does.
You may check in GetColumn() if the column is null - but what do you do with it then? Do you just return null back? In which case, what does ToString() have to work with?
How do you overcome it? Perhaps you need to check for null values in more than one place? Or you need to do something different when you find a null value the first time. As you have not posted the code for GetColumn() I can't tell you what to do. I can only suggest things for you to look at with the hope that you can figure it out for yourself.
|
|
|
|
|
if execute the following query
Select * from table1 where table1id in('100,101,102')
getting error....
Conversion failed when converting the varchar value '100,101,102' to data type int.
anybody tell me solution for this..
thanks
Ramana
|
|
|
|
|
Ramana. G.V wrote: table1id in('100,101,102')
why to enclose search expression in quotations
hope table1id column in the table is numeric
remove quotations and use
Select * from table1 where table1id in(100, 101, 102)
Regards
KP
|
|
|
|
|
if run like this...
declare @x varchar(100)
set @x = '100,101,102'
Select * from table1 where table1idin(@x)
getting that error.
how can i cast to int?
Ramana
|
|
|
|
|
Why bother using the @x variable at all?
If you are doing this by trying to pass the string as a parameter to the stored procedure, i'm afraid this won't work in quite this way.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
