spgen Work Item Rss Feed

Created Issue: Restricted access to different databases on a server

yasirmturk — Wed, 21 Jan 2009 13:27:43 GMT

while login using sql authentication a user may have restricted access to certain databases and on loading that databases the application throws exception and none of the database could be loaded. so the application fails...
i addressed this by moving the code part of database parsing to node afterselect event if level of selected node is 0.

Created Issue: blank default Author name

Darwood — Thu, 23 Oct 2008 13:32:40 GMT

The author name for the generated code comes prepopulated. Would be best if this was blank by default. I know that this can be changed in the options but it should be blank to start with.

Created Issue: using NovinMedia.Data ?

Darwood — Thu, 23 Oct 2008 13:31:26 GMT

Line 5 of the generated c# wrapper class has the line
using NovinMedia.Data;
surely this is a legacy from when you wrote the program for your own use?

Created Issue: Button to Generate SPs for all tables

Darwood — Thu, 23 Oct 2008 13:30:09 GMT

It would be way cool if you had a single button to press that would generate (and optionally run/create) all the stored procedures for all the tables in the selected database. At the moment you have to Select the table.
Click 'Generate Stored Procedures'
Click 'Run SQL Script against Server'
Repeat to fade.....

Not a big deal but it would be nice.

Created Issue: typo on Prefix

Darwood — Thu, 23 Oct 2008 13:27:14 GMT

In the options screen the word prefix is incorrectly spelt as perfix.

COMMENTED ISSUE: usp_ instead of sp_ as default stored procedure prefix?

pbolduc — Wed, 28 May 2008 17:42:04 GMT

Should the default stored procedure prefix be sp_ ? Correct me if I'm wrong, but I thought Microsoft doesn't like user-defined stored procedures that start with sp_. Perhaps the out-of-the-box default stored procedure prefix should be something like usp_ instead of sp_?
Comments: ** Comment from web user: pbolduc **

This is already a configurable item in the settings. Your stored procedures can start with 'sp_' if you like, however, it is not recommended. The reason is that when SQL Server attempts to execute a stored procedures that start with 'sp_', it will scan the master database first to resolve. By avoiding the 'sp_' prefix, you avoid the performance impact of scanning the master database.

COMMENTED ISSUE: Offline Database

pwhygle — Tue, 27 May 2008 21:40:25 GMT

When connecting to a Server, if a database if offline, you get the following error:
************** Exception Text **************
System.Data.SqlClient.SqlException: Database 'databasename' cannot be opened because it is offline.
Comments: ** Comment from web user: pwhygle **

My apologies, I did not complete the description of the issue.

After clicking continue on the error window, no other databases below the offline database are populated with tables in the treeview.

CREATED ISSUE: Offline Database

pwhygle — Tue, 27 May 2008 21:18:15 GMT

CREATED ISSUE: usp_ instead of sp_ as default stored procedure prefix?

fmorriso — Tue, 27 May 2008 14:30:20 GMT

CREATED ISSUE: optional Use [database_name] Go ?

fmorriso — Tue, 27 May 2008 14:26:07 GMT

How about an optional ability to generate the SQL script with the following lines at the top?

USE [name of database]
GO
{blank line}