We have MS SQL 2000 server. Recently, on our database application we gate
"Databse error code: 515" It says: Cannot insert the value NULL into cilumn
"contact_id", table name, column doesn't allow nulls. INSERT fails. No
changes made to databse. ...
A recent action on this table was, we exported the contact table to Excel,
updated, and imported from Excel.
Would you please advise us what the problem could be and how we can address
this.
Thanks,
Yigedeb.
CBI Inc
Hello,
Just see if you insert NULL into Contact_ID field. Please take a look into
table schema using SP_HELP <TableName> and verify the data you
are trying to insert..
Thanks
Hari
"Yigedeb" <Yigedeb@.discussions.microsoft.com> wrote in message
news:2FBF9D1C-F344-48AA-8172-0FF3E00A00BA@.microsoft.com...
> We have MS SQL 2000 server. Recently, on our database application we gate
> "Databse error code: 515" It says: Cannot insert the value NULL into
> cilumn
> "contact_id", table name, column doesn't allow nulls. INSERT fails. No
> changes made to databse. ...
> A recent action on this table was, we exported the contact table to Excel,
> updated, and imported from Excel.
> Would you please advise us what the problem could be and how we can
> address
> this.
> Thanks,
> Yigedeb.
> CBI
Showing posts with label databse. Show all posts
Showing posts with label databse. Show all posts
Wednesday, March 21, 2012
Monday, March 19, 2012
Database DLL
Hope someone here can help.
When I set up a Crystal report to an application , I got an application
error like this:
****Error : 532 Cannot find databse DLL
****Execute<PEStartPrintJob>
Is ths related to different version of Crystal or SQL server?
Thanks
Catelin
I have some ugly memories about that...532 Cannot find
database DLL is a Crystal error. There should be several (if
not more) articles on their support web site about the
error.
-Sue
On Wed, 26 Jan 2005 16:40:30 -0600, "Catelin wang"
<cwang@.cemstone.com> wrote:
>Hope someone here can help.
>When I set up a Crystal report to an application , I got an application
>error like this:
>****Error : 532 Cannot find databse DLL
>****Execute<PEStartPrintJob>
>Is ths related to different version of Crystal or SQL server?
>
>Thanks
>Catelin
>
When I set up a Crystal report to an application , I got an application
error like this:
****Error : 532 Cannot find databse DLL
****Execute<PEStartPrintJob>
Is ths related to different version of Crystal or SQL server?
Thanks
Catelin
I have some ugly memories about that...532 Cannot find
database DLL is a Crystal error. There should be several (if
not more) articles on their support web site about the
error.
-Sue
On Wed, 26 Jan 2005 16:40:30 -0600, "Catelin wang"
<cwang@.cemstone.com> wrote:
>Hope someone here can help.
>When I set up a Crystal report to an application , I got an application
>error like this:
>****Error : 532 Cannot find databse DLL
>****Execute<PEStartPrintJob>
>Is ths related to different version of Crystal or SQL server?
>
>Thanks
>Catelin
>
Database DLL
Hope someone here can help.
When I set up a Crystal report to an application , I got an application
error like this:
****Error : 532 Cannot find databse DLL
****Execute<PEStartPrintJob>
Is ths related to different version of Crystal or SQL server?
Thanks
CatelinI have some ugly memories about that...532 Cannot find
database DLL is a Crystal error. There should be several (if
not more) articles on their support web site about the
error.
-Sue
On Wed, 26 Jan 2005 16:40:30 -0600, "Catelin wang"
<cwang@.cemstone.com> wrote:
>Hope someone here can help.
>When I set up a Crystal report to an application , I got an application
>error like this:
>****Error : 532 Cannot find databse DLL
>****Execute<PEStartPrintJob>
>Is ths related to different version of Crystal or SQL server?
>
>Thanks
>Catelin
>
When I set up a Crystal report to an application , I got an application
error like this:
****Error : 532 Cannot find databse DLL
****Execute<PEStartPrintJob>
Is ths related to different version of Crystal or SQL server?
Thanks
CatelinI have some ugly memories about that...532 Cannot find
database DLL is a Crystal error. There should be several (if
not more) articles on their support web site about the
error.
-Sue
On Wed, 26 Jan 2005 16:40:30 -0600, "Catelin wang"
<cwang@.cemstone.com> wrote:
>Hope someone here can help.
>When I set up a Crystal report to an application , I got an application
>error like this:
>****Error : 532 Cannot find databse DLL
>****Execute<PEStartPrintJob>
>Is ths related to different version of Crystal or SQL server?
>
>Thanks
>Catelin
>
Wednesday, March 7, 2012
Database Designing...
Friends,
Who is responsible for the Design of Database? System Analyst, DBA, Databse Designer, Project Leader? Coz I am working as a System Analyst, but now desgining the Databse for the ERP package which I feel is another man's work. Confussed. Plz help me.
AnilI'll wait for the follow-up poll: Who gets blamed for a poorly designed database?
A: DBA
B: DBA
C: DBA
D: All of the above.|||you're kidding, right?
you have four people, and one of them is a Database Designer, and you're asking whose job it is to design the database?
answer: not the DBA
the DBA's job is to create the physical database from the finished database design
answer: not the project leader
the project leader's job is to talk to management
answer: not the systems analyst
the system analyst's job is to figure out what the users really want, not what they're asking for
let's see, have i missed anybody?|||Yeah r937 you missed someone. You missed the poor suckers that have to perform all of those roles. I'm stuck in that position right now. I know the most about the business processes, db design, dba work, java coding, object modeling, reporting progress to management, and managing interaction with the end users. It sux but it acts as great leverage when negotiating salary.|||I don't see any reason or advantage to splitting the DBA and Database Designer roles. It sounds like a recipe for turf wars to me.
Anybody?|||Originally posted by blindman
I'll wait for the follow-up poll: Who gets blamed for a poorly designed database?
A: DBA
B: DBA
C: DBA
D: All of the above.
You took the words right out of my keyboard :)|||you can't see any advantage to splitting the DBA and Database Designer roles?
whoa, you must be trollin
where to start?
how about: if the Database Designer designs the database, sufficient time and effort will be devoted to the understanding and identification of candidate keys based on business logic, whereas if the DBA does it, you get surrogate autonumber primary keys on every table and $deity knows what other similar crap
how's that?
;)|||Do you mean to say a DBA has no knowledge of Database design ...
Buzz ... You are wrong ... what we are talking about is an Integration of DBA and DD roles ... and that would be absolutely great if the person posseses enough DD and DBA knowledge .|||Well, in large shops it doesn't seem to fly. I'D LOVE TO:
- do the analysis
- do the design
- and do what I do on a daily basis (DBA stuff)
Turf wars is what we have here.
But the sad part is, that after the design is handed over to me to implement (mind you I am not invited to any of the meatings held by the project development team), I find all kinds of design issues in about 70% of the projects. At that point it's too late to take it back to the designer, or rather to the systems analyst, because success is declared and propagated all the way to the top, and I still love my job ;) So what am I left with? MAKE IT WORK!!! Recently the "designers" started listening to me a little more (I AM SHOCKED!) and started implementing any data access through a stored procedure. So, having a break like this, I have a luxury to re-write the procedure if it needs to be, and even alter table structures and relations, because the data is not directly accessed. It's a workaround that I found, but it keeps me occupied (not right now, it's boring here, everything works...)|||no, i do not mean to say the DBA has no knowledge of database design
that'd be silly, and i wouldn't say that
and who said we were talking about an integration of roles?
i thought we were talking about a0060162742357's situation where there is already two people, one of them a database designer and the other a DBA, and the question is, whose job is it to design the database?
duh...|||Database Designer
DBA
Project Leader
Programmer
hmmm .. these guys are there and still the system analyst is designing the db ... wierd|||Unfortunately it really doesnt matter who does it because the pooch usually gets screwed right from the beginning and then you have to spend the rest of your days working around a flawed design.
those magnificent bastards|||Originally posted by Ruprect
those magnificent bastards Do they come any other way ?!?!
-PatP|||How about all the "little" projects where the project manager says something like: "We only have two tables to hold our data, why don't we just dump them in the products database?"
Hmm. Would the fact that it is not product data have anything to do with that decision (or lack thereof)?
Sadly, we have no database design group here. All the developers are free to come up with their own designs, which I find out about later. And let me tell you, we have a creative bunch around here...
How are all of your shops made up? We only have project managers, programmers, and DBA.|||All very interesting comments.
So, in a split DBA/Designer environment, should the DBA be responsble only for pure "admin" functions, such as backups, index optimization, replication, etc?
I think it is absolutely essential that a database designer have good knowledge of database administration, though I don't think the reverse is necessarilly required.
I've only worked in small-to-midsize shops where I was the one-man show, so I'm curious about how duties are split in larger environments and how people keep from stepping on eachother's toes.|||The word is "micromanagement"...Or is it 2 words?|||or the client who says i want to bring these 900 various access 97 2000 and excel files into a sql server database
bottom line the only one who cares that the model is done right, is you.
it's like paul newman said
"only cream and bastards rise"|||Originally posted by blindman
All very interesting comments.
So, in a split DBA/Designer environment, should the DBA be responsble only for pure "admin" functions, such as backups, index optimization, replication, etc?
I think it is absolutely essential that a database designer have good knowledge of database administration, though I don't think the reverse is necessarilly required.
I've only worked in small-to-midsize shops where I was the one-man show, so I'm curious about how duties are split in larger environments and how people keep from stepping on eachother's toes.
I kind of disagree about the database administration piece. It would be impossible for me to be a good DBA if I didn't know about database design. I can only do so much with backups, recoveries, replication, etc.
How would I optimize the indexes and do performance tuning well though if I didn't understand database design. Half of performance tuning is knowing how proper design works and seeing where you can improve performance by applying indexes properly in the design, restructuring entities to be more efficient, and identifying weak code through analysis of the underlying structure.|||I don't disagree with you. I just feel that tweaking indexes falls within the realm of the DBA (though a designer has to plan for indexes as well). Indexes can be changed without modifying the structure or functionality of the schema, so I don't think of them as being the exclusive realm of the designer.|||Friends,
Thanx for ur suggestions n explanations. So Can I conclude that:
A system analyst : feeds the DD with user reqs and other high level flow diagrams.
A DD : models and designs the DB
A DBA (with the help of DD) : creates the Physical Database and Admins it, gives it PL
A PL : uses the info from SA and DBA+DD to develope the System(software)
A programmer : An OX
Am I Right?
Regards,
Anil,
the inexperienced|||This is a typical distribution of tasks, but I would argue that it has several flaws.
I think the Database Designer should create the physical database, though in a development environment. When it is done (or during development) the DBA should review it, and the DBA should be responsible for rolling it out to the production environment.
Also, the Database Designer should be involved with the application design from the start, including requirements gathering and functionality. I think a lot of problems occur when a system analyst and other parties gather requirements and design interfaces and then just hand the package off the the designer with the instructions to "build this". An allegory would be many of Frank Lloyd Wright's architectural designs, which may have been innovative and attractive, but were structurally unsound. The Database Designer should be a critical part of the development team.|||any competent database designer who finds himself or herself not included in the overall systems design and user requirements analysis will not stay in that job for long
Who is responsible for the Design of Database? System Analyst, DBA, Databse Designer, Project Leader? Coz I am working as a System Analyst, but now desgining the Databse for the ERP package which I feel is another man's work. Confussed. Plz help me.
AnilI'll wait for the follow-up poll: Who gets blamed for a poorly designed database?
A: DBA
B: DBA
C: DBA
D: All of the above.|||you're kidding, right?
you have four people, and one of them is a Database Designer, and you're asking whose job it is to design the database?
answer: not the DBA
the DBA's job is to create the physical database from the finished database design
answer: not the project leader
the project leader's job is to talk to management
answer: not the systems analyst
the system analyst's job is to figure out what the users really want, not what they're asking for
let's see, have i missed anybody?|||Yeah r937 you missed someone. You missed the poor suckers that have to perform all of those roles. I'm stuck in that position right now. I know the most about the business processes, db design, dba work, java coding, object modeling, reporting progress to management, and managing interaction with the end users. It sux but it acts as great leverage when negotiating salary.|||I don't see any reason or advantage to splitting the DBA and Database Designer roles. It sounds like a recipe for turf wars to me.
Anybody?|||Originally posted by blindman
I'll wait for the follow-up poll: Who gets blamed for a poorly designed database?
A: DBA
B: DBA
C: DBA
D: All of the above.
You took the words right out of my keyboard :)|||you can't see any advantage to splitting the DBA and Database Designer roles?
whoa, you must be trollin
where to start?
how about: if the Database Designer designs the database, sufficient time and effort will be devoted to the understanding and identification of candidate keys based on business logic, whereas if the DBA does it, you get surrogate autonumber primary keys on every table and $deity knows what other similar crap
how's that?
;)|||Do you mean to say a DBA has no knowledge of Database design ...
Buzz ... You are wrong ... what we are talking about is an Integration of DBA and DD roles ... and that would be absolutely great if the person posseses enough DD and DBA knowledge .|||Well, in large shops it doesn't seem to fly. I'D LOVE TO:
- do the analysis
- do the design
- and do what I do on a daily basis (DBA stuff)
Turf wars is what we have here.
But the sad part is, that after the design is handed over to me to implement (mind you I am not invited to any of the meatings held by the project development team), I find all kinds of design issues in about 70% of the projects. At that point it's too late to take it back to the designer, or rather to the systems analyst, because success is declared and propagated all the way to the top, and I still love my job ;) So what am I left with? MAKE IT WORK!!! Recently the "designers" started listening to me a little more (I AM SHOCKED!) and started implementing any data access through a stored procedure. So, having a break like this, I have a luxury to re-write the procedure if it needs to be, and even alter table structures and relations, because the data is not directly accessed. It's a workaround that I found, but it keeps me occupied (not right now, it's boring here, everything works...)|||no, i do not mean to say the DBA has no knowledge of database design
that'd be silly, and i wouldn't say that
and who said we were talking about an integration of roles?
i thought we were talking about a0060162742357's situation where there is already two people, one of them a database designer and the other a DBA, and the question is, whose job is it to design the database?
duh...|||Database Designer
DBA
Project Leader
Programmer
hmmm .. these guys are there and still the system analyst is designing the db ... wierd|||Unfortunately it really doesnt matter who does it because the pooch usually gets screwed right from the beginning and then you have to spend the rest of your days working around a flawed design.
those magnificent bastards|||Originally posted by Ruprect
those magnificent bastards Do they come any other way ?!?!
-PatP|||How about all the "little" projects where the project manager says something like: "We only have two tables to hold our data, why don't we just dump them in the products database?"
Hmm. Would the fact that it is not product data have anything to do with that decision (or lack thereof)?
Sadly, we have no database design group here. All the developers are free to come up with their own designs, which I find out about later. And let me tell you, we have a creative bunch around here...
How are all of your shops made up? We only have project managers, programmers, and DBA.|||All very interesting comments.
So, in a split DBA/Designer environment, should the DBA be responsble only for pure "admin" functions, such as backups, index optimization, replication, etc?
I think it is absolutely essential that a database designer have good knowledge of database administration, though I don't think the reverse is necessarilly required.
I've only worked in small-to-midsize shops where I was the one-man show, so I'm curious about how duties are split in larger environments and how people keep from stepping on eachother's toes.|||The word is "micromanagement"...Or is it 2 words?|||or the client who says i want to bring these 900 various access 97 2000 and excel files into a sql server database
bottom line the only one who cares that the model is done right, is you.
it's like paul newman said
"only cream and bastards rise"|||Originally posted by blindman
All very interesting comments.
So, in a split DBA/Designer environment, should the DBA be responsble only for pure "admin" functions, such as backups, index optimization, replication, etc?
I think it is absolutely essential that a database designer have good knowledge of database administration, though I don't think the reverse is necessarilly required.
I've only worked in small-to-midsize shops where I was the one-man show, so I'm curious about how duties are split in larger environments and how people keep from stepping on eachother's toes.
I kind of disagree about the database administration piece. It would be impossible for me to be a good DBA if I didn't know about database design. I can only do so much with backups, recoveries, replication, etc.
How would I optimize the indexes and do performance tuning well though if I didn't understand database design. Half of performance tuning is knowing how proper design works and seeing where you can improve performance by applying indexes properly in the design, restructuring entities to be more efficient, and identifying weak code through analysis of the underlying structure.|||I don't disagree with you. I just feel that tweaking indexes falls within the realm of the DBA (though a designer has to plan for indexes as well). Indexes can be changed without modifying the structure or functionality of the schema, so I don't think of them as being the exclusive realm of the designer.|||Friends,
Thanx for ur suggestions n explanations. So Can I conclude that:
A system analyst : feeds the DD with user reqs and other high level flow diagrams.
A DD : models and designs the DB
A DBA (with the help of DD) : creates the Physical Database and Admins it, gives it PL
A PL : uses the info from SA and DBA+DD to develope the System(software)
A programmer : An OX
Am I Right?
Regards,
Anil,
the inexperienced|||This is a typical distribution of tasks, but I would argue that it has several flaws.
I think the Database Designer should create the physical database, though in a development environment. When it is done (or during development) the DBA should review it, and the DBA should be responsible for rolling it out to the production environment.
Also, the Database Designer should be involved with the application design from the start, including requirements gathering and functionality. I think a lot of problems occur when a system analyst and other parties gather requirements and design interfaces and then just hand the package off the the designer with the instructions to "build this". An allegory would be many of Frank Lloyd Wright's architectural designs, which may have been innovative and attractive, but were structurally unsound. The Database Designer should be a critical part of the development team.|||any competent database designer who finds himself or herself not included in the overall systems design and user requirements analysis will not stay in that job for long
Sunday, February 19, 2012
Database design - best practices
Does anyone know the location of an offical (Microsoft if possible) document that shows the best practices for databse design?
For instance what to call tables now schema's exist?
Should it be
Countries
LookCountry
Geography.Country
Geography.Countries
What about Views and Stored procedures? prefix with VW_ sp_ or some alternative?
Thanks
I have never seen any Microsoft Official document on this. But SQL Gurn Vyas has his own view which is very helpful. Refer these links
http://vyaskn.tripod.com/object_naming.htm
http://vyaskn.tripod.com/coding_conventions.htm
Do not use SP_ for procedure since those are there for system storedprocdure. Ucan have USP(User Storedprocedure) its again depends. I never uses "_" (unserscore) in my tablename. It may be easy to read but difficult to use.
Madhu
Subscribe to:
Posts (Atom)