|
We know it is quite easy to fetch data from sql server to datatable with dataadaptor of ado.net. However, i want to store my query result with over 2000 records to sql server now. Is there any good approach that could store this datatable immediately to sql server?
Any idea is appreciated! Thank u in advance!
|
|
|
|
|
sorry to add that the format of the query result is not determined at first. waiting for ur reply!
|
|
|
|
|
I am trying to build a simple script but by Newbie scripting is showing...
The Database creates Ok but the tables are created in the master Database not in the Newly created Db as it should...
Do I need to switch to the new Db after it is created???
I fried to append the New Db name to the table but this gave me an error??? (ShowroomRegDB.ISSUESTb)
Thoughts...
CREATE DATABASE ShowroomRegDB
drop table ISSUESTb;
drop table eMailTb;
drop table ConfigTb;
drop table SuggestionTb;
CREATE TABLE ISSUESTb
(
Issueid INT identity(1,1) not null,
IssuedDate VARCHAR(50),
);
CREATE TABLE eMailTb
(
eMailid INT identity(1,1) not null,
Lastname VARCHAR(50),
Firstname VARCHAR(50),
eMailAddress VARCHAR(100),
);
When people make you see red, be thankful your not colour blind.
|
|
|
|
|
japel wrote: Do I need to switch to the new Db after it is created???
Yes.
After the create, add : "Use database ShowroomRegDB"
|
|
|
|
|
I'm new to ADO.NET so if this question is odd, forgive me. Anyways, here the problem. I have a DataSet, that I populated with a SqlDataAdapter that I made, then I binded the DataSet to a BindingSource and hooked that up to some controls on my Form. Now if I want to add a new record to the DataSet table (there's only one in it) do I do it through the BindingSource or through the DataSet? And once the new row is added will the BindingSource be able to see it right away (so the Form can display the new record) or do I have to something to update the BindingSource? If a quick example could be provided as well that would be awesome.
Thanks for any and all help.
- Aaron
|
|
|
|
|
The AddNew method of the bindingsource control will achieve what you are looking for. You can then enter the data for the new record in the bound controls. You will need a Save button and a Cancel button. The save button should validate the data entered by the user, call the EndEdit method of the binding source, and finally call the Update method of the tableadapter to write the new record to the datasource. The Cancel button should call the CancelEdit method of the bindingsource to discard any changes made. Whether or not you need to do anything else depends on a few things in your program structure. For example, whether you are updating the dataset from the same thread as your UI. If you do not see the results of the changes immediately, you may need to call the ResetBindings method of the bindingsource.
Hope this helps.
|
|
|
|
|
Sorry about the late reply, but I haven't been near my computer for some time. Anyways, your answer worked perfectly so thank you very much.
- Aaron
|
|
|
|
|
I've got a project going here where I created my own SqlDataAdapter. The problem I'm running into is this...the SelectCommand for the adapter requires a parameter (ie. WHERE id = @id), but I have no idea how to supply this parameter to the Fill method of the adapter.
Any help on this is much apprecitated, and if you need any more info just let me know.
Thanks!
- Aaron
|
|
|
|
|
da.SelectCommand.Parameters["@id"].Value = ???
da.Fill
only two letters away from being an asset
|
|
|
|
|
That seems to have worked perfectly.
Thanks very much for the help.
- Aaron
|
|
|
|
|
What is the best way to test T-SQL stored procedures?
Do You use some special tools for this task?
Wojtek
|
|
|
|
|
I make a copy of the database to my local machine and run the stored procedure on that copy for testing. It's pretty easy and then you don't have to worry about affecting live data.
|
|
|
|
|
Could also run it within a transaction and roll it back
only two letters away from being an asset
|
|
|
|
|
Maybe, but it is safer to run it on a copy of the live database rather than the live database itself.
|
|
|
|
|
Absolutely agree, but of course if you don't have a test database...you should be flogged anyway.
only two letters away from being an asset
|
|
|
|
|
I know it is a couple of days early, but I'm in the process of moving house so I'll probably forget if I don't say this now: Happy Birthday!
|
|
|
|
|
query analyzer
|
|
|
|
|
Hi,
Thank You for answers.
I also test stored procedures on copy of DB, but I thought there are some special tools to perform tests?
Maybe do You know any?
Wojtek
|
|
|
|
|
I'm building the dts from scratch... The goal is to build a dts to export some data (sql statement is a must) from one table to a text file. I've built a package, connections (two of them, one for the sql server, and one for the text file), steps (only one), one task with one custom task, and two transformation objects (there are two columns in the select clause in sql statement). There are absolutely no transformations included, only copy od the selected data. However, when I execute the package, I get the following error:
"Incomplete file format information - file cannot be opened."
DataSource property for the text file is "DTSFlatFile". I can't figure out what's wrong... help...
|
|
|
|
|
may be u didnt selected the right option!
|
|
|
|
|
Hi ,
I want to replicate the database beetween two sql 2000 servers .
And i am going step-by-step as suggested in the code projects replication article , in that article the have suggested that we have to change the
MSSQLSERVER service startup account to the any account which is defined in SQL
SERVER under systemadmin server role. And i am also going exatly they have written , but sql server is not permitting me to logon using any logon account which is defined under sysadminserverrole.
If anybody have the solutions/sugestions regarding this problem please
send me.
Thanking You,
In advance.
param
|
|
|
|
|
Hi,
I am looking for a good article that will explain to me the BASIC's of the dataset and datatable and in particular performance issues. The article should not be overly complex particularly as to how to access them etc - just an overview.
In particular, I'm putting together my first real program of any substance and the database is growing with tables galore and so far at least 15 datatables that I use to varying degrees. I am now thinking about memory and processor demands particularly as I'm aiming the program at the home PC user and not even a so-called power user either.
I'm now considering creating another datatable that consists of parts of other datatables allready in existence. Does creating "child" datatables use up substantially more resources or does the datatable only reference data that is already in memory in the other datatables?
There are of course many ways of skinning a cat and using the VS2005 IDE seems to tempt one to take the easiest course which may not be the most efficient in terms of memory usage, CPU usage etc.
Am I being paranoid?
Glen Harvy
|
|
|
|
|
I can't think of any articles off the top of my head, but you could look into the PerformanceCounter class or keep it simple and monitor your application's performance in terms of memory/cpu usage with the Task Manager. Hope this is a start for you because there are many ways you can go abouts with testing the performance
I'd like to help but I don't feel like Googling it for you.
|
|
|
|
|
Thanks for the tip - amazing how you can overlook the obvious ie Task Manager
Of immediate concern is my assumption that once a dataset is created and tables loaded I assume another datatable referencing tables within the dataset is only going to increase resource usage minimally.
Is this the case?
Glen Harvy
|
|
|
|
|
Glen Harvy wrote: my assumption that once a dataset is created and tables loaded I assume another datatable referencing tables within the dataset is only going to increase resource usage minimally
I'm not 100% percent sure what the ramifications are on the resources when tables reference each other
too much daily WTF for someone... - Anton Afanasyev
|
|
|
|