I've set up my 'non-sa' account as owner of a particular db (sql2k sp2). I was probably logged in as sa when I created the db using DTS from an existing db.
When I connect from my workstation using MSAccess2k via an odbc connection using the non-sa account i find that I don't have ability to create new records. If I connect as sa i can.
looking at EM's Users for that db my non-sa login has checks for 'public' and 'db_owner'. I didn't (don't) think any of the other roles are anything more than subsets of db_owner, yes? So why isn't being owner good enough for Access.
My primary concern here isn't so much connecting via Acess...the db exists only to give stuff to IIS/web pages. I'm wondering if this indicates other things that may bite my butt going forward.
How can IT departments tackle the challenges of a Big Data world? This white paper provides a roadmap to success and helps companies ensure that all their data is safe and secure, no matter if it resides on-premise with physical or virtual machines or in the cloud.
I wrote this interesting script that really help me find jobs or procedures when working in a huge environment. I could I have written it as a Procedure but then I would have to have it on each machine or have a link to a server-related search that …
Everyone has problem when going to load data into Data warehouse (EDW). They all need to confirm that data quality is good but they don't no how to proceed.
Microsoft has provided new task within SSIS 2008 called "Data Profiler Task". It solve th…
Using examples as well as descriptions, and references to Books Online, show the documentation available for datatypes, explain the available data types and show how data can be passed into and out of variables.