manojg https://docs.microsoft.com/archive/blogs/mageorg/feed.xml Wed, 17 Apr 2019 03:23:30 GMT en-US hourly 1 partitioned view is not updatable because a partitioning column was not found https://docs.microsoft.com/archive/blogs/mageorg/partitioning-column-was-not-found Thu, 14 Apr 2016 18:09:06 GMT https://blogs.msdn.microsoft.com/mageorg/?p=75  Constraint testing CHECK (Empid > 10), Constraint PK_EmpID PRIMARY KEY(EmpID) ) ON [PRIMARY] USE DB2 GO CREATE TABLE [dbo].[employee]( [Empid] [int] NOT NULL , [EmpName] [char](5) NOT NULL, [AddressLine1] [varchar](8000) NULL, [Addressline2] [varchar](8000) NULL,  Constraint testing CHECK (Empid < 11), Constraint PK_EmpID PRIMARY KEY(EmpID) ) ON [PRIMARY] I created the following view create view vwDistributedEmp as select empid,empname,AddressLine1,AddressLine2 from DB1.dbo.Employee union all select empid,empname,AddressLine1,AddressLine2 from DB2.dbo.Employee go while trying to populate the table using the view it threw the following error "partitioned view is not updatable because a partitioning column was not found" After some struggle, I suspected that it could be because of the value for the check constraint. Even though the values of EmpId would not overlap  with the above constraint the above tables were recreated as below and the insert using partitioned view succeeded. USE DB1 GO CREATE TABLE [dbo].[employee]( [Empid] [int] NOT NULL , [EmpName] [char](5) NOT NULL, [AddressLine1] [varchar](8000) NULL, [Addressline2] [varchar](8000) NULL,  Constraint testing CHECK (Empid > 10), Constraint PK_EmpID PRIMARY KEY(EmpID) ) ON [PRIMARY] USE DB2 GO CREATE TABLE [dbo].[employee]( [Empid] [int] NOT NULL , [EmpName] [char](5) NOT NULL, [AddressLine1] [varchar](8000) NULL, [Addressline2] [varchar](8000) NULL,  Constraint testing CHECK (Empid <= 10), Constraint PK_EmpID PRIMARY KEY(EmpID) ) ON [PRIMARY]   PS: Use the execution plan to check which table in the partitioned view is  used.]]> Script Task Editor in SSDT 2012 is crashing : Error 'Microsoft.VisualStudio.Progression.Actions.GetNodeAtSourcePosition' https://docs.microsoft.com/archive/blogs/mageorg/script-task-editor-in-ssdt-2012-is-crashing-error-microsoft-visualstudio-progression-actions-getnodeatsourceposition Fri, 11 Apr 2014 22:11:09 GMT https://blogs.msdn.microsoft.com/mageorg/2014/04/11/script-task-editor-in-ssdt-2012-is-crashing-error-microsoft-visualstudio-progression-actions-getnodeatsourceposition/ After all the confusion, I managed to get the database project template appear on my Visual Studio 2012 IDE. Then I installed the "Microsoft SQL Server Data Tools - Business Intelligence for Visual Studio 2012" and was happy to get the BI assets appear. Without much delay tried to create a SSIS project and everything went smooth. As part of further investigation, I created a script task and clicked on the Script task editor, then to my horror I saw it crashing, it opens another window and that crashes. The error description is Message=Field not found: 'Microsoft.VisualStudio.Progression.Actions.GetNodeAtSourcePosition'.

The error description did not take me any where.  Finally, the following steps resolved the issue

1. Uninstalled and Install again Visual Studio 2012, select the SSDT feature ( this is optional )

2.  Remove the SSDT from SQL Server installation.

3. Install "Microsoft SQL Server Data Tools - Business Intelligence for Visual Studio 2012" from https://www.microsoft.com/en-in/download/details.aspx?id=36843

4. This will populate the "C:\Program Files (x86)\Microsoft Visual Studio 11.0\VSTA" with required binaries.

5. Since I had re-installed Visual Studio, I had to install "SSDT for Visual Studio 2012" https://msdn.microsoft.com/en-US/jj650015. This will bring up the database project template.

reference :

https://msdn.microsoft.com/en-us/data/hh297027

