|
Hi
I am using MySql, querying it from VB.Net. deStart and dteEnd are VB variables. MySql does not like VB date variables, and so it is best to convert to date in your SQL Query.
|
|
|
|
|
Hi,
I have a few questions. First of all, what's the flexibility and strength of MSAccess 2007 and how much data and transactions can it support?
Second, I would like to know whether it's optimum to use MSAccess 2007 as database for a small banking system, provided it's a real life application and not a demo/tutorial one. The system will have approximately 250-300 customers per year and their daily transactions for the whole year that'll count upto 1,10,000.
If MSAccess isn't optimum then which light version DBMS can I use? How about MySQL or something else?
Third, is there any light version for MSSQL server that fits into my scenario, for almost all the MSSQL versions I have seen are developer/enterprise editions?
Regards
Priyamtheone
|
|
|
|
|
The strength of MSAccess is that it has a builtin GUI, a small footprint and xcopy deployment.
The weakness is that it doesn't scale, I wouldn't recommend it for more than ten concurrent users.
I would instead start with either Oracle Express edition or MS SQLServer Express edition. Both are for free, in both cases the biggest limitations are: won't use more than one processor, 1 GB Ram, and max DB size is 4GB.
This limits you less than you might think and both options are easy to upgrade."When did ignorance become a point of view" - Dilbert
|
|
|
|
|
I'm not sure about the 2007 version but Access was NOT a multiuser, it worked OK as a mutliuser DB until it didn't and when you asked for support from MS they would stand on the disclaimer that it is NOT multiuser.
Definitely use the Express versions (I use MSSQL but that is because of my skill set) and set up a proper client server environment. MSSQL is reasonably easy to set up and very easy to work with.Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Imagine an app that where modification of values in the GUI are immediately updated to a SQL database.
Given this scenario, would you still open and dispose of a SqlConnection object for each update? My guess would be yes because the real connection to the database should be managed via connection pools.
Any rationale for either tactic would be greatly appreciated.
|
|
|
|
|
treefirmy wrote: Any rationale for either tactic would be greatly appreciated.
I'd open it just before the Connection is used, and close it as soon as I'm done with it; Take a look at tip #3 on Connection Pooling[^].I are Troll
|
|
|
|
|
I have a database that holds information including isbn numbers for books. I discovered that the isbn is not specifically a 10 digit number it can actually have a character in it so i need to change it to an nvarchar but when i try to do so it says i can't that the table needs to be dropped. Surely I don't have to delete the table and reenter thousands or records just to change that property or do I?
Please help thanks.
|
|
|
|
|
if you can't change a field, perform these steps:
- add new field (with a new name)
- copy data from old to new field
- delete old field
- optional: rename new field
You can perform these interactively, using SQL Sever Management Studio, PHPmyAdmin, or whatever fits your database.
|
|
|
|
|
wow that worked perfectly. Luc i can't thank you and the other's enough for all your help you have given me. Hopefully one day I will be able to help others and return the favor in which you have given me.
Thanks again.
|
|
|
|
|
Someday saying thank you... that rated a 5!
|
|
|
|
|
Hi All,
I ran into an issue when trying to Decrypt a password field that I had previously encrypted and was hoping someone could help. I'm using SQL Anywhere 10.
I encrypted the password field with no issues, using the following trigger when a new record was added to the table:
ALTER TRIGGER "encrypt_new_user_pwd" BEFORE INSERT
ORDER 1 ON "QAS"."tableName"
REFERENCING NEW AS newPwd
FOR EACH ROW
BEGIN
Set newPwd.pwdField = ENCRYPT(newPwd.pwdField , 'key')
END
The problem is I'm unable to decrypt the password of the newly created record (fieldID = 0002), using the following:
SELECT CAST (DECRYPT(pwdField, 'key') AS VARCHAR(100))
FROM "QAS"."tableName" WHERE fieldID = '0002'
In Sybase when trying to execute the above statement I get the following error:
Interactive SQL
The following error occurred while fetching results:
Decryption error: Input must be a multiple of 16 bytes in length for AES
SQLCODE=-851, ODBC 3 State="08001"
Do you have any idea what's causing this error?
The pwdField is of type VARCHAR and size 15.
Thanks,
Mel
|
|
|
|
|
This is just a guess but if you read the error message it says:
MWRivera wrote: Input must be a multiple of 16 bytes in length for AES
But you say:
MWRivera wrote: The pwdField is of type VARCHAR and size 15.
Is 15 a multiple of 16?
Make pwdField bigger and see if that helps.
|
|
|
|
|
Hi David,
Thanks for the reply. I changed the length of the field to 16 and this stopped the error message from displying, the only problem then was the password was showing up as squares. I then changed the length of the field to 80 (5x16=80) sticking with the multiple of 16 rule and it works great now.
Thanks for your help with this it lead to me working it out. The reason I was recieving squares I asume is because the encrypted version of the password was larger than 16 and so the full encrypted version of it was too big to fit in the password field, therefore when I tried to decrypt it, it wasn't all there to decrypt and hence the nonsense squares.
Thanks again,
Mel
|
|
|
|
|
Hello friends,
which is the better way to use transaction?
From Database
or from Application?
|
|
|
|
|
There is no answer to this, it depends on many factors I know the language. I've read a book. - _Madmatt
|
|
|
|
|
Hi,
I need some help with the database design for storing an expression tree. It should basically store a whole expression.
I'd want to query out data (in one or more result sets as necessary) so that I can finally evaluate it somehow in my front-end application. Just kind of need a table(s) structure to store and represent the relationship.
The expressions I plan to store in the database will be mostly logical expressions. Meaning they'd evaluate to a true or false mostly.
Here is a diagrammatic representation of what I want (as a result set(s)).modified on Thursday, March 4, 2010 8:31 AM
|
|
|
|
|
Hi,
I often use trees and what you essentially needs is the ID and Parent ID
for example:
ID | ParentID | Name
1 | 0 | A
2 | 1 | AA
3 | 1 | AB
4 | 0 | B
5 | 4 | BA
6 | 4 | BB
looks like:
[]
|
-A
--AA
--AB
-B
--BA
--BB
and so on...
... I hope you mean this
|
|
|
|
|
I am using VB.Net 2008 and ADO.Net to do a Batch Update to our Oracle database.
The updates are working, but there is a trigger on the table before the row is updated to enforce a member's termination termination date.
So if I was trying to set the termination date (via the batch update) to 31-Jan-2010 but the member had a claim that was processed on 2-Feb-2010 the trigger would force the termination date to be 2-Feb-2010.
However, the trigger is NOT executing when the batch update runs?
|
|
|
|
|
I would guess that triggers are disabled for batch updates then, probably as a database default. This is a sensible idea, you do NOT want triggers firing in volume and you should be managing your data not relying on a trigger. I hate the bloody things, always causing trouble, hiding under the hood and causing issues bah! Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Good idea. I'm not a DBA so do you know for sure if there is an admin option that disable a trigger for batch updates?
|
|
|
|
|
MB_KSU wrote: do you know
No idea, especially on OracleNever underestimate the power of human stupidity
RAH
|
|
|
|
|
Can any one please tell me how to call a stored procedure from case statement. Thanks In Advance
|
|
|
|
|
A Case statement in SQL is an embedded part of a Select statement so you can't call a stored procedure in the middle, only a function. However I guess you mean something more like the following:
If @Test = 1
Execute [Procedure1];
Else If @Test = 2
Execute [Procedure2];
Else If @Test = 3
Execute [Procedure3];
Else
Execute [Procedure4];
|
|
|
|
|
you can also use case when for this.
|
|
|
|
|
You are still not going to be able to exec another proc from withing the case statement! Case and Exec() do not go together! Never underestimate the power of human stupidity
RAH
|
|
|
|