7 жыл бұрын
7 жыл бұрын
7 жыл бұрын
Пікірлер
@amat1721 20 күн бұрын
thank you !
@Spirreli 27 күн бұрын
Very good demonstration. Thanks for sharing.
@RahulTripathi0110 Ай бұрын
I can't the option to create workspace identity . i guess ms have changed it or what..
@mainajnabee 3 ай бұрын
Can I not grant OLS for individual tables (without semantic model) using tabular editor?
@KeshariDharmendra 3 ай бұрын
If you want to restrict access to individual tables in a semantic model, your only option is to use the semantic model itself. However, if you need to grant access to a specific table for a user accessing it through the warehouse or lakehouse, you can do so without using the semantic model.
@mainajnabee 3 ай бұрын
@@KeshariDharmendrathanks but my main question was about Tabular Editor having that ability
@jeromedupourque6067 4 ай бұрын
Very interesting and well explained, congratulations
@hamifa23 4 ай бұрын
you are awesome thank you！
@PallaviRoutaray-f8z 4 ай бұрын
very informative..thanks for explaining it so well
@RajaeRoopa 5 ай бұрын
Very good information 👍
@Sozvdn 6 ай бұрын
please put more such useful videos
@rameshpaskarathas6512 6 ай бұрын
Great video with explanations. Even with the correct GRANT statements to alter the SQL endpoint permissions, a user cannot seem to create VIEWS on a user specific or main dbo schema? does this seem right? A user can perform many DML operations but not create VIEWS?
@KeshariDharmendra 6 ай бұрын
@rameshpaskarathas6512, did you see any error?
@rameshpaskarathas6512 6 ай бұрын
@@KeshariDharmendra.I get an error below: " Error Details The view could not be created because of the following error. Error Code InternalError Message An internal error occurred."
@EsteraKot 6 ай бұрын
That is an awesome video!! Kudos!
@pollybora5423 6 ай бұрын
Very informative tutorial on Fabric!!
@William-Liljedahl 6 ай бұрын
I created some roles in through SQL queries in my lakehouse, I then granted this role to people and they had access to only the tables they should. However, when I woke up my pipelines that overwrite, replace or drop tables to bring in new data had all removed the roles of the people and they had nothing again? Is this how it's supposed to work?
@KeshariDharmendra 6 ай бұрын
Replace and drop will remove the access instead give access at schema level. GRANT SELECT ON schema:dbo to xyz;
@William-Liljedahl 6 ай бұрын
@@KeshariDharmendra Thank you, I was surprised that "Copy data activity" with Overwrite as table action also removed access but it hopefully won't be a problem if I do it at schema level.
@KeshariDharmendra 6 ай бұрын
@@William-Liljedahl Yes, I am assuming that it should work. If it doesn't, we can think of creating another SP activity in the pipeline to give permission
@LearnMicrosoftFabric 6 ай бұрын
Very nicely done, thanks Dharmendra!
@KeshariDharmendra 6 ай бұрын
Thank you Will!
@pollybora5423 6 ай бұрын
Very informative tutorial!!
@bennielopez6158 7 ай бұрын
This is the most robust demonstration of this feature I have seen. Thank you. It is a shame that it is not available in P-SKUs.
@pollybora5423 7 ай бұрын
Very good information!!
@pollybora5423 7 ай бұрын
Very informative!!
@ajaykumar-wc8gi 7 ай бұрын
Where is the the script which you shown in video to validate articles?
@KeshariDharmendra 7 ай бұрын
you can follow here www.dharmendrakeshari.com/add-new-articles-existing-transactional-replication-without-initializing-old-articles/
@DanielWeikert 7 ай бұрын
Great video. Could not find the slidest you used on your blog. Is it there as well br
@KeshariDharmendra 6 ай бұрын
@Daniel, I haven't finished writing my blog, I will update once I finish writing it.
@allentertainmentin1565 3 жыл бұрын
what should we do reduce this?how can we balance it?
@johnsonwelch1224 5 жыл бұрын
Great share! I found one helpful article related to this. The blog discusses how to implement SQL Server disk space and implement alert system: www.sqlserverlogexplorer.com/monitor-sql-server-disk-space-and-implement-alert/ Keep Reading!
@ab5sr 6 жыл бұрын
You didnt show how to set immediate sync\allow anonymous to zero: EXEC sp_changepublication @publication = 'Forest', @property = N'allow_anonymous', @value = 'false' GO EXEC sp_changepublication @publication = 'Forest', @property = N'immediate_sync', @value = 'false' GO
@michelleurbano0809 8 ай бұрын
Hello, am I right to alter the properties first on the affected publication before proceeding to add the articles right?
@theuserwanted 6 жыл бұрын
what is the reason it generate snapshot only for one table which is not in the subscriber? can you explain? to summarize I include the article first then generate snapshot? or there is/are some other step? thanks in advance.
@shovon100 6 жыл бұрын
you have to keep following properties disabled. otherwise old article will be regenerated on subscriber --Run on your publication database EXEC sp_changepublication @publication = 'test', --Enter your publication_name @property = 'allow_anonymous' , @value = 'false' GO EXEC sp_changepublication @publication = 'Test', --Enter your publication name @property = 'immediate_sync' , @value = 'false' GO -- then generate snapshot --then enable it back --Run on your publication database EXEC sp_changepublication @publication = 'test', --Enter your publication_name @property = 'allow_anonymous' , @value = 'true' GO EXEC sp_changepublication @publication = 'Test', --Enter your publication name @property = 'immediate_sync' , @value = 'true' GO