Database

amioni24-Jul-14 4:25

24-Jul-14 4:25

all of this properties are Ok and as i said this same package works wonders on my colleague's machine with vs 2010
i dont think it s a problem with connection string or else

GuyThiebaut24-Jul-14 3:44

GuyThiebaut

24-Jul-14 3:44

amioni wrote:
e.UniqueID e. [Web Id] from Elements

I am not seeing a comma between the two columns you reference, is that correct?

“That which can be asserted without evidence, can be dismissed without evidence.”

― Christopher Hitchens

amioni24-Jul-14 3:51

24-Jul-14 3:51

it s just an example of a query so dont worry it s with comma in my package, and it s not the problem

GuyThiebaut24-Jul-14 4:26

GuyThiebaut

24-Jul-14 4:26

Always read the error message - Syntax Error, permission violation, or nonspecific Reviews another error

There is either:
An error in the sql - you can check this by running the sql in isolation.
A permission issue - harder to track, I would test this by creating a simple SSIS package and try to run it from your code.
Non specific error - eliminate the first two possibilities then look into this.

“That which can be asserted without evidence, can be dismissed without evidence.”

― Christopher Hitchens

amioni24-Jul-14 5:09

24-Jul-14 5:09

NB : when i make this query in Stored procedure and i call it in the oledb source it work fine but not when i make it directly

GuyThiebaut24-Jul-14 5:43

GuyThiebaut

24-Jul-14 5:43

I don't understand what that means - I will need more information to be able to help you.

“That which can be asserted without evidence, can be dismissed without evidence.”

― Christopher Hitchens

jschell24-Jul-14 12:44

jschell

24-Jul-14 12:44

amioni wrote:
NB : when i make this query in Stored procedure and i call it in the oledb source it work fine but not when i make it directly

A user (database) can have different permissions based on direct sql versus stored procs.

amioni24-Jul-14 22:54

24-Jul-14 22:54

i am working with sa user (dev pc)

amioni2-Sep-14 0:52

2-Sep-14 0:52

hi,

i answer myself because i found the solution:
with sql server native client 10 we can't add param with subquery
but this problem is resolved with SQL native client 11 (sql server 2012)

thank you

Wink | ;)

sql server

saharmirzaei23-Jul-14 9:12

23-Jul-14 9:12

hi i found a Gregorian date conversion function in sql server but i dont know how i can use it!
could you help me?

Richard Deeming23-Jul-14 9:17

Richard Deeming

23-Jul-14 9:17

Not without seeing it.

What are you trying to achieve? All date/datetime types in MSSQL already use the Gregorian calendar. Are you trying to convert to a Julian date? A different calendar system?

"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer

saharmirzaei23-Jul-14 23:30

23-Jul-14 23:30

i wanna convert english calender to persian calender.i got this function but i cant use it.I am not a professional i MSSQL

PIEBALDconsult23-Jul-14 9:32

PIEBALDconsult

23-Jul-14 9:32

Just put it back where you found it.

You'll never get very far if all you do is follow instructions.

saharmirzaei23-Jul-14 23:26

23-Jul-14 23:26

thank you for your help Smile | :)

Bernhard Hiller23-Jul-14 21:49

Bernhard Hiller

23-Jul-14 21:49

Perhaps you actually think of a function for converting from/to Persian calendar?

saharmirzaei23-Jul-14 23:23

23-Jul-14 23:23

yeah i think about it and i dont know how i can use this.

Mycroft Holmes23-Jul-14 23:47

Mycroft Holmes

23-Jul-14 23:47

Seems to be a solved problem, have some google foo[^]

Never underestimate the power of human stupidity
RAH

Weird MS SQL "Error"

GenJerDan23-Jul-14 8:07

23-Jul-14 8:07

I ran this in the Management Studio:

update [Master] set Data_Thru = '7/23/2014 9:49:00 AM'
where Data_Thru = '7/23/2014 8:00:00 AM'

So why did it actually set the smalldatetime to 7/23/2014 9:50:00 AM?

(And don't yell at me for the table name. It wasn't my idea.)

We won't sit down.
We won't shut up.
We won't go quietly away.

YouTube
and
My Mu[sic], Films and Windows Programs, etc.

Richard Deeming23-Jul-14 8:47

Richard Deeming

23-Jul-14 8:47

Are you absolutely sure that that's the precise query that you executed, and that the row you're looking at is the one it updated?

smalldatetime[^] will round to the nearest minute, but it will only round up if the seconds are greater than or equal to 29.999; anything else will round down.

SQL

SELECT
    CAST('7/23/2014 9:49:29.998 AM' as smalldatetime),
    CAST('7/23/2014 9:49:29.999 AM' as smalldatetime)
;

/*
Output:
2014-07-23 09:49:00
2014-07-23 09:50:00
*/

"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer

GenJerDan23-Jul-14 9:10

23-Jul-14 9:10

Richard Deeming wrote:
Are you absolutely sure that that's the precise query that you executed, and
that the row you're looking at is the one it updated?

Yep.

Freaked me out. I've never seen that before, and it had no problem with me going in and correcting it back down to 9:49 via T-Sql

We won't sit down.
We won't shut up.
We won't go quietly away.

YouTube
and
My Mu[sic], Films and Windows Programs, etc.

Richard Deeming23-Jul-14 9:18

Richard Deeming

23-Jul-14 9:18

Weird. Are there any triggers on that table? Or other users updating the same row at the same time? Confused | :confused:

"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer

GenJerDan23-Jul-14 9:28

23-Jul-14 9:28

Nope. No triggers. And no users at all (yet).

Maybe we'll have to pass it off as a cosmic ray hitting the server and flipping a bit at just the right time. I see no resason for it, and Google came up with nothing, either.

We won't sit down.
We won't shut up.
We won't go quietly away.

YouTube
and
My Mu[sic], Films and Windows Programs, etc.

jschell23-Jul-14 12:55

jschell

23-Jul-14 12:55

When I run into impossible situations in code then the only solution is to examine my assumptions. That is always where I find the problem that lead to the impossibility in the first place.

Bernhard Hiller23-Jul-14 22:01

Bernhard Hiller

23-Jul-14 22:01

What's the version / localization of your SQL Server?
I tried it with SQL Server 10.0.5500, German localized Management studio. I adjusted the date format of your query, and tested it. And it worked as it was expected to work - I cannot reproduce your bug.

GenJerDan24-Jul-14 4:14