Showing posts with label tools. Show all posts
Showing posts with label tools. Show all posts

Thursday, March 22, 2012

Database Filename error -- cannot create db From MS online tutorials

I am using VB with Visual Studio Express. I am new to these tools. I have SQL Server 2005 Express installed on my machine. I think that I have the right version. I am just using Express for taking classes and teaching myself on my machine.

When I follow the examples in the book, I keep getting this error when I go to my ASP.NET configuration and click on the security tab to add myself as a user.

"There is a problem with your selected data store. This can be caused by an invalid server name or credentials, or by insufficient permission. It can also be caused by the role manager feature not being enabled. Click the button below to be redirected to a page where you can choose a new data store.

The following message may help in diagnosing the problem:The database filename can not contain the following 3 characters: [ (open square brace), ] (close square brace) and ' (single quote) " -- end of erro msg.

I have an apostrophe in my last name. Could that be what is causing it? Is it creating a db based on my name or something? Or do I have the wrong version of SQL Server Express installed.

Thank you for any help. I appreciate it.

--Mark

Have you checked Provide of your ASP.NET configuration? Just go to Provide panel and 'Test' it. Can you see any error message?

Monday, March 19, 2012

Database Documentation

Please advise me of any tools that are available that allow to create a data dictionary of a SQL 2000 database into either Microsoft Word or Excel.

Bill Partridge

you can use visio i think

Database Documentation

