Database group

In sql server 2005 you have a group of databases called System Databases -
Is it possible to create your own database group?

Best regards,

Jakobsgaard
If you mean in the Object Explorer tree, no not in this version.|||

This seems like a tease. Is this in grouping the works?

I am coming from an Oracle perspective where the world revolves around Schemas and Tablespaces.

The Database group makes sense to me.

Thanks

Database group

In sql server 2005 you have a group of databases called System Databases -
Is it possible to create your own database group?

Best regards,

Jakobsgaard
If you mean in the Object Explorer tree, no not in this version.|||

This seems like a tease. Is this in grouping the works?

I am coming from an Oracle perspective where the world revolves around Schemas and Tablespaces.

The Database group makes sense to me.

Thanks

Database for my site

Hello. I am not new to SQL Server but want to setup my own web site with a directory like 123aspx.com or like 411asp.net. I am not sure how to go about the structure of the data so I am going to try several different structures to hold the resources. Does anyone have any experience setting something like this up? I would take any ideas on the subject too. The site that I will hopefully have up and running is located at http://www.thedotnetzone.com.

Thanks in advance

ChadWhat kind of informations you need

______________
Paulo Gonalves

Database dump and load script

Hi,
Is anyone using a custom script, or anything else that helps allow software
developer's do their own database dump and loads rather than having to ask a
DBA every time? What are people using to allow this functionality?
We are looking to move this task from a DBA responsibility to allow for the
users to do their own database dumps and loads in the test and development
environments. The one problem we have is that the databases were not all
standardized to have the exact file path names when they are created. For
example, F:\MSSQL\data\<filename>.mdf. Some of them might be
F:\MSSQL\default\data\<filename>.mdf, etc.
Does anyone have this capability automated for what I am looking for?
Thanks for any feedback.
CynthiaWe wrote some scripts that perform these operations. Essentially, a control
table is created and populated for each DB. When a restore need to be
performed, a row is inserted into a table where a recurring job picks it up
and looks into the control tables for the necessary information. The job
generates on OSQL script and prevents the need for the developers to have
those sorts of rights necessesary to perform restores(may not be an issue for
you)
Jeff
"Cynthia" wrote:
> Hi,
> Is anyone using a custom script, or anything else that helps allow software
> developer's do their own database dump and loads rather than having to ask a
> DBA every time? What are people using to allow this functionality?
> We are looking to move this task from a DBA responsibility to allow for the
> users to do their own database dumps and loads in the test and development
> environments. The one problem we have is that the databases were not all
> standardized to have the exact file path names when they are created. For
> example, F:\MSSQL\data\<filename>.mdf. Some of them might be
> F:\MSSQL\default\data\<filename>.mdf, etc.
> Does anyone have this capability automated for what I am looking for?
> Thanks for any feedback.
> Cynthia

Database dump and load script

Hi,
Is anyone using a custom script, or anything else that helps allow software
developer's do their own database dump and loads rather than having to ask a
DBA every time? What are people using to allow this functionality?
We are looking to move this task from a DBA responsibility to allow for the
users to do their own database dumps and loads in the test and development
environments. The one problem we have is that the databases were not all
standardized to have the exact file path names when they are created. For
example, F:\MSSQL\data\<filename>.mdf. Some of them might be
F:\MSSQL\default\data\<filename>.mdf, etc.
Does anyone have this capability automated for what I am looking for?
Thanks for any feedback.
Cynthia
We wrote some scripts that perform these operations. Essentially, a control
table is created and populated for each DB. When a restore need to be
performed, a row is inserted into a table where a recurring job picks it up
and looks into the control tables for the necessary information. The job
generates on OSQL script and prevents the need for the developers to have
those sorts of rights necessesary to perform restores(may not be an issue for
you)
Jeff
"Cynthia" wrote:

> Hi,
> Is anyone using a custom script, or anything else that helps allow software
> developer's do their own database dump and loads rather than having to ask a
> DBA every time? What are people using to allow this functionality?
> We are looking to move this task from a DBA responsibility to allow for the
> users to do their own database dumps and loads in the test and development
> environments. The one problem we have is that the databases were not all
> standardized to have the exact file path names when they are created. For
> example, F:\MSSQL\data\<filename>.mdf. Some of them might be
> F:\MSSQL\default\data\<filename>.mdf, etc.
> Does anyone have this capability automated for what I am looking for?
> Thanks for any feedback.
> Cynthia

Database dump and load script

Hi,
Is anyone using a custom script, or anything else that helps allow software
developer's do their own database dump and loads rather than having to ask a
DBA every time? What are people using to allow this functionality?
We are looking to move this task from a DBA responsibility to allow for the
users to do their own database dumps and loads in the test and development
environments. The one problem we have is that the databases were not all
standardized to have the exact file path names when they are created. For
example, F:\MSSQL\data\<filename>.mdf. Some of them might be
F:\MSSQL\default\data\<filename>.mdf, etc.
Does anyone have this capability automated for what I am looking for?
Thanks for any feedback.
CynthiaWe wrote some scripts that perform these operations. Essentially, a control
table is created and populated for each DB. When a restore need to be
performed, a row is inserted into a table where a recurring job picks it up
and looks into the control tables for the necessary information. The job
generates on OSQL script and prevents the need for the developers to have
those sorts of rights necessesary to perform restores(may not be an issue fo
r
you)
Jeff
"Cynthia" wrote:

> Hi,
> Is anyone using a custom script, or anything else that helps allow softwar
e
> developer's do their own database dump and loads rather than having to ask
a
> DBA every time? What are people using to allow this functionality?
> We are looking to move this task from a DBA responsibility to allow for th
e
> users to do their own database dumps and loads in the test and development
> environments. The one problem we have is that the databases were not all
> standardized to have the exact file path names when they are created. For
> example, F:\MSSQL\data\<filename>.mdf. Some of them might be
> F:\MSSQL\default\data\<filename>.mdf, etc.
> Does anyone have this capability automated for what I am looking for?
> Thanks for any feedback.
> Cynthia

Database design issue

hi,
we are designing a web application for defect tracking. In this for each
project the user can choose his own template for writing testcases... we nee
d
to persist this data.As you can see there can be any number of textbox in
that template.
We suggested two models,
1. a table with a text column holding the XML format which contains the
template with data .
2. a table containing variable name and value as column such that a crosstab
query would return the template values for a particular project.
But the .net developers suggest creating the table on the fly while the
template is chosen.. Please note once a template is chosen for the project i
t
remains the same.
which one would be better?If you are not going to query within the template and get a subset of
testcases.you can use the XML method.But we don't have validation techniques
for the XML schema in SQL 2000. So if that's not a problem, then storing as
XML should be the best option.
But if you have cases like, the user will select testcase 5 in the template
and edit it and save it, then you are better off with the second option
because manipulation of XML is tough.
In case of option 1, You can take out the XML and edit it and replace the
old one with the new one. If thats fine, then go for option 1.
Hope this helps.