Automatic Generation of Insert, Update and Delete stored procedures

Question

Post reply

Automatic Generation of Insert, Update and Delete stored procedures

SAMARDEEP

Right there with Babe

Points: 727
More actions
July 27, 2009 at 12:41 pm

#224039

Comments posted to this topic are about the item Automatic Generation of Insert, Update and Delete stored procedures

Viewing 11 posts - 1 through 10 (of 10 total)

You must be logged in to reply to this topic. Login to reply

paul price-200520 SSC Rookie Points: 32 More actions · Answer 1

I had to replace x'3f' with spaces globally before the code would parse. These showed up as squares in my browser.

paul.m.cohen SSC Rookie Points: 45 More actions · Answer 2

The routine does not work for "timestamp" columns. I get three errors one for each procedure that is being created. Had the same problem with "3f" character except my browser showed them as spaces but Visual Studio did not understand them at all and gave a useless error message.

PS Thanks for the routine, it will be extremely useful.

SAMARDEEP Right there with Babe Points: 727 More actions · Answer 3

Hi..

Thanks for bringing this in notice..actually this is a browser problem and i'd try to rectify it in next post..

Thanks

SAMARDEEP Right there with Babe Points: 727 More actions · Answer 4

Hi paul..

Thanks for the "timestamp" issue..would rectify it soon

Regards

DWIGHT RUTLEDGE Grasshopper Points: 19 More actions · Answer 5

I had to also do the replacement for spaces. However, I have a weird issue. I copied it into one database and it works great. However, I put it into another database it just returns that command(s) completed successfully but there are not procs created. Both databases are SQL 2008 standard.

SAMARDEEP Right there with Babe Points: 727 More actions · Answer 6

HI..

Just try to debug it and see where the problem is..

there may be a problem with compatible data type..and if it is then you can easily resolve it..

Regards..

paul.m.cohen SSC Rookie Points: 45 More actions · Answer 7

Why do you use ALTER instead of CREATE when you create the Stored Procedures? I have enabled the Print option to see that it is you use the actually create the SP, then I copy what gets printed and execute it and SQL 2005 complains but if I change ALTER to CREATE I get past that issue.

ldemeyer@telenet.be SSC-Addicted Points: 490 More actions · Answer 8

DWIGHT RUTLEDGE (8/13/2009)
I had to also do the replacement for spaces. However, I have a weird issue. I copied it into one database and it works great. However, I put it into another database it just returns that command(s) completed successfully but there are not procs created. Both databases are SQL 2008 standard.

I have the same issue - no procs created (sqlserver express 2008)

SAMARDEEP Right there with Babe Points: 727 More actions · Answer 9

just put print statements after creation of every SP so that u can know which part is causing the problem..

or post your script..

marrowyung-701823 Valued Member Points: 51 More actions · Answer 10

How can I do the same thing for all user database without running this script for all database one by one ?

I am looking for a way to do it by one script only, then less human error.