Home
Help
Register
Log in

Search

 
   Active Threads  

You are here: Home > LLBLGen Pro > Designer> SQL Server 2016 and LLBLGen v1.0.2004.2
 

Pages: 1
Designer
SQL Server 2016 and LLBLGen v1.0.2004.2
Page:1/1 

  Print all messages in this thread  
Poster Message
Shawn1763
User



Location:

Joined on:
23-Oct-2018 18:01:47
Posted:
1 posts
# Posted on: 23-Oct-2018 18:15:54.  
First of all, I know this version is very old, but I'm supporting an older application! Sad

We have moved our Financial system from an Oracle DB to a SQL Server 2016 version. I need to build my LLBLGen project for certain tables in the new database owned by, let's say, "FINANCE" user (dbo). I've been assigned a login "USER1", for example. Does "USER" have to be a member of the "db_owner" role, in order to read the schema catalog?

If "USER1" is a member of the "db_owner" role, then how can DB Admin restrict the catalog information only to handful of tables to the "USER1"?

Thanks.
  Top
Walaa
Support Team



Location:

Joined on:
21-Aug-2005 16:03:48
Posted:
14464 posts
# Posted on: 23-Oct-2018 22:50:07.  
First things first.

v. 1.x is out of support.
Plus it doesn't support SQL Server 2016.


  Top
Otis
LLBLGen Pro Team



Location:
The Hague, The Netherlands
Joined on:
17-Aug-2003 18:00:36
Posted:
37377 posts
# Posted on: 24-Oct-2018 10:01:57.  
You have to upgrade to a later version of LLBLGen Pro to get support for newer versions of SQL Server as the meta data format changed, sorry.
Frans Bouma
LLBLGen Pro / ORM Profiler Lead Developer | Blog | Twitter
 
Top
Pages: 1  


Powered by HnD ©2002-2007 Solutions Design
HnD uses LLBLGen Pro

Version: 2.1.12172008 Final.