|
Last time I checked, there were seven, and most are normalized to BNF. Humor me, introduce me to the five that I don't know.
And no, it's not the database-software that needs to implement the rules, it's the database that needs to be designed according to those rules. I've seen databases in Oracle that would be well in 1NF.
--edit;
You're right on the distinction between DBMS and RDBMS. Codds rules determine whether it's a relational database.
Bastard Programmer from Hell
|
|
|
|
|
Thanks I think you undrestood I mean may I ask more questions do you know any programs of Hierarchical,network and flat(data models)
|
|
|
|
|
When designing a program and you want it to store its memory content on a hard disk (database) so that one can restore it's memory at a later time, what is the best way to go about this, do i have to design my own storage API's or there is something available? please need some help.
|
|
|
|
|
This question is so basic and so all encompassing it cannot be answered in a forum post. You need to get a very basic book on computer systems and database. If you don't have the conceptual idea of how a database works then you are not going to understand most of the information on the web, it assumes a reasonable level of knowledge.
Try browsing SQLServerCentral.com, you may find some early instruction articles there.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Persisting your app's state (like Window state, position, etc.) and persisting the data your app is working with (business data like Customer Info, Orders, etc.) are two different things.
For persisting app state, you can use XML, plain text files, etc.
For persisting business data, you can use a database. If the size of the data you're talking about is very small, you can use XML for that too.
|
|
|
|
|
Shameel wrote: If the size of the data you're talking about is very small, you can use XML for that too.
Hey i thought XML was a standard, OpenCV 2.2 uses mostly XML files for storage, so i was actually considering XML, I want to know why i should not use XML for all storage purposes?XML is cool & easy to work with
I actually want to increase the database size of an image indexing software that indexes images based on content for a Content-based Image Retrieval System i have developed so that a huge image database can be indexed, i have been using OpenCV 2.2 storage system for now, I don't know if you have used OpenCV 2.2 storage system, if you have,is it wise to keep using OpenCV 2.2 storage system even for a large data set?
|
|
|
|
|
Yes, XML is a standard and can be helpful for storing relatively small data without the overhead of using a database. But if the size of the data is very huge, performance will suffer. A properly designed RDBMS database will be really fast even if the data is very huge.
|
|
|
|
|
Thanks for the answers,i really appreciate that.
|
|
|
|
|
As a caveat on Shameels comment, if you have a small number of records and each record is large (image file) then xml may be valid. You imply you have a huge image set to manage. You really should look into strategies of image storage there are quite a number of options.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
BupeChombaDerrick wrote: store its memory content on a hard disk
I recommend writing it to a binary file.
|
|
|
|
|
Hi,
we are having a problem with an SQL Server 2005.
We are running multiple scripts to send emails on the server but from time to time the server stops sending emails and we have to do a restart to ensure functionalitsy again. We have already taken care to close all opened connections in the scripts.
Any thoughts?
|
|
|
|
|
usermj87 wrote: Any thoughts?
Only wild guesses - care to show us your code?
There are various logfiles in Sql Server. Did they contain any references to errors or warnings?
Bastard Programmer from Hell
|
|
|
|
|
Very difficult to suggest something without seeing your code. Deadlocks, Uncommitted transactions and so many other things could happen.
|
|
|
|
|
Yes...
We are using a standard Stored Procedure as sendmail function.
ALTER PROCEDURE [dbo].[sendmail_subsc]
@to varchar(200),
@copy varchar(200)=null,
@bcc varchar(200)=null,
@replyto varchar(200)=null,
@from varchar(200),
@subject varchar(200),
@body text,
@filename varchar(255)=null
AS
Declare @iMsg int
Declare @hr int
--************* Create the CDO.Message Object ************************
EXEC @hr = sp_OACreate 'CDO.Message', @iMsg OUT
-- This is to configure a remote SMTP server.
EXEC @hr = sp_OASetProperty @iMsg, 'Configuration.fields("http://schemas.microsoft.com/cdo/configuration/sendusing").Value','2'
-- This is to configure the Server Name or IP address.
EXEC @hr = sp_OASetProperty @iMsg, 'Configuration.fields("http://schemas.microsoft.com/cdo/configuration/smtpserver").Value', 'our smtp server'
-- Save the configurations to the message object.
EXEC @hr = sp_OAMethod @iMsg, 'Configuration.Fields.Update', null
-- Set the e-mail parameters.
EXEC @hr = sp_OASetProperty @iMsg, 'To', @To
IF @copy IS NOT NULL
BEGIN
EXEC @hr = sp_OASetProperty @iMsg, 'Cc', @copy
END
IF @bcc IS NOT NULL
BEGIN
EXEC @hr = sp_OASetProperty @iMsg, 'Bcc', @bcc
END
IF @replyto IS NOT NULL
BEGIN
EXEC @hr = sp_OASetProperty @iMsg, 'ReplyTo', @replyto
END
EXEC @hr = sp_OASetProperty @iMsg, 'From', @from
EXEC @hr = sp_OASetProperty @iMsg, 'Subject', @Subject
EXEC @hr = sp_OASetProperty @iMsg, 'HTMLBody', @Body
IF @filename IS NOT NULL
BEGIN
EXEC @hr = sp_OAMethod @iMsg, 'AddAttachment', null, @filename
END
-- Send mail
EXEC @hr = sp_OAMethod @iMsg, 'Send', NULL
-- Destry object
EXEC @hr=sp_OADestroy @iMsg
and the error message we get is that in this procedure the destroy object fails at one point in time and then crashed the whole server. (buffer issue?)
here is the error log from the server:
2011-12-28 02:00:51.25 spid55 Stack Signature for the dump is 0x000000015B32F370
2011-12-28 02:00:52.24 spid55 External dump process return code 0x20000001.External dump process returned no errors.
2011-12-28 02:00:52.26 spid55 Using 'dbghelp.dll' version '4.0.5'
2011-12-28 02:00:53.36 spid55 ***Stack Dump being sent to E:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLDump10000.txt
2011-12-28 02:00:53.36 spid55 SqlDumpExceptionHandler: Process 55 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
2011-12-28 02:00:53.36 spid55 * *******************************************************************************
2011-12-28 02:00:53.36 spid55 *
2011-12-28 02:00:53.36 spid55 * BEGIN STACK DUMP:
2011-12-28 02:00:53.36 spid55 * 12/28/11 02:00:53 spid 55
2011-12-28 02:00:53.36 spid55 *
2011-12-28 02:00:53.36 spid55 *
2011-12-28 02:00:53.36 spid55 * Exception Address = 00000000774A54FA Module(ntdll+00000000000254FA)
2011-12-28 02:00:53.36 spid55 * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
2011-12-28 02:00:53.36 spid55 * Access Violation occurred writing address 0000000000000024
2011-12-28 02:00:53.36 spid55 * Input Buffer 510 bytes –
2011-12-28 02:00:53.36 spid55 * exec sendmail_subsc 'email address 1(placeholder)','email address 2 (placeholder
2011-12-28 07:53:15 - ! [298] SQLServer Error: 233, Shared Memory Provider: No process is on the other end of the pipe. [SQLSTATE 08S01]
2011-12-28 07:53:15 - ! [298] SQLServer Error: 233, Communication link failure [SQLSTATE 08S01]
2011-12-28 07:53:15 - ! [382] Logon to server '(local)' failed (ConnAttemptCachableOp)
2011-12-28 07:53:15 - ! [298] SQLServer Error: 233, Shared Memory Provider: No process is on the other end of the pipe. [SQLSTATE 08S01]
2011-12-28 07:53:15 - ! [298] SQLServer Error: 233, Communication link failure [SQLSTATE 08S01]
2011-12-28 07:53:15 - ! [382] Logon to server '(local)' failed (ConnAttemptCachableOp)
|
|
|
|
|
hello guys...excuse me for this basic question. I made this new login but when I try to connect using this login this message is shown
<pre lang="c#">
Login failed for user 'xxxxx'. (Microsoft Sql Server, Error: 18456)
</pre>
Whats the problem? Everything seems fine to me.
|
|
|
|
|
overloaded Name wrote: I made this new login
Made it how?
overloaded Name wrote: when I try to connect using this login
Tried to connect how?
|
|
|
|
|
See the error number, try entering that nto a Google search, you will get this as the first result[^]
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
|
Hi ALL,
does anybody have a working C++ code that reads mutlivalue MS Acces fields via DAO? Please help!
Radjiv
|
|
|
|
|
Did you even bother to search?
check this[^]
|
|
|
|
|
I'm looking for some good examples of database documentation to use as inspiration (to copy ) for my database documentation. The technical documentation I'm fine with; I can use tools for that to extract it from the DB, but I've hit some writer's block, especially at documenting entities, i.e. tables. OK, I'm using EF, so each of my tables represents an entity model object, and I could use short, on-liners, e.g. the Member table 'stores Member records', but that is a bit useless, so I want to also document what the Member entity is, in the same piece of documentation. Now I am stuck vacillating between one-lines and one-pagers, so I would some examples of well written DB/entity documentation. Any suggestions?
|
|
|
|
|
Just my opinion:
Including
Brady Kelly wrote: the Member table 'stores Member records' may sound unnecessary but there may be that table the currently everyone knows what it is be two years from now they will not. So I suggest keeping the information.
|
|
|
|
|
I didn't say documenting the table was unnecessary, I just said I didn't only want to have something that is basically redundant in my documentation.
|
|
|
|
|
If there is sufficient documentation that basically describes the point of a table elsewhere then your table documentation should specifically reference that other documentation. By name, by section within the document and perhaps with a link if possible. If a link is not possible then enough information must be provided that someone can reliably find that other documentation...two years from now.
|
|
|
|
|
There is no other documentation. I want the documentation for the database, the only area of the application that my client will be able to easily understand, to be the definitive documentation.
|
|
|
|
|