July 27, 2009 at 12:41 pm
Comments posted to this topic are about the item Automatic Generation of Insert, Update and Delete stored procedures
August 12, 2009 at 9:45 am
I had to replace x'3f' with spaces globally before the code would parse. These showed up as squares in my browser.
August 12, 2009 at 12:19 pm
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.
August 12, 2009 at 11:18 pm
Hi..
Thanks for bringing this in notice..actually this is a browser problem and i'd try to rectify it in next post..
Thanks
August 12, 2009 at 11:19 pm
Hi paul..
Thanks for the "timestamp" issue..would rectify it soon
Regards
August 13, 2009 at 4:44 pm
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.
August 13, 2009 at 11:18 pm
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..
August 14, 2009 at 2:39 pm
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.
November 3, 2009 at 5:19 pm
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)
November 3, 2009 at 10:00 pm
just put print statements after creation of every SP so that u can know which part is causing the problem..
or post your script..
March 17, 2010 at 11:27 pm
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.
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy