Re: How to Close any opened Connections to a database? - C# Discussion Boards

Re: How to Close any opened Connections to a database?

3-Dec-09 7:51

Perhaps Management Studio has the database open? If so, you have to close Management Studio; I don't think you can close another application's connection, at least it shouldn't be your standard operating method.

modified on Thursday, December 3, 2009 2:19 PM

CoderForEver3-Dec-09 7:57

CoderForEver

3-Dec-09 7:57

I didnt get what you said... Can you elaborate it to me

Re: How to Close any opened Connections to a database?

CoderForEver3-Dec-09 8:13

CoderForEver

3-Dec-09 8:13

I knew that... but wat i wanted is how to close all connections that are opened @ that time

Re: How to Close any opened Connections to a database?

Shorgov3-Dec-09 11:17

Shorgov

3-Dec-09 11:17

Do you know how to use google?
I tried with - "kill connections sql server" and all of the top 10 results had the answer.

Re: How to Close any opened Connections to a database?

Ashfield3-Dec-09 20:53

Ashfield

3-Dec-09 20:53

BUT, to kill connections (not your own) you need sa rights, not something which most accounts should have.

Bob
Ashfield Consultants Ltd
Proud to be a 2009 Code Project MVP

Re: How to Close any opened Connections to a database?

Shorgov3-Dec-09 22:09

Shorgov

3-Dec-09 22:09

Yap, this is true, but if you are building an administrative module you should grant this kind of rights to the admin of the application.

Re: How to Close any opened Connections to a database?

Ashfield4-Dec-09 1:09

Ashfield

4-Dec-09 1:09

Shorgov wrote:
you should grant this kind of rights to the admin of the application.

Matter of opinion. It allows far to much damage to be done - do you really want to give a user the right to drop tables etc?

Bob
Ashfield Consultants Ltd
Proud to be a 2009 Code Project MVP

Re: How to Close any opened Connections to a database?

Shorgov4-Dec-09 5:32

Shorgov

4-Dec-09 5:32

Only to the appropriate user Smile | :)

In general I am agreed with you, but user not allays means dumb person. User of this admin module can be a developer(responsible for the maintenance of the system ) or a trained consultant who knows what he is doing.

Returning date time as null

Joe Rozario3-Dec-09 5:07

Re: Returning date time as null [modified]

3-Dec-09 5:07

Dear friends..

i have small problem ..

this is my code

private DateTime convertByteToDatetime(byte[] Data)
{
try
{
DateTime now = DateTime.Now;
byte[] year = new byte[2];
year[0] = Data[0];
year[1] = Data[1];
int nYear = convertByteToInt(year);
DateTime dt = new DateTime(nYear, (int)Data[2], (int)Data[3], (int)Data[4], (int)Data[5], (int)Data[6]);
return dt;
}
catch
{
return (null);
}
}
in Catch block i can't return null because Datetime is value type

i do not want to return any date if there is an error....

What shall i do..

Any idea.? suggestion?

By

joe

0x3c03-Dec-09 5:09

0x3c0

3-Dec-09 5:09

You have two options. You could return default(DateTime); or change the return type to Nullable<DateTime>

[edit] You could also rethrow the exception. I find this a tad ugly, but whatever works for you

OSDev

modified on Thursday, December 3, 2009 12:05 PM

Joe Rozario3-Dec-09 5:15

3-Dec-09 5:15

Thank Your friend ...

for Your replay ..

0x3c0 wrote:
Nullable<datetime>

what this line will return? sorry i do not know.

how to use this Nullable<datetime>?

syntax please?

thank U

0x3c03-Dec-09 5:37

0x3c0

3-Dec-09 5:37

You replace private DateTime convertByteToDatetime(byte[] Data) with private Nullable<DateTime> convertByteToDatetime(byte[] Data). Then you can either return new Nullables, or just keep your code and rely on the implicit operators. If you do that, you don't need to do anything apart from checking HasValue in your calling code. If that's true, then retrieve value.

Example:

Nullable<DateTime> nullableDate = convertByteToDatetime(new byte[] {0, 0, 0});

if(nullableDate.HasValue)
    //your date time is in nullableDate.Value
else
    //something bad happened.

However, please be aware that this will call your code to fail silently. I would personally raise an event detailing the exception before I return null so that I know precisely what went wrong without having to sprinkle try-catch blocks everywhere.

OSDev

Joe Rozario3-Dec-09 5:41

3-Dec-09 5:41

Thank You frined .....

i shall try that .

Smile | :)

PIEBALDconsult3-Dec-09 5:10

3-Dec-09 5:10

=>Joe<= wrote:
if there is an error...

... throw an Exception.

Joe Rozario3-Dec-09 5:18

3-Dec-09 5:18

thanks for your replay...

PIEBALDconsult wrote:
... throw an Exception.

i do not want stop the process ... in other words i have skip to othere work ..

thank U

PIEBALDconsult3-Dec-09 5:20

Re: Returning date time as null [modified]

3-Dec-09 5:20

That's up to the calling routine to decide.

Luc Pattyn3-Dec-09 5:44

Luc Pattyn

3-Dec-09 5:44

=>Joe<= wrote:
Any idea.? suggestion?

AFAIK there are four popular ways, you've had most of them already:

1.
set aside a special value, could be Default<DateTime> or any other value you don't need as a real value. For DateTime, there is also DateTime.MaxValue

2.
nullable types, written either as Nullable<DateTime> or DateTime? (with question mark)
I don't like them much as they take more memory, and cause some trouble when parts of your environment don't know how to handle them (e.g. files, databases, ...).

3.
Use an Exception. That often is the most elegant approach, assuming the "no value" situation really is exceptional.

[ADDED, AS SUGGESTED BY PIEBALD]
4.
Return a boolean and have the value in an out parameter. Like with TryParse.
[/ADDED]

Smile | :)

Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]

I only read code that is properly indented, and rendered in a non-proportional font; hint: use PRE tags in forum messages

modified on Thursday, December 3, 2009 2:59 PM

Joe Rozario3-Dec-09 6:00

3-Dec-09 6:00

thank you friend for your replay...and the suggestion ... Big Grin | :-D

PIEBALDconsult3-Dec-09 10:45