https://pietervanhove.azurewebsites.net/?p=461

]]> An error occurred while executing batch. Error message is: The directory name is invalid https://docs.microsoft.com/archive/blogs/mageorg/an-error-occurred-while-executing-batch-error-message-is-the-directory-name-is-invalid Thu, 09 May 2013 00:48:16 GMT https://blogs.msdn.microsoft.com/mageorg/2013/05/09/an-error-occurred-while-executing-batch-error-message-is-the-directory-name-is-invalid/ I faced the error as mentioned in the title, while executing a query using linked server.  The following steps where done to resolve the issue

1. checked the environment variables TEMP and TMP

2. from command prompt execute the following

       echo %temp%

       echo %tmp%

 

check if both are the same, and check if there is a directory with the name as you get from the environment variables.  I found that there was folder name 7 and it was not available. I created manually that folder,  the linked server executed successfully.

]]> What version of CLR is used in an executable https://docs.microsoft.com/archive/blogs/mageorg/what-version-of-clr-is-used-in-an-executable Fri, 03 May 2013 21:10:00 GMT https://blogs.msdn.microsoft.com/mageorg/2013/05/03/what-version-of-clr-is-used-in-an-executable/ 1. Open Visual studio command Prompt.

2. execute ILDASM.exe.  This will open a GUI.

3. From File->Open, select the executable.

4. double click on Manifest.   The CLR version used can be found as in the screen shot.

 

 

 

]]> How to find the .NET versions installed https://docs.microsoft.com/archive/blogs/mageorg/how-to-find-the-net-versions-installed Fri, 03 May 2013 21:01:15 GMT https://blogs.msdn.microsoft.com/mageorg/2013/05/03/how-to-find-the-net-versions-installed/ 1. open  Visual studio tools command prompt

2. execute clrver.exe and you will get the versions installed.

]]> SQL Server connection issues https://docs.microsoft.com/archive/blogs/mageorg/sql-server-connection-issues Mon, 08 Apr 2013 07:58:00 GMT https://blogs.msdn.microsoft.com/mageorg/2013/04/08/sql-server-connection-issues/ After installing sql server 2012 along side of sql server 2008 R2,  i was not able to connect to the new named instance of 2012. The following are the troubleshooting steps which led to the solution,

  1. check if the TCP net protocols  ( go to the sql server configuration manager ) are enabled.
  2. The port number is not conflicting with the default port which is used by other instance.  go to the properties of network protocol and check if the IP address and the port number mentioned are correct.
  3. open an inbound rule for the new TCP port in firewall settng.
  4. now restart the service and check if the new instance can be connected locally and remotely.
  5. if it is not possible to connect from remote machine, try to connect as <servername>,<port number>.  if this works then the port is properly assigned, otherwise there is some conflict of the port mentioned. if so, check what are the ports mapped on the server.  This can be identified by executing netstat -ao from command prompt.
  6. if it is not possible to connect as <server name>\<instance name> then check if SQL Browser service is running. if not start that service and try to connect.

 

]]> shortcut to remove empty lines from sql query window https://docs.microsoft.com/archive/blogs/mageorg/shortcut-to-remove-empty-lines-from-sql-query-window Wed, 14 Nov 2012 20:29:02 GMT https://blogs.msdn.microsoft.com/mageorg/2012/11/14/shortcut-to-remove-empty-lines-from-sql-query-window/ Most of you would have seen that while pasting the result of sp_helptext in query window, it throws up lot of blank lines. The following steps would help to format the result.

 
1.       Create a batch file with the following lines,
 
            @echo off
            findstr /v /r /c:"^$" /c:"^\ *$" /c:"^\       *$" %1 > %temp%\delblanklinestmp.txt
            copy /Y %temp%\delblanklinestmp.txt %1
            del /Q %temp%\delblanklinestmp.txt
 
2.       Save the batch file, say  c:\temp\DelBlankLines.bat
3.       From SSMS,  add the above batch file as an external tool to be executed. Refer the image below for the parameters
 
 
 
 
 
4.       Map the command to a hot key as shown below,
 
 
 
5.       You are all set to test..
6.       From query window, execute sp_helptext  <procedure>   (having result in grid would be better)
7.       Copy the text from the result window and paste into the query window.
8.       Save the query window.  If there are no irritating blank lines, create few for testing.
9.       Click Ctrl+F12.
10.     Reload to see the change..
]]>