Search

alter or create view scripts missing GO statement by RakAttack

Resolved
as Not Reproducible Help for as Not Reproducible

1
0
Sign in
to vote
Type: Bug
ID: 776541
Opened: 1/14/2013 4:02:16 PM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
When I right-click a view and either select alter view or create view, the generated script is missing GO commands so when I try and run it I get errors.
Details (expand)

Product Language

English

Version

SQL Server 2012 - Enterprise Edition

Category

Tools (SSMS, Agent, Profiler, Migration, etc.)

Operating System

Windows 7 Professional

Operating System Language

US English

Steps to Reproduce

right-click any view and select alter or create

Actual Results

USE [CustomerDB]

/****** Object: View [dbo].[vw_AllCustomers]    Script Date: 1/14/2013 3:52:16 PM ******/
SET ANSI_NULLS ON

SET QUOTED_IDENTIFIER ON


ALTER VIEW [dbo].[vw_AllCustomers]

Expected Results

USE [CustomerDB]
GO

/****** Object: View [dbo].[vw_AllCustomers]    Script Date: 1/14/2013 3:52:16 PM ******/
SET ANSI_NULLS ON
GO

SET QUOTED_IDENTIFIER ON
GO


ALTER VIEW [dbo].[vw_AllCustomers]

Platform

X64

Virtualization

 
File Attachments
0 attachments
Sign in to post a comment.
Posted by Microsoft on 3/20/2013 at 11:26 AM
Hello We didn't recieve any update from you on this issue, so we assume that the issue was resolved and we will go ahead and close it. You can always reactivate it later and provide more details as needed. Thank you Alex Grach[MSFT]
Posted by Microsoft on 1/21/2013 at 11:49 AM
Hi RakAttack,
Looks like you have set the scripting option "Delimit individual statements" to false. To set it to true, from SSMS menu, select "Tools" -> "Options". In the left of the "Options" window, select "SQL Server Object Exploer" -> "Scripting". Expand "General scripting options" and set "Delimit individual statements" to true.
Please try to script any views again and Let us know if you have any questions.

Thanks

Jinlin Zhang
Microsoft Sql Server
Posted by Microsoft on 1/15/2013 at 11:15 AM
Thank you for reporting this issue - we are investigating and will update you when we have more information.

Thanks,

Alex Grach [MSFT SQL SERVER]
Sign in to post a workaround.