Monday, March 12, 2012
Help with "like" or "wildcard" during a parameter entry.
My trouble - I have a report that uses a parameter field to show a history of a whatever number is entered into the parameter when the report is accessed. I would like to add a "like" or "wildcard" to this parameter filed.
Example:
Parameter entered = ED35A100
The results are correct I get a history of the number ED35A100
However, I would like to enter the parameter = ED35*
and get results like ED35A100, ED35C100, ED35A200, etc.
Any help on how to accomplish this would be greatly appreciated.maybe this will work...lookslike({Fieldname},"*{?Parameter}*") then go to Report...Select Expert then choose the Fieldname then in the drop down key choose Is True
Sunday, February 26, 2012
Help SQL 2K Security :-) DBA's
Here goes another wired on... Currently I have a local test SQL server setup
on my PC. I need to give access to another (entry, verrrrrryyyy entry level)
programmer access to my local server (READ ONLY). but here goes the problem,
I discovered that the employee replicated my db and left it open causing
security issues, since the data contains lots of sensitive data. (credit
cards, soc sec, emp names, etc). Is theirs a way in SQL server to assign
field level security? for example : I want to give him access to employee
names in the employee db, but I don't want him to be able to view employees
socials? the same with customers and credit card information or to restrict
him from exporting any data/scripts. any ideas'
Thanks in advance
AlexThank u!!!!
"alex" <hjhjjhhj@.ghghhg.com> wrote in message
news:%23LWLPaEWDHA.1480@.tk2msftngp13.phx.gbl...
> Hello everyone,
> Here goes another wired on... Currently I have a local test SQL server
setup
> on my PC. I need to give access to another (entry, verrrrrryyyy entry
level)
> programmer access to my local server (READ ONLY). but here goes the
problem,
> I discovered that the employee replicated my db and left it open causing
> security issues, since the data contains lots of sensitive data. (credit
> cards, soc sec, emp names, etc). Is theirs a way in SQL server to assign
> field level security? for example : I want to give him access to employee
> names in the employee db, but I don't want him to be able to view
employees
> socials? the same with customers and credit card information or to
restrict
> him from exporting any data/scripts. any ideas'
> Thanks in advance
> Alex
>|||"alex" <hjhjjhhj@.ghghhg.com> wrote in message
news:eVCvrHFWDHA.2008@.TK2MSFTNGP11.phx.gbl...
> Thank u!!!!
>
> "alex" <hjhjjhhj@.ghghhg.com> wrote in message
> news:%23LWLPaEWDHA.1480@.tk2msftngp13.phx.gbl...
> > Hello everyone,
> >
> > Here goes another wired on... Currently I have a local test SQL server
> setup
> > on my PC. I need to give access to another (entry, verrrrrryyyy entry
> level)
> > programmer access to my local server (READ ONLY). but here goes the
> problem,
> > I discovered that the employee replicated my db and left it open causing
> > security issues, since the data contains lots of sensitive data. (credit
> > cards, soc sec, emp names, etc). Is theirs a way in SQL server to assign
> > field level security? for example : I want to give him access to
employee
> > names in the employee db, but I don't want him to be able to view
> employees
> > socials? the same with customers and credit card information or to
> restrict
> > him from exporting any data/scripts. any ideas'
> >
> > Thanks in advance
> >
> > Alex
> >
> >
I have to add one more note to this even though you've gotten your answer
and probably moved on. You said you have a "local test SQL server" setup.
You should never have legitimate, sensitive customer/employee information in
a test database. There's just no need for it, and you're taking a huge risk
of that information falling into the wrong hands. Scramble or remove the
data in the sensitive columns immediately.
If you need a legitimate CCN or SSN for testing (such as validation
routines) then pull out your wallet and use your own. Risking compromise of
a customer or employee's personal information is just insane.
Ryan LaNeve
Sunday, February 19, 2012
HELP required
I am deleting a database but I am not seeing any entry in server logs or in event viewer. and same thing is happens when I am deatching a database.
Can any body tell me the way through which I can know when a particualr database was deleted or deatched.
Hi derek3060,
Informatin should be logged to master.ldf when you delete one database from your database engine. Likewise, when you detach a database from a server, same information should be logged to the database's ldf file. However, ldf file is designed to be used by sql server system only and we have no way to read/write file(microsoft does not supply such an approach).
As a work around, i would suggest you try sql server profile. You can create a new trace with sql profil, set up some filters, then all the delete database\detach database behavior will be logged (if you do want to log those behaviors)
Hope my suggesiton helps
|||Yes surely your suggestion has helped.Thanks