Re: Question on Database Project
Tech-Archive recommends: Fix windows errors by optimizing your registry
You might want to consider using the Developer edition of SQL Server
to create the database objects for your asp.net application. Although
you can create stored procedures in Visual Studio, it does have all of
the tools you need to create, tune and secure a SQL Server database.
The Developer edition costs $49 US and the license agreement prohibits
you from using it in production. See
http://www.microsoft.com/sql/howtobuy/development.mspx for more
information.
--Mary
On 1 Oct 2005 09:01:01 -0700, nashak@xxxxxxxxxxx wrote:
>Hello,
>
>
>I'm working on a asp.net project under VS-2003. I have created a
>database project and connected to my database and created some stored
>procedures. When I run my app, I get the error - "Stored procedure not
>found".
>
>I'm sure I'm missing some step to either compile this SP or do
>something so that my code recognises the SP.
>
>Could someone point me to the right direction or provide step by step
>details on how to create a DB project and how to create SP in VSTudio
>and go from there?
>
>Thanks,
.
Relevant Pages
- Re: Unable to view system stored procedures from .NET IDE and unable to debug SQL
... But what is the reason for the debug problem I mentioned below? ... try to step into a stored procedure in the Northwind database, ... Run SQL server setup or contact database ... I can't see any system stored procedures in master. ...
(microsoft.public.dotnet.framework.adonet) - Re: Identical database w/ identical stored procedures?
... > creating the maintence nightmare of updating the same stored procedure ... First of all, put your source code, tables, stored procedures and all ... This can be achieved with a help table in the database. ... Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx ...
(comp.databases.ms-sqlserver) - Re: What clients to use with Developer version?
... post myself but I still feel she meant as a database development tool only. ... Access is not geared towards designing a SQL Server 2000 database, ... >>off the developer edition of SQL Server is licensed as a development tool ...
(microsoft.public.sqlserver.clients) - Re: Does nesting stored procedures make sense to increase performance?
... Reducing client or middle-tier round trips to the database is a good idea in that it will reduce network traffic. ... In SQL Server 2000, because recompiles of query plans are done on a per-procedure basis, it's helpful some execute one SQL statement per procedure as well. ... If you're going to combine many calls into a single call, you'll need to add robust error handling to the "driver" procedure so as not to call procedures 2,3, and 4 if procedure 1 fails, etc. You'd need to replicate your existing client/middle-tier code's concept of success/failure results quit the batch of procedures on a failure and the return the results/return code that the client/middle-tier sees in the original. ... I've recently became aware of nesting stored procedures in SQL Server. ...
(microsoft.public.sqlserver.programming) - Re: Debugging in VS.NET
... > "Cannot debug stored procedures because the SQL Server database is not ...
(microsoft.public.sqlserver.msde) |
|
