Here are a few gems I just found in out JobTitle table, which stores contact
job titles in our database. If we have a job title, it's because it came in
a bulk-insert data file from a client.
The best
the big dawg
the boss
the man
The Master Himself
THE ONLY PERSON IN IT DEPARTMENT
The Simpsons
The Veritable Bugeater
ROFL!
Peace & happy computing,
Mike Labosh, MCSD
"When you kill a man, you're a murderer.
Kill many, and you're a conqueror.
Kill them all and you're a god." -- Dave Mustane"Mike Labosh" <mlabosh@.hotmail.com> wrote in message
news:emwFdG2zFHA.904@.tk2msftngp13.phx.gbl...
> The Veritable Bugeater
I'd like to hear the story behind this one.
Adam Machanic
SQL Server MVP
http://www.datamanipulation.net
--|||"Adam Machanic" <amachanic@.hotmail._removetoemail_.com> wrote in message
news:e8znzZ2zFHA.664@.tk2msftngp13.phx.gbl...
> "Mike Labosh" <mlabosh@.hotmail.com> wrote in message
> news:emwFdG2zFHA.904@.tk2msftngp13.phx.gbl...
>
> I'd like to hear the story behind this one.
>
> --
> Adam Machanic
> SQL Server MVP
> http://www.datamanipulation.net
> --
>
>
Probably not the real story, but anyway:
http://mynptv.org/sportsFeat/pionee..._lessplan1.html|||What a nightmare (it annoys me when I find data like this in a database.
Why the heck even have a column if you allow stuff like this, obviously more
annoyed by the original people to enter the data. I know if you get the
data there is probably an expectation that it is right (which is obviously
false :). I wonder if any ETL product would catch this sort of thing and
exception it out before it was entered into the database?
----
Louis Davidson - http://spaces.msn.com/members/drsql/
SQL Server MVP
"Arguments are to be avoided: they are always vulgar and often convincing."
(Oscar Wilde)
"Mike Labosh" <mlabosh@.hotmail.com> wrote in message
news:emwFdG2zFHA.904@.tk2msftngp13.phx.gbl...
> Here are a few gems I just found in out JobTitle table, which stores
> contact job titles in our database. If we have a job title, it's because
> it came in a bulk-insert data file from a client.
> The best
> the big dawg
> the boss
> the man
> The Master Himself
> THE ONLY PERSON IN IT DEPARTMENT
> The Simpsons
> The Veritable Bugeater
> ROFL!
> --
> Peace & happy computing,
> Mike Labosh, MCSD
> "When you kill a man, you're a murderer.
> Kill many, and you're a conqueror.
> Kill them all and you're a god." -- Dave Mustane
>|||> What a nightmare (it annoys me when I find data like this in a database.
> Why the heck even have a column if you allow stuff like this, obviously
> more annoyed by the original people to enter the data. I know if you get
> the data there is probably an expectation that it is right (which is
> obviously false :). I wonder if any ETL product would catch this sort of
> thing and exception it out before it was entered into the database?
heh.
If you worked here, you would hurt someone.
I could list snips from all the databases in the company that are all
similarly stupid. They don't want any automation, either: "Don't program
anything, we don't have the time. Just hurry up and copy/paste these 700
values into this Word template."
A homeless dude off the street could do this work. Why hire a guy that can
write code in 6 languages?!?
[bonking head on desk]
Anybody need a MCSD MCT? I'll be there in the morning!
Peace & happy computing,
Mike Labosh, MCSD
"When you kill a man, you're a murderer.
Kill many, and you're a conqueror.
Kill them all and you're a god." -- Dave Mustane|||Mike, I'll follow you :-)
Showing posts with label garbage. Show all posts
Showing posts with label garbage. Show all posts
Monday, March 26, 2012
garbage in sql server log files
hi,
My database server had hung up recently, and I had to restart it.
After checking the log I found some garbage entries in it.
has anyone encountered similar errors?
harshal.Garbage entry means what some of kind of ASCII characters or SQL DMP information?
Post a sample one here.|||Originally posted by Satya
Garbage entry means what some of kind of ASCII characters or SQL DMP information?
Post a sample one here.
There is some kind of ascii code|||What is the level of service pack on SQL & OS?
What was the error related when it hung?
Any SQL.DMP files are created?|||Originally posted by Satya
What is the level of service pack on SQL & OS?
What was the error related when it hung?
Any SQL.DMP files are created?
Error: 17883, Severity: 1, State: 0
The Scheduler 0 appears to be hung. SPID 94, ECID 0, UMS Context 0x39836B08.
sp3a and win 2k .|||Review information on following KBAs to deal with:
http://support.microsoft.com/?kbid=816840
http://support.microsoft.com/default.aspx?scid=kb;en-us;810885 - I feel this may be applicable to the situation if you use high-end subsystems h/w.
HTHsql
My database server had hung up recently, and I had to restart it.
After checking the log I found some garbage entries in it.
has anyone encountered similar errors?
harshal.Garbage entry means what some of kind of ASCII characters or SQL DMP information?
Post a sample one here.|||Originally posted by Satya
Garbage entry means what some of kind of ASCII characters or SQL DMP information?
Post a sample one here.
There is some kind of ascii code|||What is the level of service pack on SQL & OS?
What was the error related when it hung?
Any SQL.DMP files are created?|||Originally posted by Satya
What is the level of service pack on SQL & OS?
What was the error related when it hung?
Any SQL.DMP files are created?
Error: 17883, Severity: 1, State: 0
The Scheduler 0 appears to be hung. SPID 94, ECID 0, UMS Context 0x39836B08.
sp3a and win 2k .|||Review information on following KBAs to deal with:
http://support.microsoft.com/?kbid=816840
http://support.microsoft.com/default.aspx?scid=kb;en-us;810885 - I feel this may be applicable to the situation if you use high-end subsystems h/w.
HTHsql
Garbage appearing when displaying Oracle character fields
Hi,
I am having troubles with character fields being displayed as garbage characters in Reporting Services. I have a shared data source defined as "Oracle" not "OLE DB" going against an Oracle 9i database. When I run a query in the Wizard Query Builder (which I hear uses the OLE DB connection to Oracle) the characters display correctly without any garbage characters. When I run the query in the Generic Query Builder (which I hear uses the Oracle data processing extension) the character fields display with garbage in them. Also, when I view the data in the data layout under the Preview tab, I get the garbage characters. The garbage characters appear on the second or following rows, in which the prior row had the same value in that field. The fields can either be defined as varchar2 or char in Oracle of more than 1 character in length. varchar2(1) and char(1) data types seem to display correctly without the garbage. The problem also shows up when I deploy the report to the ReportServer and view it in the ReportManager.
Does anyone have any ideas?
Thanks!
MelindaI found out that our issue was that we were using the Oracle 8.1.5 client to connect to an Oracle 9i database. This was causing garbage characters to appear in our reports. Once I upgraded to use the Oracle 9.1 client, it worked as expected. I did some digging and found a small line in the documentation that suggests the minimum client is Oracle 8.1.7 or later.
"Melinda" wrote:
> Hi,
> I am having troubles with character fields being displayed as garbage characters in Reporting Services. I have a shared data source defined as "Oracle" not "OLE DB" going against an Oracle 9i database. When I run a query in the Wizard Query Builder (which I hear uses the OLE DB connection to Oracle) the characters display correctly without any garbage characters. When I run the query in the Generic Query Builder (which I hear uses the Oracle data processing extension) the character fields display with garbage in them. Also, when I view the data in the data layout under the Preview tab, I get the garbage characters. The garbage characters appear on the second or following rows, in which the prior row had the same value in that field. The fields can either be defined as varchar2 or char in Oracle of more than 1 character in length. varchar2(1) and char(1) data types seem to display correctly without the garbage. The problem also shows up when I deploy the report to the ReportServer and view it in the ReportManager.
> Does anyone have any ideas?
> Thanks!
> Melinda
I am having troubles with character fields being displayed as garbage characters in Reporting Services. I have a shared data source defined as "Oracle" not "OLE DB" going against an Oracle 9i database. When I run a query in the Wizard Query Builder (which I hear uses the OLE DB connection to Oracle) the characters display correctly without any garbage characters. When I run the query in the Generic Query Builder (which I hear uses the Oracle data processing extension) the character fields display with garbage in them. Also, when I view the data in the data layout under the Preview tab, I get the garbage characters. The garbage characters appear on the second or following rows, in which the prior row had the same value in that field. The fields can either be defined as varchar2 or char in Oracle of more than 1 character in length. varchar2(1) and char(1) data types seem to display correctly without the garbage. The problem also shows up when I deploy the report to the ReportServer and view it in the ReportManager.
Does anyone have any ideas?
Thanks!
MelindaI found out that our issue was that we were using the Oracle 8.1.5 client to connect to an Oracle 9i database. This was causing garbage characters to appear in our reports. Once I upgraded to use the Oracle 9.1 client, it worked as expected. I did some digging and found a small line in the documentation that suggests the minimum client is Oracle 8.1.7 or later.
"Melinda" wrote:
> Hi,
> I am having troubles with character fields being displayed as garbage characters in Reporting Services. I have a shared data source defined as "Oracle" not "OLE DB" going against an Oracle 9i database. When I run a query in the Wizard Query Builder (which I hear uses the OLE DB connection to Oracle) the characters display correctly without any garbage characters. When I run the query in the Generic Query Builder (which I hear uses the Oracle data processing extension) the character fields display with garbage in them. Also, when I view the data in the data layout under the Preview tab, I get the garbage characters. The garbage characters appear on the second or following rows, in which the prior row had the same value in that field. The fields can either be defined as varchar2 or char in Oracle of more than 1 character in length. varchar2(1) and char(1) data types seem to display correctly without the garbage. The problem also shows up when I deploy the report to the ReportServer and view it in the ReportManager.
> Does anyone have any ideas?
> Thanks!
> Melinda
Subscribe to:
Posts (Atom)