Database

sql server 2008 table convert to xml files

28-Oct-12 23:33

Azher.Cybertech wrote:
yes i m familiar with join concept. bt i doesn't work for my requirement

I'm sure the examples don't work as-is. You'll need to write some Sql to gather the required results Smile | :)

Bastard Programmer from Hell Suspicious | :suss:

if you can't read my code, try converting it here[^]

shannya25-Oct-12 20:48

shannya

25-Oct-12 20:48

sql server 2008 table convert to xml files

Ingo25-Oct-12 23:51

25-Oct-12 23:51

shannya wrote:
sql server 2008 table convert to xml files

Is that a statement or a question?

If it's a statement, tell us more.

If it's a question look herehere. Roll eyes | :rolleyes:

By the way, it would be more polite to tell us what do you want to know and ask a real question. Thumbs Up | :thumbsup:

------------------------------
Author of Primary ROleplaying SysTem

How do I take my coffee? Black as midnight on a moonless night.
War doesn't determine who's right. War determines who's left.

kankeyan26-Oct-12 0:31

kankeyan

26-Oct-12 0:31

select*from <Table Name> for xml path ('Head')

select*from <Table Name> for xml path ('Head') ,root('Title')

select*from <Table Name> for xml raw

try like this there are more formats

modified 26-Oct-12 15:29pm.

Ingo26-Oct-12 2:14

26-Oct-12 2:14

Seems that you inserted html code that corrupts the output of codeproject. The topics after yours are missing and if I open your answer I see the others again but displayed wrong!

------------------------------
Author of Primary ROleplaying SysTem

How do I take my coffee? Black as midnight on a moonless night.
War doesn't determine who's right. War determines who's left.

kankeyan26-Oct-12 2:29

kankeyan

26-Oct-12 2:29

select*from for xml path ('Head')

select*from for xml path ('Head') ,root('Title')

select*from for xml raw

try like this there are more formats

Application / Database user management

Joy Sinha22-Nov-12 20:21

Joy Sinha

22-Nov-12 20:21

(SELECT * from [db].[schema].[tbl] FOR XML PATH(''),ROOT(''))

Koshbert25-Oct-12 8:02

Koshbert

25-Oct-12 8:02

Hello All,

When designing an application, desktop or web, what is the best way to manage users that must access a database?

Is it better to have a single group that all users belong to and let the application manage all the security?

Or setup different groups with different permissions on the database and then associate users with that and whatever security the database can't manage handle that in the application?

Or is there a third way that I am just not seeing?

Thanks,

Koshbert

David Mujica25-Oct-12 9:37

David Mujica

25-Oct-12 9:37

You will get answers for both methods.
1) Create users and handle security in the database
2) Create users in the application and connect with one user to the database.

There are pluses and minuses for both situations, however, consider this ...

Given a website like Facebook, you can create an account and have some set of permissions.
Do you really think it is creating a database user on the backend? Hmmm ... Probably not.

The real answer is up to you. You can do it either way.

I personally create one user in the database and handle all the security in the application.

Good luck. Thumbs Up | :thumbsup:

Michael Potter25-Oct-12 11:53

Michael Potter

25-Oct-12 11:53

I agree with David.

I usually create users/rights as structures in the database and use one SQL user/password to access the database.

I do break this rule when security is a one shot item -> You either have full access or you have zero access. In this case I won't go to the trouble to create user/rights structures and just use standard group security on the database.

Koshbert26-Oct-12 5:37

Koshbert

26-Oct-12 5:37

So then you guys have a table with user ids and a hash for the password that is used for logging into the application and everyone is associated with the one database user id.

That makes the database management piece pretty easy.

So what is the downside to this approach?

Thanks,

Koshbert

Michael Potter29-Oct-12 3:31

Michael Potter

29-Oct-12 3:31

The only downside is adding development complexity. You need to manage rights in the application which requires the development of objects manage users and thier rights.

Koshbert26-Oct-12 8:55

Koshbert

26-Oct-12 8:55

Follow up question:

For desktop applications how do you keep the single user id / password in sync? Alot of people for good reason want to change the supplied default password so hard coding it would be a bad idea.

Is this kind of design pattern covered in a blog, article or book anywhere online?

Thanks,

Koshbert

Can I use "Create Domain" in Sql Server 2008?

Michael Potter29-Oct-12 3:46

Michael Potter

29-Oct-12 3:46

I work in a closed environment and have no applications in third party hands so changing the db password is not an issue.

Not sure how I would handle an application at other sites. Even encrypting a connection string would require a hardcoded key somewhere along the line.

WebMaster25-Oct-12 2:39

WebMaster

25-Oct-12 2:39

Hello

I am trying to execute this query:

SQL

Create  Domain  Email
As
    Varchar(255) Check (Position('@', Value) > 1)

But the below error will occur:

Unknown object type 'Domain' used in a CREATE, DROP, or ALTER statement.

SignatureNotFoundException

Eddy Vluggen25-Oct-12 4:09

25-Oct-12 4:09

..Sql Server does not know about "domains". It hosts tables, records, and you can create things like databases and tables.

How did you expect this to work? Simply throw in the word "domain" and pray that Sql knows what you want?

Computers don't work like that. You learn the computers language if you want things from it, not the other way around.

Bastard Programmer from Hell Suspicious | :suss:

if you can't read my code, try converting it here[^]

Ingo25-Oct-12 4:18

25-Oct-12 4:18

Eddy Vluggen wrote:
Sql Server does not know about "domains". It hosts tables, records, and you can create things like databases and tables.

A DOMAIN in SQL is defined as a set of values for a given attribute! So, of course SqlServer knows something about domains! It just called different!

In SqlServer you use ADD CONSTRAINT to simulate domains.

------------------------------
Author of Primary ROleplaying SysTem

How do I take my coffee? Black as midnight on a moonless night.
War doesn't determine who's right. War determines who's left.

Eddy Vluggen25-Oct-12 5:41

25-Oct-12 5:41

Goood morning Big Grin | :-D

It is, you're right, stupid mistake. ..and twice as bad given the tone.

Bastard Programmer from Hell Suspicious | :suss:

if you can't read my code, try converting it here[^]

WebMaster28-Oct-12 22:33

WebMaster

28-Oct-12 22:33

I saw some samples for creating UDDTs using Create Domain... .
I didn't that word from myself.

SignatureNotFoundException

Eddy Vluggen25-Oct-12 4:11

25-Oct-12 4:11

..now that I had my rant, let's try and find an answer to your problem. For that, we first need to get a clear description on the problem itself; as is know, I can only guess at what you are trying to do.

Are you trying to store email-adresses? (creating them is done in another server)
Create a login? (Google for "create login")
Something else?

Bastard Programmer from Hell Suspicious | :suss:

if you can't read my code, try converting it here[^]

WebMaster28-Oct-12 22:42

WebMaster

28-Oct-12 22:42

I am trying to create a UDDT. I know how to do it using "Create Type", but I have also saw some query like I have posted.

SignatureNotFoundException

Ingo25-Oct-12 4:24

25-Oct-12 4:24

Well, as I know, DOMAIN is not implemented in SqlServer but as a SQL-Language element it's a reserved word.
You can use ADD CONSTRAINT to check the values (google for sql server add constraint, there are lot of samples).

------------------------------
Author of Primary ROleplaying SysTem

How do I take my coffee? Black as midnight on a moonless night.
War doesn't determine who's right. War determines who's left.

Member 954700625-Oct-12 18:21

Member 9547006

25-Oct-12 18:21

Perhaps an alias data type ?

http://msdn.microsoft.com/en-us/library/ms175007(v=sql.100).aspx