Showing posts with label couple. Show all posts
Showing posts with label couple. Show all posts

Wednesday, March 21, 2012

Database Setup and Design

I have a couple questions I hope someone might be able to answer, or
rather point me in the correct direction.

I am an independant developer and I am working on a small CRM for small
businesses. Nothing fancy, but built with c# and the .NET framework.

In my study of other CRM's like Microsoft, Clarify, and Misc I have
noticed something things that I do not understand.

1. When using a database, are customers and the customers
cases/problems kept in seperate tables?

2. When logging notes and misc, how is text formatted/kept in the
database. I see notes inside cases that are formatted and keep the
formatting after the cases are written the the DB.

Thanks for any info, and I am sure I am asking more then simple
questions.Sorry had one other thought. Say if customers are tracking emails or
phone messages, is a seperate table setup for each call/email or would
there be a notes database with a related key #.|||In a relational database a table represents an entity - informally, a set of
things that are alike in the sense that they have a common set of
attributes. So one might expect to see one table for Customers, another
table for Cases, a table for Invoices, etc. Data in tables are related by
keys. The database design will usually be static once it is built - the
design may be changed if the business requirements change but it isn't
necessary or desirable to create new tables at runtime. Database architects
use a set of rules called Normal Forms to help determine how to model
entities in a database.

In a nutshell, those are some general principles. However, my experience is
that commercial software packages built on relational databases sometimes
tend to use those databases in ways that are very non-standard and peculiar
to that application. The usual assumptions don't always apply. I don't know
about any of the packages you mentioned though so I could be wrong.

For storing formatted text there are various options. As RTF or HTML in a
text column for example. Or as a formatted document stored as a binary
database object.

Hope this helps.

--
David Portas
SQL Server MVP
--|||On 2/8/05 6:32 PM, in article
1107905552.527746.228500@.o13g2000cwo.googlegroups. com, "cvillard"
<cvillard@.gmail.com> wrote:

> I have a couple questions I hope someone might be able to answer, or
> rather point me in the correct direction.
> I am an independant developer and I am working on a small CRM for small
> businesses. Nothing fancy, but built with c# and the .NET framework.
> In my study of other CRM's like Microsoft, Clarify, and Misc I have
> noticed something things that I do not understand.
> 1. When using a database, are customers and the customers
> cases/problems kept in seperate tables?
> 2. When logging notes and misc, how is text formatted/kept in the
> database. I see notes inside cases that are formatted and keep the
> formatting after the cases are written the the DB.
> Thanks for any info, and I am sure I am asking more then simple
> questions.

We have a several applications where we store the data with HTML tags so it
displays formatted on the web site.

-Greg|||Thank you both for the information, this is really helpful and I think
I have some good information and ideas to start with. Much Appreciated.

Thanks again,
Chucksql

Friday, February 17, 2012

DataBase Performance Issues

Hello,

A couple of things -
Does too many stored procedures in your database affect the performance and speed of the calls?
I have many stored procedures and it seems like the more I create the slower it is to create them. Each time I use enterprise manager it also seems slower and slower to open tables, create tables and create stored procedures for code.

How can I increase the performance of my database by starting and stopping the server at a specified time. and how often should I do this restart?

Thanks in advance for input,
EIt may depend on your DBMS. In general, I wouldn't think more stored procedures would slow down the database. In my experience running Enterprise Manager is always slow when connecting to a remote machine. It is sometimes fast and sometimes slow when connecting to my localmachine's SQL server. Using Query Analyzer is ALWAYS fast (remote or local).

You may want to post this question to the forum at SQLMag.com|||No. Number of stored procedures donot slow performance by any means.

The GUI of using Enterprise manager can be a little heavy ... Is the performance same when using isqlw (Query Analyzer) ... I suppose that would be pretty fast ...

::how often should I do this restart?::

I am not sure why you would like to do this ... I've a SQL Server running for quite a while now without a restart ... So whay are you keen on doing this ...