I would be interested in hearing what tools people have used to document the
business uses of tables in a database? I have looked at the meta data
services that comes with SQL Server, and while it looks like a good tool, I
do not think that it fits particularly well with what I am looking to
accomplish. I would like to have some documentation that outlines the
business uses of/business rules for each table in the database. Almost an
ERD, but something that discusses/shows information about the business model
that the database/system(s) were constructed to support.
Any advice is appreciated!
TimHello Tim,
This might not be what you are looking for but maybe it can be. I've started
a project which is intended to help people with their network documentation.
The output is to Microsoft word.
The project has two files, one for documenting Servers in general and one
for documenting SQL-Servers. I've just started with the SQL version so there
are a lot of things that can be added.
If you are interested in the project you can find information here:
http://sydi.sourceforge.net
If you want to add feature requests you can do so here:
http://sourceforge.net/tracker/?group_id=116471&atid=674897
Best regards
Patrick
"TimS" <timstspry@.msn.com(donotspam)> wrote in message
news:77AD57C8-C893-41D7-B200-38435DB2D11A@.microsoft.com...
> I would be interested in hearing what tools people have used to document
the
> business uses of tables in a database? I have looked at the meta data
> services that comes with SQL Server, and while it looks like a good tool,
I
> do not think that it fits particularly well with what I am looking to
> accomplish. I would like to have some documentation that outlines the
> business uses of/business rules for each table in the database. Almost an
> ERD, but something that discusses/shows information about the business
model
> that the database/system(s) were constructed to support.
> Any advice is appreciated!
> Tim|||Hi Tim,
Here is what we have done. In our database we have two "extra tables" One
that describes the tables and one that describes individual fields
(columns). The fields table has a foreign key back to the tables table so
that fields can be associated with their proper table. In those tables we
have columns that are used to describe the individual tables and fields.
Things like business rules, uses etc. We then have a set of web pages that
connect to an empty version of the database that has only this meta data
information in it. Everyone can use them to view and update this
information. Each time a new version of the DB comes out we have an
automated process that creates a new empty DB, copies the two tables of meta
data from the existing DB and then updates the metadata tables with the
updates to the schema (updated tables & colums). The existing DB then gets
replaced with the updated DB and the web pages now use this.
Wayne
"TimS" <timstspry@.msn.com(donotspam)> wrote in message
news:77AD57C8-C893-41D7-B200-38435DB2D11A@.microsoft.com...
>I would be interested in hearing what tools people have used to document
>the
> business uses of tables in a database? I have looked at the meta data
> services that comes with SQL Server, and while it looks like a good tool,
> I
> do not think that it fits particularly well with what I am looking to
> accomplish. I would like to have some documentation that outlines the
> business uses of/business rules for each table in the database. Almost an
> ERD, but something that discusses/shows information about the business
> model
> that the database/system(s) were constructed to support.
> Any advice is appreciated!
> Tim|||SchemaToDoc (http://www.schematodoc.com) lets you annotate the tables and
fields in your database. It then lets you export the structure of your
database (tables, fields, indexes, check constraints, foreign key
constraints, and triggers) as well as your annotations to a Word document.
"Patrick Ogenstad" <patrick.ogenstad@.netsafe.se> wrote in message
news:uoeqjdgoEHA.1272@.TK2MSFTNGP09.phx.gbl...
> Hello Tim,
>
> This might not be what you are looking for but maybe it can be. I've
started
> a project which is intended to help people with their network
documentation.
> The output is to Microsoft word.
>
> The project has two files, one for documenting Servers in general and one
> for documenting SQL-Servers. I've just started with the SQL version so
there
> are a lot of things that can be added.
>
> If you are interested in the project you can find information here:
> http://sydi.sourceforge.net
>
> If you want to add feature requests you can do so here:
> http://sourceforge.net/tracker/?group_id=116471&atid=674897
>
> Best regards
> Patrick
>
> "TimS" <timstspry@.msn.com(donotspam)> wrote in message
> news:77AD57C8-C893-41D7-B200-38435DB2D11A@.microsoft.com...
> > I would be interested in hearing what tools people have used to document
> the
> > business uses of tables in a database? I have looked at the meta data
> > services that comes with SQL Server, and while it looks like a good
tool,
> I
> > do not think that it fits particularly well with what I am looking to
> > accomplish. I would like to have some documentation that outlines the
> > business uses of/business rules for each table in the database. Almost
an
> > ERD, but something that discusses/shows information about the business
> model
> > that the database/system(s) were constructed to support.
> >
> > Any advice is appreciated!
> >
> > Tim
>

Database Documentation

I would be interested in hearing what tools people have used to document the
business uses of tables in a database? I have looked at the meta data
services that comes with SQL Server, and while it looks like a good tool, I
do not think that it fits particularly well with what I am looking to
accomplish. I would like to have some documentation that outlines the
business uses of/business rules for each table in the database. Almost an
ERD, but something that discusses/shows information about the business model
that the database/system(s) were constructed to support.
Any advice is appreciated!
Tim
Hello Tim,
This might not be what you are looking for but maybe it can be. I've started
a project which is intended to help people with their network documentation.
The output is to Microsoft word.
The project has two files, one for documenting Servers in general and one
for documenting SQL-Servers. I've just started with the SQL version so there
are a lot of things that can be added.
If you are interested in the project you can find information here:
http://sydi.sourceforge.net
If you want to add feature requests you can do so here:
http://sourceforge.net/tracker/?grou...71&atid=674897
Best regards
Patrick
"TimS" <timstspry@.msn.com(donotspam)> wrote in message
news:77AD57C8-C893-41D7-B200-38435DB2D11A@.microsoft.com...
> I would be interested in hearing what tools people have used to document
the
> business uses of tables in a database? I have looked at the meta data
> services that comes with SQL Server, and while it looks like a good tool,
I
> do not think that it fits particularly well with what I am looking to
> accomplish. I would like to have some documentation that outlines the
> business uses of/business rules for each table in the database. Almost an
> ERD, but something that discusses/shows information about the business
model
> that the database/system(s) were constructed to support.
> Any advice is appreciated!
> Tim
|||Hi Tim,
Here is what we have done. In our database we have two "extra tables" One
that describes the tables and one that describes individual fields
(columns). The fields table has a foreign key back to the tables table so
that fields can be associated with their proper table. In those tables we
have columns that are used to describe the individual tables and fields.
Things like business rules, uses etc. We then have a set of web pages that
connect to an empty version of the database that has only this meta data
information in it. Everyone can use them to view and update this
information. Each time a new version of the DB comes out we have an
automated process that creates a new empty DB, copies the two tables of meta
data from the existing DB and then updates the metadata tables with the
updates to the schema (updated tables & colums). The existing DB then gets
replaced with the updated DB and the web pages now use this.
Wayne
"TimS" <timstspry@.msn.com(donotspam)> wrote in message
news:77AD57C8-C893-41D7-B200-38435DB2D11A@.microsoft.com...
>I would be interested in hearing what tools people have used to document
>the
> business uses of tables in a database? I have looked at the meta data
> services that comes with SQL Server, and while it looks like a good tool,
> I
> do not think that it fits particularly well with what I am looking to
> accomplish. I would like to have some documentation that outlines the
> business uses of/business rules for each table in the database. Almost an
> ERD, but something that discusses/shows information about the business
> model
> that the database/system(s) were constructed to support.
> Any advice is appreciated!
> Tim
|||SchemaToDoc (http://www.schematodoc.com) lets you annotate the tables and
fields in your database. It then lets you export the structure of your
database (tables, fields, indexes, check constraints, foreign key
constraints, and triggers) as well as your annotations to a Word document.
"Patrick Ogenstad" <patrick.ogenstad@.netsafe.se> wrote in message
news:uoeqjdgoEHA.1272@.TK2MSFTNGP09.phx.gbl...
> Hello Tim,
>
> This might not be what you are looking for but maybe it can be. I've
started
> a project which is intended to help people with their network
documentation.
> The output is to Microsoft word.
>
> The project has two files, one for documenting Servers in general and one
> for documenting SQL-Servers. I've just started with the SQL version so
there[vbcol=seagreen]
> are a lot of things that can be added.
>
> If you are interested in the project you can find information here:
> http://sydi.sourceforge.net
>
> If you want to add feature requests you can do so here:
> http://sourceforge.net/tracker/?grou...71&atid=674897
>
> Best regards
> Patrick
>
> "TimS" <timstspry@.msn.com(donotspam)> wrote in message
> news:77AD57C8-C893-41D7-B200-38435DB2D11A@.microsoft.com...
> the
tool,[vbcol=seagreen]
> I
an
> model
>

Sunday, March 11, 2012

Database Diff?

Are there any tools/utilties that can diff 2 sql server databases. I know the DB Pro Edition of VSTS can do it, but its hard to justify a jump from my $800 copy of VS2005 Pro to a $5k-6k version of VS just to get database diff. The tablediff looks promising but I need it to do SPROCS and SFUNCS too. Any helps or recommendations would be appreciated.

You might give Redgate SQL Compare a try.

http://www.red-gate.com/products/SQL_Compare/index.htm?gclid=CMCczdPZx4wCFQlQWAod_HLZaw

|||ApexSQL's Diff tool is also quite good and not very expensive. (www.ApexSQL.com)|||Thanks. They both look good!

Thursday, March 8, 2012

Database Diagram and SP4

I had originally posted this in the sqlserver.server group, which was
probably incorrect. So, I thought I would try the tools group. Sorry to those
who end up reading it twice
I installed SP4 on my local SQL Server and all is well, except...
The database designer is behaving a little differently. If I move or resize
a table, the relationship lines are re-arranged more radically than they were
in the previous version (SP3). After this, the lines (including simple
straight lines) seem to have a break in the middle, and it is impossible to
reposition a simple line by dragging the whole thing at once. You have to
drag the top and bottom (or left and right) halves separately, and then they
rarely line up in a straight line again. If you drag on the break in the
middle, the line will, in some cases, create new sections and double back on
itself.
Is this a bug in SP4? Is there any way to change this behavior?
Hi
I have not noticed anything different, but it does seem to render quicker.
I will play with it a bit to see what I find.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Ray Novak" <RayNovak@.discussions.microsoft.com> wrote in message
news:DE21797B-73D9-422E-8CB6-FF12EA21A986@.microsoft.com...
>I had originally posted this in the sqlserver.server group, which was
> probably incorrect. So, I thought I would try the tools group. Sorry to
> those
> who end up reading it twice
> I installed SP4 on my local SQL Server and all is well, except...
> The database designer is behaving a little differently. If I move or
> resize
> a table, the relationship lines are re-arranged more radically than they
> were
> in the previous version (SP3). After this, the lines (including simple
> straight lines) seem to have a break in the middle, and it is impossible
> to
> reposition a simple line by dragging the whole thing at once. You have to
> drag the top and bottom (or left and right) halves separately, and then
> they
> rarely line up in a straight line again. If you drag on the break in the
> middle, the line will, in some cases, create new sections and double back
> on
> itself.
> Is this a bug in SP4? Is there any way to change this behavior?
>
|||Thanx Mike - I have also noticed that the diagrams seem faster.
It seems that this problem applies to diagrams I created "pre-SP4". I tried
creating a new diagram and it is (so far) behaving correctly.
"Mike Epprecht (SQL MVP)" wrote:

> Hi
> I have not noticed anything different, but it does seem to render quicker.
> I will play with it a bit to see what I find.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Ray Novak" <RayNovak@.discussions.microsoft.com> wrote in message
> news:DE21797B-73D9-422E-8CB6-FF12EA21A986@.microsoft.com...
>
>

Wednesday, March 7, 2012

Database Designing tools

Hi all,
Does anyone know how I can design the database schema. I mean what tools can be used to the design the database and view the table relationships, etc. TIA.

Vik!Enterprise Manager? Makes a pretty good job in SQL Server for this.

Friday, February 17, 2012

Database creation/management tools?

Can someone please tell me if there are any third-party tools that will
allow me to create/manage/diagram databases as easily for SQL Server as for
Access?
I'm currently developing a pretty complex SQL database by creating it first
in Access and using the Upsizing wizard, but I've found that certain things
get lost in the translation, and I'd prefer to not have to go through the
extra work of finding/fixing the omissions.
Thanks!I would NOT develop any "pretty complex SQL database by creating it first in
Access and using the Upsizing wizard."
--
Linchi Shea
linchi_shea@.NOSPAMml.com
"Joe Sabatini" <sabatini@.optonline.net> wrote in message
news:eg2xj3GkDHA.708@.TK2MSFTNGP10.phx.gbl...
> Can someone please tell me if there are any third-party tools that will
> allow me to create/manage/diagram databases as easily for SQL Server as
for
> Access?
> I'm currently developing a pretty complex SQL database by creating it
first
> in Access and using the Upsizing wizard, but I've found that certain
things
> get lost in the translation, and I'd prefer to not have to go through the
> extra work of finding/fixing the omissions.
> Thanks!
>|||I agree with Linchi. It should be designed in a totally SQL Server aware
and compatible tool. You might want to look at the ERD tools from
Embarcadero or Sybase but they will not be cheap. Another alternative that
is less expensive but does have many features is a tool called xcase.
http://www.xcase.com/index3.html
--
Andrew J. Kelly
SQL Server MVP
"Linchi Shea" <linchi_shea@.NOSPAMml.com> wrote in message
news:%232m6TjHkDHA.2200@.TK2MSFTNGP12.phx.gbl...
> I would NOT develop any "pretty complex SQL database by creating it first
in
> Access and using the Upsizing wizard."
> --
> Linchi Shea
> linchi_shea@.NOSPAMml.com
>
> "Joe Sabatini" <sabatini@.optonline.net> wrote in message
> news:eg2xj3GkDHA.708@.TK2MSFTNGP10.phx.gbl...
> > Can someone please tell me if there are any third-party tools that will
> > allow me to create/manage/diagram databases as easily for SQL Server as
> for
> > Access?
> >
> > I'm currently developing a pretty complex SQL database by creating it
> first
> > in Access and using the Upsizing wizard, but I've found that certain
> things
> > get lost in the translation, and I'd prefer to not have to go through
the
> > extra work of finding/fixing the omissions.
> >
> > Thanks!
> >
> >
>