Please let me know, if anyone knows it, a code static analysis tool for Sybase database (stored procedures, functions, triggers).
Imagine I am creating a Winforms app, using WCF I connect the same to SQL Server. I would be creating stored procedures in SQL Server.
My scenario here is as I release updates for my app over time...like ver 1.0, ver 2.0...v.n...
I might then need to modify my stored procedures. But I can't do that as it might affect users using the earlier version of the app. Hence I might need to create new stored procedures for the newer versions over time.
So I would want to know what is the best naming convention for my stored procedures? Can I name them something like sp_name_1_0, sp_name_2_0 and so on? It would have been much easier if there was some kind of grouping possible for stored procedures in SQL Server like folders...
Let me know what the best way is!
Thanks,
Sarin Gopalan
I have just installed Sql Server Compact Edition. To my surprise, we can't use stored procedure in sql server CE. Do I have any alternative of Stored Procedure in Sql Server CE.
I am strongly obsessed with stored procedure, I can'nt think of an application without stored procedures.
Please help, Thanks in advance.
Edit: Can I use Managed Stored Procedures.
SqlCe is a local database for use by an application. There is no need for stored procedures since the database is just a local data store, and the business logic is in the application. It is not an engine. If you need an engine then use SqlExpress or its big brother. See Steve Lasker's Comparing SQL Server Express and Compact Editions Whitepaper at http://download.microsoft.com/download/A/4/7/A47B7B0E-976D-4F49-B15D-F02ADE638EBE/Compact_Express_Comparison.doc. It explains everything you need to know.
No, you cannot use managed stored procedures. SqlCe is in-process.
Also, you might find Data Storage Architecture with SQL Server 2005 Compact Edition at http://msdn.microsoft.com/en-us/library/bb380177(SQL.90).aspx helpful.
This blog from Steve Lasker describes how you can implement something similar to sprocs on SQL Server Compact: http://blogs.msdn.com/stevelasker/archive/2008/02/11/stored-procedures-and-sql-server-compact-the-great-debate.aspx
You will have to use inline sql in your application. Use SqlCeCommand.CommandText Property to specify sql text.
I don't really know what is supported by SQL Server CE, but UDFs can often be substituted for stored procedures. If that doesn't help, try calculated columns and/or indexed views. If those are not available as options, then I think you are stuck with putting the logic in your application.
We have a very complex set of stored procedures that have been migrated over from Oracle in to SQL 2005. At one time, I heard there was a solution where sequence diagrams could be created from either watching a stack trace in VS or by the SQL profiler. I've searched long and hard and have found may tools that will create sequence diagrams of your code, but not the DB interaction. Is anybody aware of a set of tools that maybe able to help me out.
I can stand up many different environments including SQL 2005, SQL 2005, VS 2005, VS 2008.
I'm not aware of any, but you could add a call-log table with a timestamp and sp/function name, and have each sp & function log its activity.
I have a fairly complex CLR stored procedure. What is the best way to debug the procedure? I would like to step through it if possible.
Google is your friend. Or more info in your post.
How to: Debug a SQL CLR Stored Procedure