Skip to main content

Avoid using sp_rename ...

sp_rename is the system stored procedure used to rename user created objects like “Stored procedure“, “Trigger“, “Table“ etc., This SP works pretty fine as long as you don't use it to rename a “Stored proc“, “Trigger“ or a “View“.

Let me try and explain this with an example. Normally once a SP, Trigger or a View is created an entry is made into sysobjects as well as syscomments tables.

For better understanding follow the following steps (examples uses Pubs database).

Step 1:

/*
Description: Sample procedure to demonstrate sp_rename issue
Author: M. Vadivel
Date: August 12, 2004
*/

Create Procedure FetchAuthorsDetails
As
Select * from Authors

Step 2: [self explanatory]

/*
Description: Query to see the stored proc details in sysobjects
Author: M. Vadivel
Date: August 12, 2004
*/

Select [name] from sysobjects where name like 'FetchAuthors%'

Step 3: [self explanatory]

/*
Description: Query to see the stored proc details in syscomments
Author: M. Vadivel
Date: August 12, 2004
*/

Select [text] from syscomments where [text] like '%FetchAuthors%'

Step 4:

Now let us try to rename this stored proc using sp_rename.

/*
Description: Query to rename the stored procedure into a new name
Author: M. Vadivel
Date: August 12, 2004
*/

sp_rename 'FetchAuthorsDetails','FetchAuthorsDetailsRenamed'

After this if you execute the queries mentioned in Step 2 and 3 you could find that in syscomments table still the old name is retained!!

In order to double check it, go to SQL Enterprise Manager and navigate to the Pubs database. If you check the SP name it would be the new name only. But just double click that SP and see the code within it. It would be refering to the old sp name i.e., 'FetchAuthorsDetails'.

So in order to avoid this confusion its always better to generate the script of the SP, trigger or view which you would like to rename. Then delete it and recreate it with a new name (using the script generated).
Labels:

Comments

Post a Comment

Popular posts from this blog

Registry manipulation from SQL

Registry Manupulation from SQL Server is pretty easy. There are 4 extended stored procedure in SQL Server 2000 for the purpose of manupulating the server registry. They are: 1) xp_regwrite 2) xp_regread 3) xp_regdeletekey 4) xp_regdeletevalue Let us see each one of them in detail! About xp_regwrite This extended stored procedure helps us to create data item in the (server’s) registry and we could also create a new key. Usage: We must specify the root key with the @rootkey parameter and an individual key with the @key parameter. Please note that if the key doesn’t exist (without any warnnig) it would be created in the registry. The @value_name parameter designates the data item and the @type the type of the data item. Valid data item types include REG_SZ and REG_DWORD . The last parameter is the @value parameter, which assigns a value to the data item. Let us now see an example which would add a new key called " TestKey ", and a new data item under it called TestKeyValue :
Post a Comment
Read more

Screen scraping using XmlHttp and Vbscript ...

I wrote a small program for screen scraping any sites using XmlHttp object and VBScript. I know I haven't done any rocket science :) still I thought of sharing the code with you all. XmlHttp -- E x tensible M arkup L anguage H ypertext T ransfer P rotocol An advantage is that - the XmlHttp object queries the server and retrieve the latest information without reloading the page. Source code: < html > < head > < script language ="vbscript"> Dim objXmlHttp Set objXmlHttp = CreateObject("Msxml2.XMLHttp") Function ScreenScrapping() URL == "UR site URL comes here" objXmlHttp.Open "POST", url, False objXmlHttp.onreadystatechange = getref("HandleStateChange") objXmlHttp.Send End Function Function HandleStateChange() If (ObjXmlHttp.readyState = 4) Then msgbox "Screenscrapping completed .." divShowContent.innerHtml = objXmlHttp.responseText End If End Function </ script > < head > < body > &l
2 comments
Read more

Script table as - ALTER TO is greyed out - SQL SERVER

One of my office colleague recently asked me why we are not able to generate ALTER Table script from SSMS. If we right click on the table and choose "Script Table As"  ALTER To option would be disabled or Greyed out. Is it a bug? No it isn't a bug. ALTER To is there to be used for generating modified script of Stored Procedure, Functions, Views, Triggers etc., and NOT for Tables. For generating ALTER Table script there is an work around. Right click on the table, choose "Modify" and enter into the design mode. Make what ever changes you want to make and WITHOUT saving it right click anywhere on the top half of the window (above Column properties) and choose "Generate Change Script". Please be advised that SQL Server would drop actually create a new table with modifications, move the data from the old table into it and then drop the old table. Sounds simple but assume you have a very large table for which you want to do this! Then it woul
2 comments
Read more