ringht now i am working with one web page, in that page i have 3 sections of data [or 3 set of data] in 1 set 4 to 5 fields actions to be taken when we click on save button 1st it should save the 1st fields data in one of my sp and it should get the table level id it should loop that table level id into another set of records & insert into to the another sp
We are building an ASP.NET application with C#.net language and Oracle 9i database. Here we installed Oracle 9i client software on our PCs.We never worked on Oracle 9i database. It's the first time.We are planning to build stored procedures in Oracle database and call them from our ASP.NET application. Does working with Oracle stored procedures and ASP.NET is similar to that of working with MS SQL Server stored procedures and ASP.NET?
I have a stored procedure which is working fine and also code in my vb class, which when I click on save, looks as though it has executed but no information is saved into the database....
My code used to save the data into the database is below.
I have several stored procedures in my database, some of them have params, some have no params. I tried to fill a business object by calling the stored procedures, but failed so far. How could I do that dynamically? Later, I want to use this object as a datasource for a report...but thats the next step. The important facts are:
different stored procs return different amount of columns stored procs can have params, but its not required
I have access to two servers, one with my development database on, and another with the live database on.
All SQL Stored Procedures, Functions, Views are encrypted on the live database (using WITH ENCRYPTION in my query)
However I'm concerned I might accidentally encrypt a bunch of SProcs on my development database meaning I can no longer view/edit that code.
I have full control over the server and database, and was wondering if there is a way I can prevent these from being encrypted, therefore throwing up an error when this is attempted?
The database I am using has a schema called EQB and as such, my stored procedures are named as EQB.usp_SelectFunds, EQB.usp_SelectAccount, etc.
On the select tab of the Configure Data Source screen, I choose to use a stored procedure. The dropdown shows my stored procedures, however, the schema name does not show up in front of the stored procedures in the drop down. I see only usp_SelectFunds, usp_SelectAccount, etc.
I select one of the stored procedures and when I click TEST, I get the message that the stored procedure is not found. If I instead choose to use a SQL statement instead on the configuration screen and enter EXEC EQB.usp_SelectFunds and click TEST, it works fine.
Why are my stored procedures not showing up correctly in the stored procedure drop down and how can I fix this?
I'm a novice @ asp.net and in fact any dynamic website building as I'm normally the dba behind the scenes, however, circumstances arise and now I'm looking at the front end, so forgive me if my question seems so obvious or badly worded, it's only day 2 of the .net environment for me.
I have a stored procedure with several parameters (11) that I have written & tested on the server.
I am trying to call it on a web form (using visual web developer 2008 express)
I have created the text boxes & drop downs on the form.
Added a gridview table connected to my stored procedure (which then works on testing) (parameters set to control & picked from the dropdown of form boxes to match).
there is also a submit button. (no coding added) just dragged on page.
Like i said when I test the connection for the gridview of the stored procedure it works, however on the web face it doesn't. I put in the parameters click the submit button and the screen refreshes, i get done @ the bottom but no results. I tried just using the sql and got the same result. I've looked at books but can't see what I'm missing, although, i suspect the onclick event of my submit button.
And this is my other SP that I define Condition ,and according to that condition it update or insert data in database
USE [behtop] GO /****** Object: StoredProcedure [dbo].[insertestate] Script Date: 10/04/2012 11:36:21 ******/ SET ANSI_NULLS ON GO SET QUOTED_IDENTIFIER ON GO ALTER procedure [dbo].[insertestate]
[Code] ....
In first SP @code parameter is column in table that I don't want accept duplicate value and condition of that is:
IF NOT EXISTS(SELECT behcode FROM Estate_p WHERE code = @code)
And in second SP I have @code parameter that I don't want it insert duplicate data on it too. But here condition is
IF @id > 0 AND EXISTS(SELECT behcode FROM Estate_p WHERE id=@id)
The following code works well as long as I pass a querystring value to the datalist.
Private Sub BindGrid() Dim id As Integer = Integer.Parse(Context.Request.QueryString("id")) Dim strConnString As String = ConfigurationManager.ConnectionStrings("Conn").ConnectionString Using con As New SqlConnection(strConnString) Using cmd As New SqlCommand() cmd.CommandText = "select Id, Name from tblFiles where Id=@Id"
[Code] ......
However, the page errors with the message "Value cannot be null." if I don't pass a value. I know that DataList does not have an EmptyItem Property like a Gridview control. I do not want the page to error if I don't pass a value. Need info to deal with empty values in a datalist.
Most websites have pointed me to this code to use:
The 'list' throws an error. The error is "Too few type arguments to 'System.COllections.Generic.List". I am not sure if the code is written in C# and that is what is causing the error. It seems that it should work but I can not figure out the 'list' error.
I have several VB.NET functions which pass and receive values from executed stored procedures using parameters. However, the latest method I am using seems to be a little too specific on the datatype and data length of the parameters for my liking (i.e.
LogActivityCommand.Parameters.Add("@strErrSource", SqlDbType.NVarChar, 300).Value = strErrSource). For example:
[code]....
If I end up changing the datatype and data length properties of the variables in my SQL stored procedures in the future, I am going to have to re-visit my VB code too and alter the parameter settings here as well.
I have a situation where in a legacy app (VB6) I have a grid which is populated by any one of a large number of (100+) stored procedures. Each of the procedures returns one or more rows with an identical list of columns (including column names, column data types, column order). I am basically looking at the (best) options to keep things reasonably light weight. Each procedure has its own set of parameters, each of which would result in different query plans etc. I have tried using each query to exec select into a (temp) table which is encapsulated into a "master" query which then returns a single results set, but it breaks SQL, the query optimiser returns an infinite number of rows - this is a MS documented issue. Looking for possible ways forward: generics, model view etc
I was reviewing my old post about this issue with a accessdatasource and that was simple since the Select, Update and Delete were all written within the datasource.
But this page im having issues with is using SQLDataSource and pointing to Store procedures. My issue is that i have created the sqldatasource with Insert(storeprocedure), Select(actual select statement), Update(storeprocedure) and was trying to take advantage of gridviews capabilities for editing when connected to a datasource that has all those elements setup.
Here is my datasource and gridview code: The gridview row goes into edit mode, but the changes never take affect on the database.
We have an existing application with a mature database where most of the business logic is in Stored Procedures that are maintained by a separate department. Application developers are not given access to the database except via stored procedures.
I am looking for an example of calling stored procedures from within MVC.
Actually, we have done almost no development until now in ASP.Net at all. Is the difficulty in interacting with stored procedures a MVC problem or is it a more generic ASP.Net problem?
I used to be a software tester. I am a little bit familiar with stored procedures from client-server apps. My understanding is that they are on a server (where they operate more efficiently than if they were a module of code on a client machine) and they are used to modify the database.
Can anyone give me information a nutshell about stored procedures and when to use them?
I've been working on an upgrade for an app that's currently online.
I copied the database to my development server, have been making upgrades to the db (new tables, additional stored procedures, functions, etc). The new upgraded db is now complete and ready to go back online. I developed a script for all the new tables as I created them.
Basically this new db will go with the new upgraded app at a new domain.
So my plan is this...
Copy my existing db (the original) over to the new server.Run the script I developed on my development server to upgrade the new db to the latest version. Take the original db offline once the new one is running. However when I developed the new sps and fcns I didn't script them like I did for the tables (ooops! not thinking), and I have about 100 new sps. Is there anyway to script all the sps in one hit, so that I can run one script to upgrade the new db?
Suppose you have to query a lot of tables and calculate some values and spit it out to the user. Is it ok to have all the business logic for this in the stored procedures? Or is it a better practice to return all the data to the application and do all the data manipulation and rolling up in there?
writing vb.net classes based on a MS Sql Stored procedure. So, here's my question.....Is there some kind of tool out there that will generate a class based on a stored procedure. So, for example, the tool can read a Stored Procedure like below: