Database Discussion Boards

Re: SQL Server (image) data type

Eddy Vluggen11-Jun-12 0:07

Eddy Vluggen

11-Jun-12 0:07

10 Mb will remain just that, unless you use a CompressionStream.

Bastard Programmer from Hell Suspicious | :suss:

MySQL Password

Tom M3W10-Jun-12 4:09

Tom M3W

10-Jun-12 4:09

I had a programmer in a foreign country develop an application for me, I had to dismiss him because he would not finish the program on time. I asked him for the source code to MySQL db and he would not provide it. I paid him so that wasn't the issue. I need to move my application from one cloud server to another company and I need help in figuring out how to break the db code to move the application. There are a lot of connection points in and out of the db so I can't just copy the db and move it over.

Thanks

Re: MySQL Password

Eddy Vluggen10-Jun-12 4:13

Eddy Vluggen

10-Jun-12 4:13

Isn't the password mentioned in the connectionstring?

Bastard Programmer from Hell Suspicious | :suss:

difficult query

m_safaaaa9-Jun-12 8:12

m_safaaaa

9-Jun-12 8:12

hello,

I have a table named: 'Applicant' having fields:

'id_Applicant', 'name,'date_of_birth','date_of_death'

the sql or oracle query is:

'Select all applicant who are alive on 30-05-2012'

Please it's urgent

thanks alot.

Re: difficult query

Richard Andrew x649-Jun-12 9:09

Richard Andrew x64

9-Jun-12 9:09

What have you tried so far?

The difficult we do right away...
...the impossible takes slightly longer.

Re: difficult query

Paul Conrad9-Jun-12 9:24

Paul Conrad

9-Jun-12 9:24

m_safaaaa wrote:
Please it's urgent

That's a big no no to say in a forum post. People will help you when they can. As the other poster has mentioned, what have you tried so far?

""Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon

Re: difficult query

PIEBALDconsult9-Jun-12 10:16

PIEBALDconsult

9-Jun-12 10:16

I suspect that 2012-05-30 just might possibly be between the date_of_birth and the date_of_death (or some date in the future if null). Unsure | :~

You are using DATE or DATETIME fields, right? Right?

modified 9-Jun-12 17:11pm.

Re: difficult query

Sandeep Mewara9-Jun-12 20:09

Sandeep Mewara

9-Jun-12 20:09

Posting in multiple forums is considered rude. Please find an appropriate forum and stick to it: Difficult query please it's urgent[^]

Sandeep Mewara
[My last tip/trick]: Server side Delimiters in ASP.NET[^]

Re: difficult query

vvashishta10-Jun-12 19:08

vvashishta

10-Jun-12 19:08

SELECT * FROM Applicant
WHERE Date_Of_Death > CONVERT(VARCHAR,'30-05-2012',106)

- Happy Coding -
Vishal Vashishta

Re: difficult query

Bernhard Hiller10-Jun-12 20:02

Bernhard Hiller

10-Jun-12 20:02

Works great, if the guy is still alive today...
Your query selects all who have already died past that date - that's a difference.

Re: difficult query

Bernhard Hiller10-Jun-12 19:59

Bernhard Hiller

10-Jun-12 19:59

Either date_fo_death is null or greater than the given date:

SQL

SELECT *
FROM Applicant 
WHERE date_of_death is null
   OR date_of_death>@somedate

Re: difficult query

Michael Potter12-Jun-12 11:02

Michael Potter

12-Jun-12 11:02

SQL

SELECT
    id_Applicant,
    name,
    date_of_birth,
    date_of_death
FROM
    Applicant
WHERE
    '5/30/2012' BETWEEN date_of_birth AND ISNULL(date_of_death,'1/1/3000')

SSIS OleDB or ADO.NET

cjb1107-Jun-12 23:05

cjb110

7-Jun-12 23:05

Just wondering what differences there are between these two connection methods in SSIS? We are connecting to SQL 2008 R2 databases.

Is one better performing than the other? Or is one easier to use? There does seem to be certain tasks that can only use one or the other.

Re: SSIS OleDB or ADO.NET

PIEBALDconsult8-Jun-12 3:44

PIEBALDconsult

8-Jun-12 3:44

