database error -help

I'm using sqlserver 2000 and when i go to enterprise
manager and click on one of the database it is giving me
internet explorer script error. it is refering to
c:/programfiles/mssql2000/80/tools/bin/resources/1033/sqlmm
c.rll/tabs.html
Can anyone help please?Try switching from taskpad view to anything else, select
the database (should be no error), then go back to taskpad
view. Of the top of my head, this is the one issue I can
think of...
>--Original Message--
>I'm using sqlserver 2000 and when i go to enterprise
>manager and click on one of the database it is giving me
>internet explorer script error. it is refering to
>c:/programfiles/mssql2000/80/tools/bin/resources/1033/sqlm
m
>c.rll/tabs.html
>Can anyone help please?
>.
>

Database Documentation is important

Hi
As a project manager,
=B7 Do you have an up-2-date overview of the database structure?
=B7 What will you do when your database administrator leaves your
company?
=B7 Are you willing to pay extra hours to update the database
information?
As a developer,
=B7 Do you spent too much hours on writing boring database
documentation?
=B7 Are you tired of not having the latest DB-information?
More info on www.dbmanual.com and download the free evaluation version.
FrederikI took a look at your live demo, and it seems to offer no advantages over
just browsing a database in Enterprise Manager. Explain the "documentation"
aspect of it.
<frederik@.dbmanual.com> wrote in message
news:1140473260.871832.218700@.g14g2000cwa.googlegroups.com...
Hi
As a project manager,
Do you have an up-2-date overview of the database structure?
What will you do when your database administrator leaves your
company?
Are you willing to pay extra hours to update the database
information?
As a developer,
Do you spent too much hours on writing boring database
documentation?
Are you tired of not having the latest DB-information?
More info on www.dbmanual.com and download the free evaluation version.
Frederik

Database Documentation

Hi guys, my manager asked me that to do documentation; right now we are using MSSQL SERVER 2005 Databases, here you assume I am new to make documents on any database but good idea about databases currently that data warehouse in development environment need to done this documentation before go on test environment . So that way you advise me to prepare a document.

Here is my main concerned how to start and what things should we keep in mind while preparing document (what are measurements).if you any prepared documents could help to start or there tool we should use (power point) them. any help appreciated

Things to include in DB documentation, and some suggested sources:

1.Server where DB is implemented; SQL Server version used, and required (for example SQL 2005 SP1 because of fix to XXX).

2.Database design - in an ideal world, you should have a ERD for a

database design before the database was created. This may have been

done in an external tool like ERWin, Rational Rose, PowerDesigner etc.

etc. You can also use the Database Diagram tool in Enterprise manager

(sql 2000, not sure about SQL 7.0) or SQL Server Management Studio

(SQL2005) to create these diagrams. The physical DB model (or

design, or ERD, - whatever your preferred name), is, imho, the single

most important piece of documentation about a database;

3. Volumetrics - this is a field on it's own, and one that is often

largely ignored (until a problem occurs!). This is about predicting the

sizing of a database, so as to ensure that the production server has

sufficient capacity when initially created, and sufficient space during

the database life. Since space addition can be a difficult/time

consuming activity (for example, ordering disks, taking server off-line

to add them, or getting drives purchased and added to a SAN and

allocated to the LUNs for you server, if you have a SAN), you really

want to know how much space you need, and when you are going to need

more. There are 2 large sections to this: predictions based on

assumptions, and forecasts made on trend analysis.

- predictions are done during design and creation phase. For example,

the business should have some kind of idea about the viability of a

system. In that, they would, hopefully, have some kind of expectations

regarding usage - for example: We expect 2000 orders a day, typically

of an average of 13.5 products. That already tells us we can expect

2000 rows in our order table, on a daily basis, and 27000 rows in the

OrderItem table. Extrapolation that further, based on 21*12 working

days a year, and we have a prediction of 504 000 rows in the order

table at year end, and 6 804 000 rows in the OrderItem table. This kind

of information can be used to generate an estimated size for the

database, so we can ensure that the database will have enough space on

the brand new server the business bought

