|
myConnection.Dispose();
myConnection.Close();
Dispose and then close
|
|
|
|
|
|
It's a bit odd that it has both. Close comes from IDbConnection, while Dispose is inherited from System.ComponentModel.Component.
A bit of digging with Reflector[^] shows that Dispose simply calls Close, if the connection is in the Open state, then sets the ConnectionString property to null.
My rule of thumb is that if you're planning to call Open on this object again, use Close, but if you're not going to use this object again, use Dispose.
Stability. What an interesting concept. -- Chris Maunder
|
|
|
|
|
That's good information, but I don't think that using Dispose with the built-in connection pooling will do anything but incur a slight performance penalty for the extra work, although I haven't tested yet. It seems that the actual underlying connection is just mapped to IDbConnection instances, and associated upon Open() and disassociated upon Close. From the docs, it seems logical to assume that resetting ConnectionString, in correctly implemented code, would result in the IDbConnection being disassociated from its pool, but why bother if you're just throwing the object away?
One good thing that you bring up is that it's probably a good idea to hang onto your IDbConnection if you're going to need a connection again, even after Close(). This'll get you out of some creation and destruction overhead. Bright bright bright
-Jeff
here, bloggy bloggy
|
|
|
|
|
I have a service that connects to SQL Server 2K via ODBC.
I need the service to know when certain tables have been modified.
Right now the plan is :
- create trigger(s) for the appropriate modifications
- have the trigger(s) call an extended stored proc with the name of the server, port and message
- the esp will connect to the specified service and send the message
Questions :
Is there a way to do this already that i've missed ?
If not, when does the dll with the esp get loaded/unloaded.
In particular, i don't want the esp to create a socket each time it's called, i'd like to have 3 esp's : an init, one called by the trigger, and a term. The init would open the socket, the term would close it, and the one called by the trigger would just send the message. Of course this won't work if the dll is loaded/unloaded on each call (doubt it works this way, just want to make sure).
...cmk
Save the whales - collect the whole set
|
|
|
|
|
Hey guys,
I need a stored procedure which could read data from all types of files and then print the data or store it in a table. i have tried bulk insert but when bulk insert reads the data and stores it in a table it creates many rows (.i.e rows = number of lines in the files). say if there are 20 lines then 20 rows and if 700 lines 700 rows. I want to store the data in one string and print it. Also the files i need to read are generated on runtime. If u want to take a look at the Sto. Proc. here it is. Please note files culd be of any size.
**********************************************************
1. Bulk insert
CREATE PROC sp_readTextFile @filename sysname
as
BEGIN
SET nocount ON
EXEC ('bulk INSERT WilTemp FROM "' + @filename + '"')
SELECT * FROM WilTemp
END
GO
***********************************************************
2. Using a filesytem object
CREATE PROCEDURE [dbo].[readFromFile] (@FileName varchar(255))
AS
DECLARE @FS int, @OLEResult int, @FileID int, @Text1 varchar(8000)
EXECUTE @OLEResult = sp_OACreate 'Scripting.FileSystemObject', @FS OUT
IF @OLEResult <> 0 PRINT 'Scripting.FileSystemObject'
--read a file
execute @OLEResult = sp_OAMethod @FS, 'OpenTextFile', @FileID OUT, @FileName, 1
IF @OLEResult <> 0 PRINT 'OpenTextFile'
--Read Text1
execute @OLEResult = sp_OAMethod @FileID, 'ReadAll', @Text1 OUT
IF @OLEResult <> 0 PRINT 'ReadAll'
--insert into tfromfile values (@Text1)
Print @Text1
EXECUTE @OLEResult = sp_OADestroy @FileID
EXECUTE @OLEResult = sp_OADestroy @FS
GO
|
|
|
|
|
Does anyone know how to insert commas in database? like if i want to insert:
Hi,How are you? I am fine, ThanQ.
??
|
|
|
|
|
This should work:
INSERT myTable(myColumn)
VALUES('Hi,How are you? I am fine, ThanQ')
"You can have everything in life you want if you will just help enough other people get what they want." --Zig Ziglar
Coming soon: The Second EuroCPian Event
|
|
|
|
|
Thats wrong syntax.
What about multicolumns?
Insert into Table1(col1,col2,col3) values('Hi, how are you?','I'm fine thanQ',I guess, this SQL will fail, for sure');
See, so many quotes and commas in the SQL statement.
Do I need to parse and eleminate all those quotes and commas, do u have any other trick?
|
|
|
|
|
Anonymous wrote:
Thats wrong syntax
Sorry, I missed the INTO 
Anonymous wrote:
What about multicolumns?
They are no different.
INSERT INTO Table1(col1, col2, col3)
values('0,23','2,49','4,99')
Anonymous wrote:
See, so many quotes and commas in the SQL statement
Ah! Now... This is different - You never mentioned anything about quotes before.
Anonymous wrote:
Do I need to parse and eleminate all those quotes and commas, do u have any other trick?
No tricks, just the SQL Server Books online that come with SQL Server 2000.
SET QUOTED_IDENTIFIER OFF
GO
Insert into Table1(col1,col2,col3)
values("Hi, how are you?","I'm fine thank you","I guess this SQL won't fail!");
GO
SET QUOTED_IDENTIFIER ON
I actually tested this on a real live SQL Server so I wouldn't mess up the syntax again by just writing it in directly to the web site
"You can have everything in life you want if you will just help enough other people get what they want." --Zig Ziglar
Coming soon: The Second EuroCPian Event
|
|
|
|
|
Thanks! but i am using MS Access, and trying to insert using ADO.NET(C#)
Colin Angus Mackay wrote:
SET QUOTED_IDENTIFIER OFFGOInsert into Table1(col1,col2,col3) values("Hi, how are you?","I'm fine thank you","I guess this SQL won't fail!");GOSET QUOTED_IDENTIFIER ON
|
|
|
|
|
Thanks! but i am using MS Access, and trying to insert using ADO.NET(C#)
Colin Angus Mackay wrote:
SET QUOTED_IDENTIFIER OFFGOInsert into Table1(col1,col2,col3) values("Hi, how are you?","I'm fine thank you","I guess this SQL won't fail!");GOSET QUOTED_IDENTIFIER ON
The above syntax is SQL server specific!!
|
|
|
|
|
Anonymous wrote:
Thanks! but i am using MS Access.... The above syntax is SQL server specific!!
Why didn't you say that?!?
"You can have everything in life you want if you will just help enough other people get what they want." --Zig Ziglar
Coming soon: The Second EuroCPian Event
|
|
|
|
|
Hi
the best way to avoid problems realated to invalid characters is to insert using Insert Commands. and pass the string values as parameters..
this way it will work fine even if the string contains * ' _ ? etc.
|
|
|
|
|
The advice given by other folks here is sound. I just wanted to mention a couple of things.
1) I'm no Access expert, but valid SQL escaping syntax for quotes in strings works this way:
INSERT INTO blah (data) VALUES ('My daddy''s goat just ran up a tree')
Just double them.
2) I think that you're confused about commas. If they appear inside strings, they're not evaluated as list delimiters by the parsing engine at all. You can have zillions of commas inside your strings with no impact whatsoever.
Regards,
Jeff Varszegi
EEEP! An Extensible Expression Evaluation Package
|
|
|
|
|
Hi Friends,
Is there any way to install office 2000 developer on named instance?
VIkramS
|
|
|
|
|
vikrams wrote:
Is there any way to install office 2000 developer on named instance?
Do you mean SQL Server named instance?
If so, it asks you during setup. I think one of the questions is about a default install/instance and you say no then you get a text box to type the name of the instance.
It has been a while since I've installed it, so I'm a bit fuzzy.
"You can have everything in life you want if you will just help enough other people get what they want." --Zig Ziglar
Coming soon: The Second EuroCPian Event
|
|
|
|
|
Hello All,
I have a SQL 200 DB in place, but now I want to run a script or SP that will give me as an output the name and data type of all the columns in one of the tables. Any Ideas?
Thanks in Advance.
|
|
|
|
|
|
|
You're welcome! I assume you have access to Query Analyzer, yes? You could spend a fun couple of hours just poking around in
1) the master.dbo tables, where lots of useful information is stored;
2) INFORMATION_SCHEMA views, which Microsoft recommends whenever possible;
3) the other databases like msdb, where job and replication info is stored
etc. etc. Also look up system functions and sp_ stored procedures in books online. After all that, you'll have the beginnings of the beginnings of a good working knowledge of SQL Server. And get your boss to spring for the Microsoft Press books on SQL Server; they're really good.
Regards,
Jeff Varszegi
EEEP! An Extensible Expression Evaluation Package
|
|
|
|
|
For some reasons I have to use Auto Translate=False in my connection string.
My connection string is like;
"data source=2003-SERVER;Initial Catalog=db_name;uid=db_user;pwd=user_password;max pool size=50;Auto Translate=False"
This works fine when I use system.data.oledb. But not working with system.data.sqlclient. It gives me
System.ArgumentException: Keyword not supported: 'auto translate'
This shows me that I cannot use Auto Translate with system.data.sqlclient, but when I try to add sqlconnection from Visual Studio 2003, ToolBox->Data->SqlConnection and then build connection string from properties window <new connection...>, I can see Auto Translate option in Data Link Properties' All tab. Ok I set it to false and turn back to code behind to see how it uses auto translate=false, I saw nothing about it. ConnectionString is in there but contains nothing about Auto Translate=False.
Any ideas about how to add Auto Translate=False to my connection string, and use it with system.data.sqlclient?
Thanks in advance.
|
|
|
|
|
System.Data.SqlClient implements the Tabular Data Stream (TDS) protocol for communicating with SQL Server directly (well, it uses the underlying dbnetlib.dll so that any protocol can be used, but it performs all the formatting itself). You shouldn't necessarily expect all parameters to be supported.
The Auto Translate option, by my understanding, applies to character data supplied to OLE DB in byte-oriented character format (loosely referred to as 'ANSI' by a lot of MS documentation). In order to prevent misinterpretation by the remote server, it converts from the thread's character set to Unicode (UTF-16) then back from UTF-16 to the server's configured byte-oriented character set. If you turn the option off, it simply passes the bytes directly to the server with no translation; if the client and server use different encodings, this can lead to misinterpreted data.
However, in .NET you only provide character data to the managed provider as a System.String. This type is natively Unicode UTF-16; hence the Auto Translate option, if it were available, would have no effect.
If you're trying to store and retrieve binary data, use a binary-type column (binary, varbinary or image) and the appropriate type for the SqlParameter (SqlDbType.Binary, SqlDbType.VarBinary, SqlDbType.Image).
If you're reading byte-oriented character data from a file, ensure that you're interpreting it correctly by setting the Encoding in your StreamReader constructor, or use the appropriate encoding when converting a byte array to a string.
If you post the exact problem you're experiencing, it might be possible to work out a solution.
Stability. What an interesting concept. -- Chris Maunder
|
|
|
|
|
My problem is; I have a sql server which has collation: Latin1_General_CI_AS, and a database with same collation (actually, I am not the designer of that db, and I cant change any settings). In a table I have a varchar(60) column. When I insert text data which contains Turkish characters, Turkish characters are not stored normal. So when I retrieve those data to my asp.net application, Turkish characters are not displayed correctly, which is expected. All my language settings in web.config file is set to Turkish, but this still couldnt solve my problem. But when I use data.oledb to connect sql server and set auto translate=false, everything works fine. But when I use data.sqlclient, Turkish characters are not displayed correctly. And I cant use auto translate=false property with sqlclient.
Any ideas?
Thanks in advanced
|
|
|
|
|
Ah, I see what you're doing: setting Auto Translate=False simply does a byte-for-byte copy into the field - you're basically pretending to SQL Server that you're providing the correct encoding.
The database column is using code page 1252[^] (Windows Western), but your data is encoded with 1254[^].
This really isn't a good idea. Searches and sorts are unlikely to match your cultural expectations if the server has the wrong collation.
I'm afraid I can't offer a short-term solution: I don't know enough about it. The long-term solution is to get the collation changed for the field.
I think this is probably a job for Microsoft tech support.
Stability. What an interesting concept. -- Chris Maunder
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