An ADO.net connection will use the native client classes so it is better.

sql Date conversion not working in sql 2000

Robymon7-Jun-12 22:12

Robymon

7-Jun-12 22:12

I am trying to insert string date to datetime column with the following way.(Sql2000)

CONVERT(DATETIME, @To, 103)

but this is not saving the DD/MM/YYYY format in the webserver, but it is working in my local machine.In the webserver sql it is saving as MM/DD/YYYY format.

Re: sql Date conversion not working in sql 2000

Bernhard Hiller7-Jun-12 22:41

Bernhard Hiller

7-Jun-12 22:41

Use a parameterized query, that will do the magic around the date format.

Re: sql Date conversion not working in sql 2000

Corporal Agarn8-Jun-12 1:30

Corporal Agarn

8-Jun-12 1:30

It is based on how the systems are setup. Cannot remember the SET command and have to go to work. Sorry.

Re: sql Date conversion not working in sql 2000

Simon_Whale8-Jun-12 4:43

Simon_Whale

8-Jun-12 4:43

SQL

SET DATEFORMAT DMY

that the one you were thinking of?

Lobster Thermidor aux crevettes with a Mornay sauce, served in a Provençale manner with shallots and aubergines, garnished with truffle pate, brandy and a fried egg on top and Spam - Monty Python Spam Sketch

Re: sql Date conversion not working in sql 2000

Corporal Agarn8-Jun-12 4:44

Corporal Agarn

8-Jun-12 4:44

Yep thanks

Re: sql Date conversion not working in sql 2000

Eddy Vluggen8-Jun-12 1:51

Eddy Vluggen

8-Jun-12 1:51

Your string-representation is a culture-dependent format, a way of displaying a date in a specific culture. Date (and time) itself is not a string, but a number.

Make sure it's a DATE column in the database, and pass a Date (not a string) to the query. Use parameters as suggested.

using (var con = new SqlConnection(connectionString))
using (var cmd = con.CreateCommand())
{
  cmd.CommandText = "SELECT * FROM SomeTable WHERE MyDate = @MyDate";
  cmd.Parameters.AddWithValue("@MyDate", DateTime.Now);
}

Bastard Programmer from Hell Suspicious | :suss:

Re: sql Date conversion not working in sql 2000

Luc Pattyn8-Jun-12 2:47

Luc Pattyn

8-Jun-12 2:47

the purpose of a database is to store information, not to format it. Store dates and datetimes in fields with the appropriate type, and let your applications take care of formatting when presenting results to the user. Do not try and have the database format stuff, you will get lots of trouble and never get satisfactory results.

And as others have said, use SQL parameters rather than SQL string concatenation, to feed dates and datetimes to the database; thus avoiding all conflicts with regional settings and the like.

Smile | :)

Luc Pattyn [My Articles] Nil Volentibus Arduum

Re: sql Date conversion not working in sql 2000

PIEBALDconsult8-Jun-12 4:11

PIEBALDconsult

8-Jun-12 4:11

If the column is a DATETIME, then the statement "it is saving as MM/DD/YYYY format" is untrue.

If the output of SELECT thedate FROM table shows different formats when executed on different systems, it is because of the "Region and Language" settings of the systems -- see the control panel -- and this is correct behaviour. If you want to override this behaviour (you shouldn't) then format it via the query.

And I strongly reccommend ISO 8601 format YYYY-MM-DD.

Re: sql Date conversion not working in sql 2000

vvashishta10-Jun-12 19:09

vvashishta

10-Jun-12 19:09

Put it like,

CONVERT( VARCHAR, @To AS DATETIME, 103 ) )

- Happy Coding -
Vishal Vashishta

function

Rafat Ali Khan7-Jun-12 21:39

Rafat Ali Khan

7-Jun-12 21:39

How to make a function in sql server-2008?

Re: function

Simon_Whale7-Jun-12 21:42

Simon_Whale

7-Jun-12 21:42

Have a read of this MSDN: Create Function[^]

there are some examples at the bottom of the page

Lobster Thermidor aux crevettes with a Mornay sauce, served in a Provençale manner with shallots and aubergines, garnished with truffle pate, brandy and a fried egg on top and Spam - Monty Python Spam Sketch

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.