|
Add Group By ProductName, Field2
after the where clause
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Hi everyone! I need to grant permission on a table in a database to a database role in another database.
I have client database containing information about clients. In another database, I have roles for different departments. Now I need to grant permission on specific tables in the client database to roles or departments which are located in another database.
I have been struggling for a solution but have not succeeded. Is there any way to accomplish this task? Please help.
|
|
|
|
|
Dan_K wrote: Now I need to grant permission
Is some kind of permission problem ocurring now that wasn't occuring before? Maybe I'm missing the obvious.
Chris Meech
I am Canadian. [heard in a local bar]
In theory there is no difference between theory and practice. In practice there is. [Yogi Berra]
posting about Crystal Reports here is like discussing gay marriage on a catholic church’s website.[Nishant Sivakumar]
|
|
|
|
|
I use two database one is local server because there internet is not available. another is on global server my problem is that how to update local database on global database.
|
|
|
|
|
Do some research into "replication" this may meet your needs or you can script the data transfer. There is no simple way to "merge" 2 databases. You may also look into Data Compare from Red Gate but I don't think that is going to be the tool.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
What database server are you using?
|
|
|
|
|
|
|
You can also user the SQL import Export wizard to transfer the data from one database to other database either table wise of bulk
|
|
|
|
|
Yeah that's me, I have sql server express installed on my local machine so I can test stuff without polluting the development server. So I have not needed it for ages, not trying anything new on a database level recently.
Well now I want to create a test database and I mislaid the blasted sa password and I don't have enough rights on the dammed thing. Apparently the only was is to re install the database Gggrrrr
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Which is why you dont use SQL Authentication.
I feel your pain. Been there.
|
|
|
|
|
|
Now that I did not know, have 5 for he link, thank you, you have justified the rant...
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
hi every buddy
i hav e a problem to create new user in sql server 2008 r2
i create a user and my user created.
and i logined with this user succesfully. but when i want to create a new database in sqlserver authentication mode
i facing with this problem
"Create Database permission Denied in DataBase master.[error 262]"
thanks for any help.
|
|
|
|
|
You need dbo permission on the Master database (I think) to be able to create a database. Do some research on what permissions are available in SQL server it will be very enlightening.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
grant server role with sysadmin
|
|
|
|
|
HOW TO CONNECT DATABASE TO .NET PROJECT
|
|
|
|
|
Don't write in capital letters - looks like you're shouting. Try the manual[^].
|
|
|
|
|
Hi All,
Can someone enlighten me as to why you would need a default value of 0 on a tinyint field.
I'm not even sure if you do need to set it on all tinyint fields but I was told this by our previous DBA.
If the field "Allows Nulls", can it by default be left null without causing any problems?
Thanks,
JammoD
|
|
|
|
|
The same reason you'd want (need?) a default on any field - to save space.
You see, by making a field nullable it requires 1 extra byte of info per field per record to determine if the field is null.
|
|
|
|
|
I don't see saving 1 extra byte per field a relevant issue. I suspect it is an internal convention, default to 0 and the dba/developers/coder/us lazy bastards do not need to test for null values.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
If both of the following are true then it could be relevant.
1. High volume system.
2. Many columns of this type. (Really high volumes even a couple might be relevant.)
However since the vast majority of systems will never have both of these it isn't going to be relevant.
Mycroft Holmes wrote: and the dba/developers/coder/us lazy bastards do not need to test for null values.
And maybe a bit stupid too since zero and null are not necessarily the same thing.
|
|
|
|
|
jschell wrote: since zero and null are not necessarily the same thing
The is always a debating point, do we allow null to represent a value in a numeric field?
As I'm a lazy sod I disallow null in numeric field as my default position and until the business can convince me otherwise that is the way it is designed.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Thanks guys answers my question!
|
|
|
|
|
Can some one explain to me what a Staging area is ?
And I also want to know whether it is a database, a file, or something else altogether..?
|
|
|
|