  | 
			
				SoftTree Technologies 
				Technical Support Forums
			 | 
		 
		  | 
	 
	 
	
	
	
		
	
	
	
		| Author | 
		Message | 
	 
	
		
			anp@ambientasgr.com 
			 
			
  
			
			
				Joined: 24 Feb 2025 Posts: 8 Country: Italy | 
			 
			  
		 | 
		
			
				  Intellisense doesn't show all schemas | 
				     | 
			 
			
				Hi.
 
I'm using Sql Assistant 13.0. I'm using it since more than one year with no probs with SQLSERVER 2017. Now we are migrating to a new instance with the same database, but the intellisense doesn't show all schemas.
 
I can see schemas like [domain\user] or the schena dbo. Other schemas (like Staging, created with dbo as owner) aren't shown and even if I start to write Staging.TableName, after typing Staging. the list of table under the Staging schema isn't visualized.
 
 
Thanks for your help
 
 
Best
 
Andrea
  | 
			 
		  | 
	 
	
		| Fri Aug 01, 2025 3:58 am | 
		          | 
	 
	
		  | 
	 
	
		
			SysOp 
			Site Admin 
			
  
			
			
				Joined: 26 Nov 2006 Posts: 7992
  | 
			 
			  
		 | 
		
			
				   | 
				     | 
			 
			
				Hi Andrea, this is a permissions issue.  Granting VIEW DEFINITION permission at the database level to your user, or specific permissions on the schema or objects, can resolve this.
  | 
			 
		  | 
	 
	
		| Fri Aug 01, 2025 8:46 am | 
		          | 
	 
	
		  | 
	 
	
		
			anp@ambientasgr.com 
			 
			
  
			
			
				Joined: 24 Feb 2025 Posts: 8 Country: Italy | 
			 
			  
		 | 
		
			
				   | 
				     | 
			 
			
				At database/server level? can you suggest me a script or something similar?
 
At a first glance, it seems that I have identical permission on both server/databases
 
Thanks a lot
 
 
EDIT: I tried this
 
 
GRANT VIEW definition ON SCHEMA::Dimensions TO [domain\myuser]
 
 
but the schema Dimensions isn't showed in intellisense
 
 
EDIT 2:
 
I solved the issue adding to the Schema query in DBQueries the following
 
 
or @@version like 'Microsoft SQL Server 2022%'
 
 
Now all schemas are correctly showed in the intellisense
  | 
			 
		  | 
	 
	
		| Fri Aug 01, 2025 9:32 am | 
		          | 
	 
	
		  | 
	 
	
		
			SysOp 
			Site Admin 
			
  
			
			
				Joined: 26 Nov 2006 Posts: 7992
  | 
			 
			  
		 | 
		
			
				   | 
				     | 
			 
			
				Maybe you had a customized query in the options which wasn't compatible with your server version? 
 
 
The default query with a condition "@@version LIKE '%SQL Server 20%' " should have covered the case of 2022. Any version beginning with "20" is compatible with that condition. 
 
You may want to try restoring factory default options as there might be other issues you haven't noticed yet and think they are by design, while they are not.
  | 
			 
		  | 
	 
	
		| Mon Aug 04, 2025 8:42 am | 
		          | 
	 
	
		  | 
	 
	
		
			anp@ambientasgr.com 
			 
			
  
			
			
				Joined: 24 Feb 2025 Posts: 8 Country: Italy | 
			 
			  
		 | 
		
			
				   | 
				     | 
			 
			
				
	  | 
	
 
	  | 
	Maybe you had a customized query in the options which wasn't compatible with your server version? 
 
 
The default query with a condition "@@version LIKE '%SQL Server 20%' " should have covered the case of 2022. Any version beginning with "20" is compatible with that condition. 
 
You may want to try restoring factory default options as there might be other issues you haven't noticed yet and think they are by design, while they are not. | 
	 
 
 
 
Thanks I'll do it
  | 
			 
		  | 
	 
	
		| Tue Aug 05, 2025 4:30 am | 
		          | 
	 
	
		  | 
	 
	
		 | 
	 
 
  
	 
	    
	   | 
	
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
  | 
   
 
		 | 
	 
	  |