|
Can you show your store procedure statement
Best Regards,
SOFTDEV
If you have knowledge, let others light their candles at it
|
|
|
|
|
In SP there is nothing but only select and insert statements, i mean i'm selecting new data from web sql server and inserting it into our local sqlserver.
krishna veer singh
|
|
|
|
|
I always assumed that accessing the same Access database by multiple users somehow just works, i.e. many users can read and write to an Access database in a shared folder on the network.
I assumed the same functionality with SQLce.
However, I've never been able to test it.
Does it work as I assumed ?
|
|
|
|
|
abiemann wrote: I always assumed that accessing the same Access database by multiple users somehow just works, i.e. many users can read and write to an Access database in a shared folder on the network.
Happens way too often and although Access provides locking-mechanisms and the likes, you'll find that it fails to perform adequately.
SQL Express is also available free, and you can easily upsize your Access-database to SQL Express.
I are Troll 
|
|
|
|
|
Yes, it works as you assumed... However, in both cases, each user needs to have their own front end installed (whether that's an Access DB, VB, whatever) You don't want a bunch of users opening the same file at the same time (ie: a single access database containing both tables as well as queries, forms and reports....)
|
|
|
|
|
the Access DB is used to only store data and it will be located in some shared folder on the network.
There's about 10 client apps (which is probably what you meant by "front end") that will, at any point of time, read data from the database and also write data to the database.
Forms will not be implemented in the database directly.
|
|
|
|
|
Access and SQL Server will both be fine as a back end then...
|
|
|
|
|
let us take the server is down and all the data are corrupted. other than backup,replication, log shipping what can we do to get back the data or make the customer to proceed with the work ?
|
|
|
|
|
Repeating the question won't help
only two letters away from being an asset
|
|
|
|
|
Ah, but this time some of it is bold and underlined (I guess for those of use that were too dim to understand the first time). 
|
|
|
|
|
I'm waiting for a reply, but I don't have a backup, and my response will be then you don't have a client!
|
|
|
|
|
Hi friends.
Please tell me how to convert nvarchar to smalldatetime in sql server
|
|
|
|
|
With the convert function.
declare @a nvarchar(20)
set @a = '1 jul 2009 15:30:45'
select convert(smalldatetime,@a)
Bob
Ashfield Consultants Ltd
Proud to be a 2009 Code Project MVP
|
|
|
|
|
Hi Thanks For your reply ,
The thing is that i have one table in which date is stored in column(datataype nvarchar)
There are more than lacs of records in this table.
so i want to convert this field into following format
ORIGINAL FORMAT OF FIELD IN TABLE (DATATYPE:-NVARCHAR) => 30/11/2009
I WANT INTO FORMAT : 30112009
AND ANOTHE FORMAT : 30/11/2009(SMALL DATETIME)
Please help me out.
I tried the solution which you gave but its giving following error
"Msg 8115, Level 16, State 2, Line 1
Arithmetic overflow error converting expression to data type smalldatetime.
"
Please help me out
|
|
|
|
|
Not sure why you get this error.
declare @a nvarchar(20)
select @a = '30/11/2009'
select convert(smalldatetime,@a)
gives me 2009-11-30 00:00:00, which is correct. How it is displayed (i.e. 30/11/2009 or 30112009) is down to your format mask, SQL Server simply stores the datetime value as a number.
Please, before posting any more questions around this, use the F1 key and read up on date time data types.
Bob
Ashfield Consultants Ltd
Proud to be a 2009 Code Project MVP
|
|
|
|
|
What you said is very correct , i am not denying it. The thing is that i am inserting into destination column(smalldatetime) from source column(nvarchar) and the number of records are around 4lac.
I am inserting through sql script in query analyser. After insrting some 20k records it generates that "Arithmetic overflow error".
This was task given to me. thats why otherwise i could change my destination column to datetime. Its working.
But I am forcebly want it to smalldatetime as this was task for me.
|
|
|
|
|
Have you done any data analysis to make sure that all the values you are trying to convert fall into the acceptable range for smalldatetime values?
Perhaps you have a record (around the 20K mark) that has a typo in the date, and instead of 30/11/2009 it's 31/11/2009 (which isn't valid) or 30/11/9999...
|
|
|
|
|
So you have an invalid date in there. Use the isdate function to find any that are invalid.
declare @a nvarchar(20)
set @a = '30/11/2009'
select isdate(@a)
-- returns 1
set @a = '31/11/2009'
select isdate(@a)
-- returns 0
Its not rocket science.
Bob
Ashfield Consultants Ltd
Proud to be a 2009 Code Project MVP
|
|
|
|
|
You were correct there were dates in dd/mm/yyyy which were incorrect format according to ISDATE() function . So i converted it into mm/dd/yyyy format and it worked.
Now thing is that i just saved in date format only like '11/30/2009' but in table having column date (datatype smalldatetime) it stored like '11/30/2009 00:00:00.000'
I want to store only date (datatype=smalldatetime). Is there any way to store into sql server 2005 date column with date only excluding time.
|
|
|
|
|
Lalit singh wrote: Is there any way to store into sql server 2005 date column with date only excluding time.
No, as I said in an earlier post, sql server stores the date and time as a number, not in any format. Just use a format when you display it.
Bob
Ashfield Consultants Ltd
Proud to be a 2009 Code Project MVP
|
|
|
|
|
Thank you very much for your valuable response.
|
|
|
|
|
why would you choose smalldatetime when all you want to store is a date?
Luc Pattyn
I only read code that is properly indented, and rendered in a non-proportional font; hint: use PRE tags in forum messages
Local announcement (Antwerp region): Lange Wapper? 59.24% waren verstandig genoeg om NEEN te stemmen; bye bye viaduct.
|
|
|
|
|
Questions such as this explain so much about the world we now find ourselves in 
|
|
|
|
|
From the discussion I gather that you are running up against the first problem of storing date data in a non date data format.
You have precicely 1 choice to fix this problem, change your data type to datetime NOW, if you use a work around to convert from nvarchar to datetime then you will always be performing that work around. STOP AND FIX YOUR DATA.
I suggest creating a new column in a datetime format and convert/copy the data to that field. You are already getting an error (arithmetic) so I know your nvarchar data is corrupt. I would recursively convert as much as possible and then manually update the rest.
|
|
|
|
|
let us take the server is down and all the data are corrupted. other than backup,replication, log shipping what can we do to get back the data or make the customer to proceed with the work ?
bala
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