- forecasts are done on an on-going basis and are a pro-active measure

by the DBAs in production to determine real growth of a database. So,

after the first month, for example, the dba's note that the ORder table

has 60000 entries, and the Orderitem table has 900 000 rows. Based on

that, they can forecast that the year end sizes will now be 720 000

order rows, and 10 800 000 OrderItems. The goods news is that the

business is doing 42% more orders, at that point in time, that

predicted (see the prediction above), and has sold 58% more Items. They

can use the extra money to buy some disk space, because the forecast

says that at 60000 order per month, the DB is going to be the size that

was predicted for year-end, after less than 9 months (9*60000 = 540 000

> 504 000, for example).

I haven't covered a discussion about the increase in volumes on the

underlying server resources (for example, are the batch jobs able to

finish processing within the agreed SLA's, now that we are doing 2857

orders per day? Do we have periods where this causes excessive load on

the server? These things are NOT (imho) part of a DB document, but they

do flow out of the forecasts that are being done. A final comment on

forecasts above is that, when they are done regularly, you can also do

trend analysis - this is use for technical people - for example, orders

are growing by 10% each month, so in fact that 9 month prediction is

too far away - it needs to be earlier

(60000+66000+72600+79860+87846+96630.6+106293.66=569230 after 7 months).

4. Access - who needs access, to what. For example, Users required, and

which stored procedures they need to execute. Hopefully, there is

little of no dorect table access, but that can also be listed. This can

be done in a matrix in excel:

User -> UserA UserB

Object
TableA - S

TableB - -

SP_1 - Ex

SP_2 - Ex

SP_3 Ex ExGr

SP_4 Ex -

And a key that defines the meanings:

S = Select (D=Delete,U=Update,I=Insert)

Ex = Execute

ExGr = Execute with Grant

etc. etc. These are examples - create as seems relevant.

5. Maintenance. what is the DRP strategy - do you have off-site

backups, how often, are they tested? Do you do regular maintenance (db

indexdefrag's etc) and if so, are they maintenance plans, or specific

jobs?

depending on the target audience for the document (for example someone

using it to rebuild servers in a disaster), you could consider adding

reference to the Source Control system, so that if the database needs

to be rebuilt, they know where to get relevant code.

hmm - well that was off the top of my head. Hopefully it gives you a

good palce to start. I'd be interested to see the additional items

other people suggest.|||

You might want to check out SqlSpec. It will generate documentation for any SQL 2000 or 2005 database. It's very reasonably priced at $50, a fraction of other data dictionary software out there.

see www.elsasoft.org for more info.

|||Interesting. It does seem quite useful and covers much of what I listed|||

You might be interested in checking out dbdesc as well. This tool documents SQL Server databases and you can fully customize its reports as it uses XSL templates to generate the final files. It has built-in templates to generate Word 2003, RTF, HTML, XML and PDF reports.

It was reviewed by Mike Gunderloy (Larkware News) here.

|||

Hi, Geth. Have you gotten everything you need on this subject? If so, you can close the thread, if not, let us know and we'll try to give you some more help.

Buck Woody

|||ERm. I'm happy, but I wasn't the thread starter. Can I cl,ose someone else's thread?|||

You're right! My bad. I'm not sure if you can mark it "happy" or not. I'll ask the right person this time...

|||

Hello - did you get everything you needed? I have some more info on building your own documentor here:

http://www.informit.com/guides/content.asp?g=sqlserver&seqNum=108&rl=1

If you've found these answers to be helpful, you can mark this thread as "answered". Thanks!

|||IAM Happy we can close this thread

Database Documentation

Hi guys, my manager asked me that to do documentation; right now we are using MSSQL SERVER 2005 Databases, here you assume I am new to make documents on any database but good idea about databases currently that data warehouse in development environment need to done this documentation before go on test environment . So that way you advise me to prepare a document.

Here is my main concerned how to start and what things should we keep in mind while preparing document (what are measurements).if you any prepared documents could help to start or there tool we should use (power point) them. any help appreciated

Things to include in DB documentation, and some suggested sources:

1.Server where DB is implemented; SQL Server version used, and required (for example SQL 2005 SP1 because of fix to XXX).

2.Database design - in an ideal world, you should have a ERD for a

database design before the database was created. This may have been

done in an external tool like ERWin, Rational Rose, PowerDesigner etc.

etc. You can also use the Database Diagram tool in Enterprise manager

(sql 2000, not sure about SQL 7.0) or SQL Server Management Studio

(SQL2005) to create these diagrams. The physical DB model (or

design, or ERD, - whatever your preferred name), is, imho, the single

most important piece of documentation about a database;

3. Volumetrics - this is a field on it's own, and one that is often

largely ignored (until a problem occurs!). This is about predicting the

sizing of a database, so as to ensure that the production server has

sufficient capacity when initially created, and sufficient space during

the database life. Since space addition can be a difficult/time

consuming activity (for example, ordering disks, taking server off-line

to add them, or getting drives purchased and added to a SAN and

allocated to the LUNs for you server, if you have a SAN), you really

want to know how much space you need, and when you are going to need

more. There are 2 large sections to this: predictions based on

assumptions, and forecasts made on trend analysis.

- predictions are done during design and creation phase. For example,

the business should have some kind of idea about the viability of a

system. In that, they would, hopefully, have some kind of expectations

regarding usage - for example: We expect 2000 orders a day, typically

of an average of 13.5 products. That already tells us we can expect

2000 rows in our order table, on a daily basis, and 27000 rows in the

OrderItem table. Extrapolation that further, based on 21*12 working

days a year, and we have a prediction of 504 000 rows in the order

table at year end, and 6 804 000 rows in the OrderItem table. This kind

of information can be used to generate an estimated size for the

database, so we can ensure that the database will have enough space on

the brand new server the business bought

- forecasts are done on an on-going basis and are a pro-active measure

by the DBAs in production to determine real growth of a database. So,

after the first month, for example, the dba's note that the ORder table

has 60000 entries, and the Orderitem table has 900 000 rows. Based on

that, they can forecast that the year end sizes will now be 720 000

order rows, and 10 800 000 OrderItems. The goods news is that the

business is doing 42% more orders, at that point in time, that

predicted (see the prediction above), and has sold 58% more Items. They

can use the extra money to buy some disk space, because the forecast

says that at 60000 order per month, the DB is going to be the size that

was predicted for year-end, after less than 9 months (9*60000 = 540 000

> 504 000, for example).

I haven't covered a discussion about the increase in volumes on the

underlying server resources (for example, are the batch jobs able to

finish processing within the agreed SLA's, now that we are doing 2857

orders per day? Do we have periods where this causes excessive load on

the server? These things are NOT (imho) part of a DB document, but they

do flow out of the forecasts that are being done. A final comment on

forecasts above is that, when they are done regularly, you can also do

trend analysis - this is use for technical people - for example, orders

are growing by 10% each month, so in fact that 9 month prediction is

too far away - it needs to be earlier

(60000+66000+72600+79860+87846+96630.6+106293.66=569230 after 7 months).

4. Access - who needs access, to what. For example, Users required, and

which stored procedures they need to execute. Hopefully, there is

little of no dorect table access, but that can also be listed. This can

be done in a matrix in excel:

User -> UserA UserB

Object
TableA - S

TableB - -

SP_1 - Ex

SP_2 - Ex

SP_3 Ex ExGr

SP_4 Ex -

And a key that defines the meanings:

S = Select (D=Delete,U=Update,I=Insert)

Ex = Execute

ExGr = Execute with Grant

etc. etc. These are examples - create as seems relevant.

5. Maintenance. what is the DRP strategy - do you have off-site

backups, how often, are they tested? Do you do regular maintenance (db

indexdefrag's etc) and if so, are they maintenance plans, or specific

jobs?

depending on the target audience for the document (for example someone

using it to rebuild servers in a disaster), you could consider adding

reference to the Source Control system, so that if the database needs

to be rebuilt, they know where to get relevant code.

hmm - well that was off the top of my head. Hopefully it gives you a

good palce to start. I'd be interested to see the additional items

other people suggest.|||

You might want to check out SqlSpec. It will generate documentation for any SQL 2000 or 2005 database. It's very reasonably priced at $50, a fraction of other data dictionary software out there.

see www.elsasoft.org for more info.

|||Interesting. It does seem quite useful and covers much of what I listed|||

You might be interested in checking out dbdesc as well. This tool documents SQL Server databases and you can fully customize its reports as it uses XSL templates to generate the final files. It has built-in templates to generate Word 2003, RTF, HTML, XML and PDF reports.

It was reviewed by Mike Gunderloy (Larkware News) here.

|||

Hi, Geth. Have you gotten everything you need on this subject? If so, you can close the thread, if not, let us know and we'll try to give you some more help.

Buck Woody

|||ERm. I'm happy, but I wasn't the thread starter. Can I cl,ose someone else's thread?|||

You're right! My bad. I'm not sure if you can mark it "happy" or not. I'll ask the right person this time...

|||

Hello - did you get everything you needed? I have some more info on building your own documentor here:

http://www.informit.com/guides/content.asp?g=sqlserver&seqNum=108&rl=1

If you've found these answers to be helpful, you can mark this thread as "answered". Thanks!

|||IAM Happy we can close this thread

database disappearence

All of a sudden all the databases under the SQL Server Enterprise Manager have disappeared. Any idea why and how to get them back? I 'm on SQL 2000 with SP3Damn Miracle thing again....

Close and restart EM...What happens?|||That sure is a miracle brett :)|||I though miracles were supposed to be good things? Sounds more like a voodoo curse to me.

Try waving a dead chicken over it.

Database Diagrams from SQL Server

In your experiences, what is the best way to create Database Diagrams?
SQL Server Enterprise Manager Diagrams or Visio?
In SQL Server Enterprise Manager, when I create a "Diagram" and then try to
"Autosize Selected Tables" it leaves a lot of white space at the top which
results in the Table printing over one page. Is there any way to control
this? Does that have something to do with my printer set-up? Even if I
click and drag the table to the top of the page, it automatically slides it
down again creating that white space.
If I Reverse Engineer the Table into Visio, the column attributes are not
showing up.
I welcome your opinions and your help is GREATLY appreciated.
Thanks!
wnfisba
My best way to do this is to use Visio Enterprise Edition (with
reeingineering tool). YOu have a good chance to do your modifications
in here and deploy them right away in the server. Another tool which is
often mentioned is Erwin - a database modelling solution.
HTH, Jens Suessmeyer.
|||When attempting to Reverse Engineer into Visio, I am not seeing the column
attributes. The column names are coming
over, but not their attributes. Can I change that?
Please let me know.
Thanks!
"Jens" wrote:

> My best way to do this is to use Visio Enterprise Edition (with
> reeingineering tool). YOu have a good chance to do your modifications
> in here and deploy them right away in the server. Another tool which is
> often mentioned is Erwin - a database modelling solution.
> HTH, Jens Suessmeyer.
>
|||I also prefer Visio (or Erwin or ERstudio or pretty much
anything) over the Diagram tool in Enterprise Manager.
In terms of the columns in Visio, that's just a setting you
can change. In Visio, open the diagram, go to the menu and
select Database, then Options, then Document. A database
document window pops up. On the tables tab, you can select
what is displayed for the tables in the diagram (which types
of columns, if you want to display data types, etc.).
-Sue
On Thu, 19 Jan 2006 11:50:02 -0800, "wnfisba"
<wnfisba@.discussions.microsoft.com> wrote:

>In your experiences, what is the best way to create Database Diagrams?
>SQL Server Enterprise Manager Diagrams or Visio?
>In SQL Server Enterprise Manager, when I create a "Diagram" and then try to
>"Autosize Selected Tables" it leaves a lot of white space at the top which
>results in the Table printing over one page. Is there any way to control
>this? Does that have something to do with my printer set-up? Even if I
>click and drag the table to the top of the page, it automatically slides it
>down again creating that white space.
>If I Reverse Engineer the Table into Visio, the column attributes are not
>showing up.
>I welcome your opinions and your help is GREATLY appreciated.
>Thanks!
>wnfisba

Database Diagrams export

Hi, Can someone help me?
I need to create a tree structured diagram of our Server databases. I know how to create diagrams via the Enterprise manager, but I don't know how I can export them into some format, that I can further work with (doc., txt.,etc.). Is there some other tool, then the one in enterprise manager?
Thanks in advance.
Magdalena.That may be helpful:

Script SQL Server 2005 diagrams to a file

Database diagrams

Can a Database Diagram be imported or exported so that the schema can be
shown to someone that does not have Enterprise Manager installed on their
system?
If so what tools can do this?
No; you can do a screen capture or print to a PDF, perhaps.
Adam Machanic
SQL Server MVP
http://www.datamanipulation.net
"Jim Abel" <JimAbel@.discussions.microsoft.com> wrote in message
news:65C71846-71F2-4875-B0C8-79C18104F5CF@.microsoft.com...
> Can a Database Diagram be imported or exported so that the schema can be
> shown to someone that does not have Enterprise Manager installed on their
> system?
> If so what tools can do this?

Database diagrams

Does anyone know if there is a way to export a database diagram from SQL
enterprise manager to either Microsoft visio or any other paint program?
thanx PapaniiHi,
The only way to export them out is via Copy and Paste or you can get a
graphic print driver (Postscript driver) and save the print to a file. Then
you may be able to import it into another program.
There is no option from SQL Sever to do this.
regards
Greg O
AGS SQL Server Documentation Builder - MS SQL Server
http://www.ag-software.com/ags_scribe_index.aspx
"Papanii Okai" <papanii58@.hotmail.com> wrote in message
news:uUesp8jBEHA.2600@.TK2MSFTNGP09.phx.gbl...
> Does anyone know if there is a way to export a database diagram from SQL
> enterprise manager to either Microsoft visio or any other paint program?
> thanx Papanii
>|||visio enterprise has the ability to Reverse Engineer your DB.
Visio will Build the ERD for you if you point it at your Database.
Greg Jackson
PDX, Oregon

Database diagrams

Can a Database Diagram be imported or exported so that the schema can be
shown to someone that does not have Enterprise Manager installed on their
system?
If so what tools can do this?No; you can do a screen capture or print to a PDF, perhaps.
Adam Machanic
SQL Server MVP
http://www.datamanipulation.net
--
"Jim Abel" <JimAbel@.discussions.microsoft.com> wrote in message
news:65C71846-71F2-4875-B0C8-79C18104F5CF@.microsoft.com...
> Can a Database Diagram be imported or exported so that the schema can be
> shown to someone that does not have Enterprise Manager installed on their
> system?
> If so what tools can do this?

Database diagrams

Can a Database Diagram be imported or exported so that the schema can be
shown to someone that does not have Enterprise Manager installed on their
system?
If so what tools can do this?No; you can do a screen capture or print to a PDF, perhaps.
Adam Machanic
SQL Server MVP
http://www.datamanipulation.net
--
"Jim Abel" <JimAbel@.discussions.microsoft.com> wrote in message
news:65C71846-71F2-4875-B0C8-79C18104F5CF@.microsoft.com...
> Can a Database Diagram be imported or exported so that the schema can be
> shown to someone that does not have Enterprise Manager installed on their
> system?
> If so what tools can do this?

Database design

How do I get my Database Design, my manager told me that there is an
option for the same to create it....
Is there any?
Please guide........
Regards,
Amit AroraScript?
select ordinal_position 'Seq',
cast(column_name as varchar(40)) 'Column',
isnull(character_maximum_length, numeric_precision) 'Size',
cast(data_type as varchar(12)) 'Type'
from information_schema.columns
where table_name = 'tests'
http://www.databaseanswers.com/data_models/index.htm -- examples
database design
<aroraamit81@.gmail.com> wrote in message
news:1147263655.365843.215460@.j73g2000cwa.googlegroups.com...
> How do I get my Database Design, my manager told me that there is an
> option for the same to create it....
> Is there any?
> Please guide........
> Regards,
> Amit Arora
>|||Nopes just needed the way to export my database deisgn, like you have
design diagram, so that I can show it to my manager
Thanks,
Amit Arora|||Print it?
<aroraamit81@.gmail.com> wrote in message
news:1147264818.029433.201190@.j33g2000cwa.googlegroups.com...
> Nopes just needed the way to export my database deisgn, like you have
> design diagram, so that I can show it to my manager
> Thanks,
> Amit Arora
>

Database design

How do I get my Database Design, my manager told me that there is an
option for the same to create it....
Is there any?
Please guide........
Regards,
Amit AroraScript?
select ordinal_position 'Seq',
cast(column_name as varchar(40)) 'Column',
isnull(character_maximum_length, numeric_precision) 'Size',
cast(data_type as varchar(12)) 'Type'
from information_schema.columns
where table_name = 'tests'
http://www.databaseanswers.com/data_models/index.htm -- examples
database design
<aroraamit81@.gmail.com> wrote in message
news:1147263655.365843.215460@.j73g2000cwa.googlegroups.com...
> How do I get my Database Design, my manager told me that there is an
> option for the same to create it....
> Is there any?
> Please guide........
> Regards,
> Amit Arora
>|||Nopes just needed the way to export my database deisgn, like you have
design diagram, so that I can show it to my manager
Thanks,
Amit Arora|||Print it?
<aroraamit81@.gmail.com> wrote in message
news:1147264818.029433.201190@.j33g2000cwa.googlegroups.com...
> Nopes just needed the way to export my database deisgn, like you have
> design diagram, so that I can show it to my manager
> Thanks,
> Amit Arora
>

Database data file does not auto-grow

Dear all,
We are using SQL2000 sp4 on Windows 2000 Svr.
We found one of the database size become zero in Enterprise manager.
We have checked the database setting and the database is already set
auto-growth, without limit, by 1000Mb each time.
The data file size reach 6G now.
Is there anything we miss? That's the first time we meet this case.
We have checked the Harddisk drive for the data file and it still have over
100G space.
IvanIvan wrote:
> Dear all,
> We are using SQL2000 sp4 on Windows 2000 Svr.
> We found one of the database size become zero in Enterprise manager.
> We have checked the database setting and the database is already set
> auto-growth, without limit, by 1000Mb each time.
> The data file size reach 6G now.
> Is there anything we miss? That's the first time we meet this case.
> We have checked the Harddisk drive for the data file and it still have over
> 100G space.
> Ivan
Do you get an error message saying the filegroup is full?
What is the output of EXEC sp_spaceused?
Auto-growth is usually a bad idea and isn't something I would normally
recommend for a production application. Why would you want to grow a
6GB database in 1GB increments?
--
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--|||dbcc updateusage?
Cheers,
"Ivan" wrote:
> Dear all,
> We are using SQL2000 sp4 on Windows 2000 Svr.
> We found one of the database size become zero in Enterprise manager.
> We have checked the database setting and the database is already set
> auto-growth, without limit, by 1000Mb each time.
> The data file size reach 6G now.
> Is there anything we miss? That's the first time we meet this case.
> We have checked the Harddisk drive for the data file and it still have over
> 100G space.
> Ivan
>
>

Database data file does not auto-grow

Dear all,
We are using SQL2000 sp4 on Windows 2000 Svr.
We found one of the database size become zero in Enterprise manager.
We have checked the database setting and the database is already set
auto-growth, without limit, by 1000Mb each time.
The data file size reach 6G now.
Is there anything we miss? That's the first time we meet this case.
We have checked the Harddisk drive for the data file and it still have over
100G space.
Ivan
Ivan wrote:
> Dear all,
> We are using SQL2000 sp4 on Windows 2000 Svr.
> We found one of the database size become zero in Enterprise manager.
> We have checked the database setting and the database is already set
> auto-growth, without limit, by 1000Mb each time.
> The data file size reach 6G now.
> Is there anything we miss? That's the first time we meet this case.
> We have checked the Harddisk drive for the data file and it still have over
> 100G space.
> Ivan
Do you get an error message saying the filegroup is full?
What is the output of EXEC sp_spaceused?
Auto-growth is usually a bad idea and isn't something I would normally
recommend for a production application. Why would you want to grow a
6GB database in 1GB increments?
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
|||dbcc updateusage?
Cheers,
"Ivan" wrote:

> Dear all,
> We are using SQL2000 sp4 on Windows 2000 Svr.
> We found one of the database size become zero in Enterprise manager.
> We have checked the database setting and the database is already set
> auto-growth, without limit, by 1000Mb each time.
> The data file size reach 6G now.
> Is there anything we miss? That's the first time we meet this case.
> We have checked the Harddisk drive for the data file and it still have over
> 100G space.
> Ivan
>
>

Database data file does not auto-grow

Dear all,
We are using SQL2000 sp4 on Windows 2000 Svr.
We found one of the database size become zero in Enterprise manager.
We have checked the database setting and the database is already set
auto-growth, without limit, by 1000Mb each time.
The data file size reach 6G now.
Is there anything we miss? That's the first time we meet this case.
We have checked the Harddisk drive for the data file and it still have over
100G space.
IvanIvan wrote:
> Dear all,
> We are using SQL2000 sp4 on Windows 2000 Svr.
> We found one of the database size become zero in Enterprise manager.
> We have checked the database setting and the database is already set
> auto-growth, without limit, by 1000Mb each time.
> The data file size reach 6G now.
> Is there anything we miss? That's the first time we meet this case.
> We have checked the Harddisk drive for the data file and it still have ove
r
> 100G space.
> Ivan
Do you get an error message saying the filegroup is full?
What is the output of EXEC sp_spaceused?
Auto-growth is usually a bad idea and isn't something I would normally
recommend for a production application. Why would you want to grow a
6GB database in 1GB increments?
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--|||dbcc updateusage?
Cheers,
"Ivan" wrote:

> Dear all,
> We are using SQL2000 sp4 on Windows 2000 Svr.
> We found one of the database size become zero in Enterprise manager.
> We have checked the database setting and the database is already set
> auto-growth, without limit, by 1000Mb each time.
> The data file size reach 6G now.
> Is there anything we miss? That's the first time we meet this case.
> We have checked the Harddisk drive for the data file and it still have ove
r
> 100G space.
> Ivan
>
>

Database creation from inside of Visual C#

When I create a database from inside of Visual C# Express, why can't I view it with the manager from the SQL Server Express Edition? I mean, it does not appear at all. Is there any problem?

hi,

chances are you are using a User Instance, so that you can usually not "browse" your database using a "standard" connection via SQL Server Management Studio.. the article explains how to connect to User Instance databases via other clients than the calling application..

regards

|||

Hi

Well, I followed the article closely and retrieved the pipe and ran the command "sqlcmd -S np:\\.\pipe\010E053B-3912-43\tsql\query" and I received the following error:

"HResult 0x2, Level 16, State 1
Named Pipes Provider: Could not open a connection to SQL Server [2].
Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while establi
shing a connection to the server. When connecting to SQL Server 2005, this failu
re may be caused by the fact that under the default settings SQL Server does not
allow remote connections..
Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired."

I enabled Remote Connections from Surface Area Controll, stoped the service, restarted it, and it gives me the same error. How can I connect to a User Instance with the SQL Server Management? I did not saw such option ...

Also I want to ask if there are some resources to learn for an absolute beginner SQL Server Express. Some recomandations would be nice.

|||

hi,

try the SQL Server Configuration Manager as well... there you can enable the desired nework protocol..

regards

|||

Check out the FAQ at the top of this forum, you will find instructions on connecting Management Studio to a User Instance.

Enabling remote connections is not required, particularly since User Instances only support local connections. If you bravely read through the entire error you got, you'll see that the problem you're having is a timeout. This is a particularly bad error message that gets throwen for basically every connection problem (hey, I wasn't here when they wrote it). The important bit is usually at the end in parenthasis.

In your case I'll bet your User Instance isn't started so you're timing out trying to connect. The FAQ explains the details of how to get this to work.

Mike