 |
|
|
Apologies for the shouting but this is important.
When answering a question please:
- Read the question carefully
- Understand that English isn't everyone's first language so be lenient of bad spelling and grammar
- If a question is poorly phrased then either ask for clarification, ignore it, or mark it down. Insults are not welcome
- If the question is inappropriate then click the 'vote to remove message' button
Insults, slap-downs and sarcasm aren't welcome. Let's work to help developers, not make them feel stupid.
cheers,
Chris Maunder
The Code Project Co-founder
Microsoft C++ MVP
|
|
|
|
|
|
|
For those new to message boards please try to follow a few simple rules when posting your question.- Choose the correct forum for your message. Posting a VB.NET question in the C++ forum will end in tears.
- Be specific! Don't ask "can someone send me the code to create an application that does 'X'. Pinpoint exactly what it is you need help with.
- Keep the subject line brief, but descriptive. eg "File Serialization problem"
- Keep the question as brief as possible. If you have to include code, include the smallest snippet of code you can.
- Be careful when including code that you haven't made a typo. Typing mistakes can become the focal point instead of the actual question you asked.
- Do not remove or empty a message if others have replied. Keep the thread intact and available for others to search and read. If your problem was answered then edit your message and add "[Solved]" to the subject line of the original post, and cast an approval vote to the one or several answers that really helped you.
- If you are posting source code with your question, place it inside <pre></pre> tags. We advise you also check the "Encode "<" (and other HTML) characters when pasting" checkbox before pasting anything inside the PRE block, and make sure "Use HTML in this post" check box is checked.
- Be courteous and DON'T SHOUT. Everyone here helps because they enjoy helping others, not because it's their job.
- Please do not post links to your question into an unrelated forum such as the lounge. It will be deleted. Likewise, do not post the same question in more than one forum.
- Do not be abusive, offensive, inappropriate or harass anyone on the boards. Doing so will get you kicked off and banned. Play nice.
- If you have a school or university assignment, assume that your teacher or lecturer is also reading these forums.
- No advertising or soliciting.
- We reserve the right to move your posts to a more appropriate forum or to delete anything deemed inappropriate or illegal.
cheers,
Chris Maunder
The Code Project Co-founder
Microsoft C++ MVP
|
|
|
|
|
|
|
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
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
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
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
Hi All,
can you help me? i have problem to sum up in MSSQL.
I have column below
Sale Date Total Sale/USD Deposit/USD Difference/USD
01/02/2012 188 180 -8
02/02/2012 110 100 -10
I want to create one more column is Accumulative to sum up column Different.
Accumulative
-8
-18
Can any one give me SQL statement to product result above.
Thanks.
Socheat
modified 5 days ago.
|
|
|
|
|
|
|
|
|
|
Thank for your information
Socheat
|
|
|
|
|
|
|
I need to compare two tables in sql server. they are located on different databases. I need to compare the data. The tables have about 200 fields in them.
IS there a way to compare this data and know which field does not match?
Using a hashtotal, would say if two rows are different but does not which data is exactly different. And it gets tough with 200 fields in a table.
Also the size of the table is big, about 100000 rows at minimum.
Thank you so much.
|
|
|
|
|
|
|
I suggest you create a copy of the second table in the first server - otherwise your compare will be delayed by the network.
vanikanc wrote: Using a hashtotal, would say if two rows are different but does not which data is exactly different. And it gets tough with 200 fields in a table.
200 fields? How about normalizing that table?
You could write a small table-valued function that compares each field individually for a given record and that spits out only the columnnames where there's differences, by looping through all the columns (see sys.columns).
Another option might be Sql Compare[^] from Red Gate. It shows the difference in your data, but also on a row-by-row level. The changed columns are highlighted in a different color though, and there's a trial-version available.
Bastard Programmer from Hell
|
|
|
|
|
|
|
How about using the Hashtotal or checksum concept and if the two rows are different, then write them out to 2 different text files (FileA & FileB). At the end of the process, you could use a tool like BeyondCompare to compare the data in the two files.
Just a thought.
Awesome tool to have in your bag of tricks ...
http://www.scootersoftware.com/[^]
|
|
|
|
|
|
|
I need to choose the most appropriate data engine for an application, and can use some advice.
Background:
I am replacing an existing application, rewriting it from ground up using VS 2010, C# and .NET 4.0.
The prior app used Access style databases. Microsoft discourages this type of database for new apps, or I would continue with it.
Very few of our customers need or use database servers. Typically, a customer would maintain a collection of separate databases, one for each project. Databases only need to be accessed locally. The self contained single file approach of the Access database was ideal, since it is highly portable and easily archived or deleted after a project ends. The largest database I have ever seen reached 100 mb. Typical databases are less than 20 mb, many around 2-4 mb.
The data model is largely relational, and idealy suited to object modeling (without inherited classes).
I like the EF and Code First options in VS 2010, but it all seems to be focused on working with a single server based db. I need to be able to browse and open databases. In rare cases, a customer may even open more than one db at a time, using mdi children for each db. This is not an absolute requirement, but is highly desirable.
Any ideas or suggestions?
|
|
|
|
|
|
|
SqlCE would be appropriate; doesn't require a server and is meant as a local file-based db (just as Access). You can open as many as you want simultaneous, and consists of a single file with the ".sdf" file extension.
Without the need to have it all in a single file that can be copied/moved around, I'd go for Sql Server and merge all the databases.
Bastard Programmer from Hell
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Rant 
Admin