Missing dll file: system

Showing posts with label system. Show all posts

Monday, March 26, 2012

Model backup failed

Good morning,
I am new to sql server and I have an issue with my backups.
So I set up these jobs:
Backup for System database:
Model, Master, MSDB DATABASE separately (every day at 22h)
Model, Master, MSDB log separately (every hour, between 5h-21h)
Backup for User Database
Database User (every day at 23h)
Database Log (every hour, between 02h-21h)
2 Plan Maintenance
Integrity Checks for all Database (System + User)
Optimization Job for all Database (System + User)
Why does my model backup and msdb log failed ? any idea?
Thanks
InaCan you post us the contents of your error log file please!
"ina" <roberta.inalbon@.gmail.com> wrote in message
news:1155022867.432337.303640@.75g2000cwc.googlegroups.com...
> Good morning,
> I am new to sql server and I have an issue with my backups.
> So I set up these jobs:
> Backup for System database:
> Model, Master, MSDB DATABASE separately (every day at 22h)
> Model, Master, MSDB log separately (every hour, between 5h-21h)
> Backup for User Database
> Database User (every day at 23h)
> Database Log (every hour, between 02h-21h)
> 2 Plan Maintenance
> Integrity Checks for all Database (System + User)
> Optimization Job for all Database (System + User)
> Why does my model backup and msdb log failed ? any idea?
> Thanks
> Ina
>|||Immy wrote:
> Can you post us the contents of your error log file please!
> "ina" <roberta.inalbon@.gmail.com> wrote in message
> news:1155022867.432337.303640@.75g2000cwc.googlegroups.com...
> > Good morning,
> >
> > I am new to sql server and I have an issue with my backups.
> >
> > So I set up these jobs:
> >
> > Backup for System database:
> >
> > Model, Master, MSDB DATABASE separately (every day at 22h)
> > Model, Master, MSDB log separately (every hour, between 5h-21h)
> >
> > Backup for User Database
> >
> > Database User (every day at 23h)
> > Database Log (every hour, between 02h-21h)
> >
> > 2 Plan Maintenance
> > Integrity Checks for all Database (System + User)
> > Optimization Job for all Database (System + User)
> >
> > Why does my model backup and msdb log failed ? any idea?
> >
> > Thanks
> >
> > Ina
> >
What is recovery model msdb database? If it is simple you log backup
will fail
For model database backup failure look in error log , it will have
detailed information about it.
Regards
Amish Shah|||"ina" <roberta.inalbon@.gmail.com> wrote in message
news:1155022867.432337.303640@.75g2000cwc.googlegroups.com...
> Good morning,
> I am new to sql server and I have an issue with my backups.
> So I set up these jobs:
> Backup for System database:
> Model, Master, MSDB DATABASE separately (every day at 22h)
> Model, Master, MSDB log separately (every hour, between 5h-21h)
> Backup for User Database
> Database User (every day at 23h)
> Database Log (every hour, between 02h-21h)
> 2 Plan Maintenance
> Integrity Checks for all Database (System + User)
> Optimization Job for all Database (System + User)
> Why does my model backup and msdb log failed ? any idea?
Beacuse they are in SIMPLE recovery mode and there's no need for a
logbackup.
The full should work fine though.
> Thanks
> Ina
>|||Hi,
What is the error you are getting?
First of all there is no need to backup the log for Model and Master
database; this is because we
are not supposed to do manipulations into these system databases.
Incase if you are getting errors in transaction log backup then verify the
recovery model for MSDB and Model databases.
For transaction log backup the recovery model should be either Bulk_logged
or Full.
Thanks
Hari
SQL Server MVP
"ina" <roberta.inalbon@.gmail.com> wrote in message
news:1155022867.432337.303640@.75g2000cwc.googlegroups.com...
> Good morning,
> I am new to sql server and I have an issue with my backups.
> So I set up these jobs:
> Backup for System database:
> Model, Master, MSDB DATABASE separately (every day at 22h)
> Model, Master, MSDB log separately (every hour, between 5h-21h)
> Backup for User Database
> Database User (every day at 23h)
> Database Log (every hour, between 02h-21h)
> 2 Plan Maintenance
> Integrity Checks for all Database (System + User)
> Optimization Job for all Database (System + User)
> Why does my model backup and msdb log failed ? any idea?
> Thanks
> Ina
>|||Thanks guys.
It was because the MSDB Database was set up to simple instead of Full.
I changed it
but the model DB backup I do not know why it is failing
The job failed. The Job was invoked by Schedule 26 (Schedule 1). The
last step to run was step 1 (Step 1).
This is the job error I get.
Ina
I thing
Hari Prasad wrote:
> Hi,
> What is the error you are getting?
> First of all there is no need to backup the log for Model and Master
> database; this is because we
> are not supposed to do manipulations into these system databases.
> Incase if you are getting errors in transaction log backup then verify the
> recovery model for MSDB and Model databases.
> For transaction log backup the recovery model should be either Bulk_logged
> or Full.
> Thanks
> Hari
> SQL Server MVP
>
> "ina" <roberta.inalbon@.gmail.com> wrote in message
> news:1155022867.432337.303640@.75g2000cwc.googlegroups.com...
> > Good morning,
> >
> > I am new to sql server and I have an issue with my backups.
> >
> > So I set up these jobs:
> >
> > Backup for System database:
> >
> > Model, Master, MSDB DATABASE separately (every day at 22h)
> > Model, Master, MSDB log separately (every hour, between 5h-21h)
> >
> > Backup for User Database
> >
> > Database User (every day at 23h)
> > Database Log (every hour, between 02h-21h)
> >
> > 2 Plan Maintenance
> > Integrity Checks for all Database (System + User)
> > Optimization Job for all Database (System + User)
> >
> > Why does my model backup and msdb log failed ? any idea?
> >
> > Thanks
> >
> > Ina
> >|||Specify a report file for the Maint Plan and check for the SQL Server errors in that report file.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"ina" <roberta.inalbon@.gmail.com> wrote in message
news:1155043376.504435.46880@.n13g2000cwa.googlegroups.com...
> Thanks guys.
> It was because the MSDB Database was set up to simple instead of Full.
> I changed it
> but the model DB backup I do not know why it is failing
> The job failed. The Job was invoked by Schedule 26 (Schedule 1). The
> last step to run was step 1 (Step 1).
> This is the job error I get.
> Ina
> I thing
> Hari Prasad wrote:
>> Hi,
>> What is the error you are getting?
>> First of all there is no need to backup the log for Model and Master
>> database; this is because we
>> are not supposed to do manipulations into these system databases.
>> Incase if you are getting errors in transaction log backup then verify the
>> recovery model for MSDB and Model databases.
>> For transaction log backup the recovery model should be either Bulk_logged
>> or Full.
>> Thanks
>> Hari
>> SQL Server MVP
>>
>> "ina" <roberta.inalbon@.gmail.com> wrote in message
>> news:1155022867.432337.303640@.75g2000cwc.googlegroups.com...
>> > Good morning,
>> >
>> > I am new to sql server and I have an issue with my backups.
>> >
>> > So I set up these jobs:
>> >
>> > Backup for System database:
>> >
>> > Model, Master, MSDB DATABASE separately (every day at 22h)
>> > Model, Master, MSDB log separately (every hour, between 5h-21h)
>> >
>> > Backup for User Database
>> >
>> > Database User (every day at 23h)
>> > Database Log (every hour, between 02h-21h)
>> >
>> > 2 Plan Maintenance
>> > Integrity Checks for all Database (System + User)
>> > Optimization Job for all Database (System + User)
>> >
>> > Why does my model backup and msdb log failed ? any idea?
>> >
>> > Thanks
>> >
>> > Ina
>> >
>|||Thank you all for this good advice I will check it.
Ina
Tibor Karaszi wrote:
> Specify a report file for the Maint Plan and check for the SQL Server errors in that report file.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "ina" <roberta.inalbon@.gmail.com> wrote in message
> news:1155043376.504435.46880@.n13g2000cwa.googlegroups.com...
> > Thanks guys.
> >
> > It was because the MSDB Database was set up to simple instead of Full.
> > I changed it
> > but the model DB backup I do not know why it is failing
> >
> > The job failed. The Job was invoked by Schedule 26 (Schedule 1). The
> > last step to run was step 1 (Step 1).
> >
> > This is the job error I get.
> >
> > Ina
> >
> > I thing
> > Hari Prasad wrote:
> >> Hi,
> >>
> >> What is the error you are getting?
> >>
> >> First of all there is no need to backup the log for Model and Master
> >> database; this is because we
> >> are not supposed to do manipulations into these system databases.
> >>
> >> Incase if you are getting errors in transaction log backup then verify the
> >> recovery model for MSDB and Model databases.
> >> For transaction log backup the recovery model should be either Bulk_logged
> >> or Full.
> >>
> >> Thanks
> >> Hari
> >> SQL Server MVP
> >>
> >>
> >> "ina" <roberta.inalbon@.gmail.com> wrote in message
> >> news:1155022867.432337.303640@.75g2000cwc.googlegroups.com...
> >> > Good morning,
> >> >
> >> > I am new to sql server and I have an issue with my backups.
> >> >
> >> > So I set up these jobs:
> >> >
> >> > Backup for System database:
> >> >
> >> > Model, Master, MSDB DATABASE separately (every day at 22h)
> >> > Model, Master, MSDB log separately (every hour, between 5h-21h)
> >> >
> >> > Backup for User Database
> >> >
> >> > Database User (every day at 23h)
> >> > Database Log (every hour, between 02h-21h)
> >> >
> >> > 2 Plan Maintenance
> >> > Integrity Checks for all Database (System + User)
> >> > Optimization Job for all Database (System + User)
> >> >
> >> > Why does my model backup and msdb log failed ? any idea?
> >> >
> >> > Thanks
> >> >
> >> > Ina
> >> >
> >

Model backup failed

mobing data-posting again

I hate to post twice but I never received a response from 2 days ago.
I am capturing system information about computers. Currently I have one
table named SystemInfo that gets data inserted by DTS everyday. Before
running DTS job, I would truncate table and insert all new data. Since there
are times I miss pulling data for machines, I end up truncating data and
then losing that information unitl maybe the next day. I am trying to keep
my system info with the latest data even when I do not poll.
Steps I took:
Kept SystemInfo table and created a StagingSystemInfo table that the DTS job
inserts all data. Both tables are identical as in structure. Instead of
truncating SystemInfo, I need to know how to check my staging table and if
the computername exists drop computername from SystemInfo and insert data
and them move onto the next node. I just don't know how to do the check. I
know I can use the insert into command.
For example,
If computername exists in StagingSystemInfo table
Then drop that computername from SystemInfo and insert data.
Keep running unil I have reached the last computername.
In the end I should have my SystemInfo table with current data and if I did
not get data for a particular machine in staging table I will still have in
SystemInfo table.
At the end drop table."Big D" <BigDaddy@.newsgroup.nospam> wrote in message
news:eVYvxHxVFHA.3320@.TK2MSFTNGP12.phx.gbl...
>I hate to post twice but I never received a response from 2 days ago.
>
> I am capturing system information about computers. Currently I have one
> table named SystemInfo that gets data inserted by DTS everyday. Before
> running DTS job, I would truncate table and insert all new data. Since
> there
> are times I miss pulling data for machines, I end up truncating data and
> then losing that information unitl maybe the next day. I am trying to keep
> my system info with the latest data even when I do not poll.
> Steps I took:
> Kept SystemInfo table and created a StagingSystemInfo table that the DTS
> job
> inserts all data. Both tables are identical as in structure. Instead of
> truncating SystemInfo, I need to know how to check my staging table and if
> the computername exists drop computername from SystemInfo and insert data
> and them move onto the next node. I just don't know how to do the check. I
> know I can use the insert into command.
>
> For example,
> If computername exists in StagingSystemInfo table
> Then drop that computername from SystemInfo and insert data.
> Keep running unil I have reached the last computername.
> In the end I should have my SystemInfo table with current data and if I
> did
> not get data for a particular machine in staging table I will still have
> in
> SystemInfo table.
> At the end drop table.
Why not simply perform an update and an insert? You didn't provide any
information on the structure of the tables involved (DDL), so all I can
offer is pseudocode:
UPDATE SystemInfo
SET
Column1 = (SELECT Column1 FROM StagingSystemInfo WHERE
SystemInfo.computername = StagingSystemInfo.computername),
Column2 = (SELECT Column2 FROM StagingSystemInfo WHERE
SystemInfo.computername = StagingSystemInfo.computername),
.
.
.
ColumnN = (SELECT ColumnN FROM StagingSystemInfo WHERE
SystemInfo.computername = StagingSystemInfo.computername)
WHERE EXISTS (SELECT * FROM StagingSystemInfo WHERE SystemInfo.computername
= StagingSystemInfo.computername)
INSERT INTO SystemInfo (computername, Column1, Column2, ... ,ColumnN)
SELECT computername, Column1, Column2, ... ,ColumnN
FROM StagingSystemInfo
WHERE NOT EXISTS (SELECT * FROM SystemInfo WHERE SystemInfo.computername =
StagingSystemInfo.computername)|||Below is the structure of my database. I included my Create Table statement.
As you can see they are the same
SystemInfo - Where I want to store all the most updated data.
CREATE TABLE [dbo].[SystemInfo] (
[IBDI_IBDIVersion] [nvarchar] (1000) COLLATE SQL_Latin1_General_CP1_CI_AS
NULL ,
[Win32_BIOS_Name] [nvarchar] (1000) COLLATE SQL_Latin1_General_CP1_CI_AS
NULL ,
[Win32_BIOS_SMBIOSBIOSVersion] [nvarchar] (1000) COLLATE
SQL_Latin1_General_CP1_CI_AS NULL ,
[Win32_ComputerSystem_Model] [nvarchar] (1000) COLLATE
SQL_Latin1_General_CP1_CI_AS NULL ,
[Win32_ComputerSystem_TotalPhysicalMemor
y] [nvarchar] (1000) COLLATE
SQL_Latin1_General_CP1_CI_AS NULL ,
[Win32_ComputerSystem_TimeZone] [nvarchar] (1000) COLLATE
SQL_Latin1_General_CP1_CI_AS NULL ,
[Win32_DiskDrive_Model] [nvarchar] (1000) COLLATE
SQL_Latin1_General_CP1_CI_AS NULL ,
[Win32_DiskDrive_FirmWare] [nvarchar] (1000) COLLATE
SQL_Latin1_General_CP1_CI_AS NULL ,
[Win32_LogicalDisk_FreeSpace] [nvarchar] (1000) COLLATE
SQL_Latin1_General_CP1_CI_AS NULL ,
[Win32_LogicalDisk_Size] [nvarchar] (1000) COLLATE
SQL_Latin1_General_CP1_CI_AS NULL ,
[Win32_POTSModem_Description] [nvarchar] (1000) COLLATE
SQL_Latin1_General_CP1_CI_AS NULL ,
[LTSPOS_ModemFlashDate] [nvarchar] (1000) COLLATE
SQL_Latin1_General_CP1_CI_AS NULL ,
[Win32_Processor_CurrentClockSpeed] [nvarchar] (1000) COLLATE
SQL_Latin1_General_CP1_CI_AS NULL ,
[SystemName] [nvarchar] (1000) COLLATE SQL_Latin1_General_CP1_CI_AS NULL
Next is the StagingSystemInfo where I load the data and want to update the
SystemInfo.
CREATE TABLE [dbo].[StagingSystemInfo] (
[IBDI_IBDIVersion] [nvarchar] (1000) COLLATE SQL_Latin1_General_CP1_CI_AS
NULL ,
[Win32_BIOS_Name] [nvarchar] (1000) COLLATE SQL_Latin1_General_CP1_CI_AS
NULL ,
[Win32_BIOS_SMBIOSBIOSVersion] [nvarchar] (1000) COLLATE
SQL_Latin1_General_CP1_CI_AS NULL ,
[Win32_ComputerSystem_Model] [nvarchar] (1000) COLLATE
SQL_Latin1_General_CP1_CI_AS NULL ,
[Win32_ComputerSystem_TotalPhysicalMemor
y] [nvarchar] (1000) COLLATE
SQL_Latin1_General_CP1_CI_AS NULL ,
[Win32_ComputerSystem_TimeZone] [nvarchar] (1000) COLLATE
SQL_Latin1_General_CP1_CI_AS NULL ,
[Win32_DiskDrive_Model] [nvarchar] (1000) COLLATE
SQL_Latin1_General_CP1_CI_AS NULL ,
[Win32_DiskDrive_FirmWare] [nvarchar] (1000) COLLATE
SQL_Latin1_General_CP1_CI_AS NULL ,
[Win32_LogicalDisk_FreeSpace] [nvarchar] (1000) COLLATE
SQL_Latin1_General_CP1_CI_AS NULL ,
[Win32_LogicalDisk_Size] [nvarchar] (1000) COLLATE
SQL_Latin1_General_CP1_CI_AS NULL ,
[Win32_POTSModem_Description] [nvarchar] (1000) COLLATE
SQL_Latin1_General_CP1_CI_AS NULL ,
[LTSPOS_ModemFlashDate] [nvarchar] (1000) COLLATE
SQL_Latin1_General_CP1_CI_AS NULL ,
[Win32_Processor_CurrentClockSpeed] [nvarchar] (1000) COLLATE
SQL_Latin1_General_CP1_CI_AS NULL ,
[SystemName] [nvarchar] (1000) COLLATE SQL_Latin1_General_CP1_CI_AS NULL
"Chris Hohmann" <nospam@.thankyou.com> wrote in message
news:eAN59nxVFHA.1148@.tk2msftngp13.phx.gbl...
> "Big D" <BigDaddy@.newsgroup.nospam> wrote in message
> news:eVYvxHxVFHA.3320@.TK2MSFTNGP12.phx.gbl...
> Why not simply perform an update and an insert? You didn't provide any
> information on the structure of the tables involved (DDL), so all I can
> offer is pseudocode:
> UPDATE SystemInfo
> SET
> Column1 = (SELECT Column1 FROM StagingSystemInfo WHERE
> SystemInfo.computername = StagingSystemInfo.computername),
> Column2 = (SELECT Column2 FROM StagingSystemInfo WHERE
> SystemInfo.computername = StagingSystemInfo.computername),
> .
> .
> .
> ColumnN = (SELECT ColumnN FROM StagingSystemInfo WHERE
> SystemInfo.computername = StagingSystemInfo.computername)
> WHERE EXISTS (SELECT * FROM StagingSystemInfo WHERE
> SystemInfo.computername = StagingSystemInfo.computername)
> INSERT INTO SystemInfo (computername, Column1, Column2, ... ,ColumnN)
> SELECT computername, Column1, Column2, ... ,ColumnN
> FROM StagingSystemInfo
> WHERE NOT EXISTS (SELECT * FROM SystemInfo WHERE SystemInfo.computername =
> StagingSystemInfo.computername)
>
>
>|||"Big D" <BigDaddy@.newsgroup.nospam> wrote in message
news:%23m1a8V0VFHA.2128@.TK2MSFTNGP15.phx.gbl...
> "Chris Hohmann" <nospam@.thankyou.com> wrote in message
> news:eAN59nxVFHA.1148@.tk2msftngp13.phx.gbl...
> Below is the structure of my database. I included my Create Table
> statement. As you can see they are the same
> SystemInfo - Where I want to store all the most updated data.
> CREATE TABLE [dbo].[SystemInfo] (
> [IBDI_IBDIVersion] [nvarchar] (1000) COLLATE SQL_Latin1_General_CP1_CI_AS
> NULL ,
> [Win32_BIOS_Name] [nvarchar] (1000) COLLATE SQL_Latin1_General_CP1_CI_AS
> NULL ,
> [Win32_BIOS_SMBIOSBIOSVersion] [nvarchar] (1000) COLLATE
> SQL_Latin1_General_CP1_CI_AS NULL ,
> [Win32_ComputerSystem_Model] [nvarchar] (1000) COLLATE
> SQL_Latin1_General_CP1_CI_AS NULL ,
> [Win32_ComputerSystem_TotalPhysicalMemor
y] [nvarchar] (1000) COLLATE
> SQL_Latin1_General_CP1_CI_AS NULL ,
> [Win32_ComputerSystem_TimeZone] [nvarchar] (1000) COLLATE
> SQL_Latin1_General_CP1_CI_AS NULL ,
> [Win32_DiskDrive_Model] [nvarchar] (1000) COLLATE
> SQL_Latin1_General_CP1_CI_AS NULL ,
> [Win32_DiskDrive_FirmWare] [nvarchar] (1000) COLLATE
> SQL_Latin1_General_CP1_CI_AS NULL ,
> [Win32_LogicalDisk_FreeSpace] [nvarchar] (1000) COLLATE
> SQL_Latin1_General_CP1_CI_AS NULL ,
> [Win32_LogicalDisk_Size] [nvarchar] (1000) COLLATE
> SQL_Latin1_General_CP1_CI_AS NULL ,
> [Win32_POTSModem_Description] [nvarchar] (1000) COLLATE
> SQL_Latin1_General_CP1_CI_AS NULL ,
> [LTSPOS_ModemFlashDate] [nvarchar] (1000) COLLATE
> SQL_Latin1_General_CP1_CI_AS NULL ,
> [Win32_Processor_CurrentClockSpeed] [nvarchar] (1000) COLLATE
> SQL_Latin1_General_CP1_CI_AS NULL ,
> [SystemName] [nvarchar] (1000) COLLATE SQL_Latin1_General_CP1_CI_AS NULL
>
> Next is the StagingSystemInfo where I load the data and want to update the
> SystemInfo.
> CREATE TABLE [dbo].[StagingSystemInfo] (
> [IBDI_IBDIVersion] [nvarchar] (1000) COLLATE SQL_Latin1_General_CP1_CI_AS
> NULL ,
> [Win32_BIOS_Name] [nvarchar] (1000) COLLATE SQL_Latin1_General_CP1_CI_AS
> NULL ,
> [Win32_BIOS_SMBIOSBIOSVersion] [nvarchar] (1000) COLLATE
> SQL_Latin1_General_CP1_CI_AS NULL ,
> [Win32_ComputerSystem_Model] [nvarchar] (1000) COLLATE
> SQL_Latin1_General_CP1_CI_AS NULL ,
> [Win32_ComputerSystem_TotalPhysicalMemor
y] [nvarchar] (1000) COLLATE
> SQL_Latin1_General_CP1_CI_AS NULL ,
> [Win32_ComputerSystem_TimeZone] [nvarchar] (1000) COLLATE
> SQL_Latin1_General_CP1_CI_AS NULL ,
> [Win32_DiskDrive_Model] [nvarchar] (1000) COLLATE
> SQL_Latin1_General_CP1_CI_AS NULL ,
> [Win32_DiskDrive_FirmWare] [nvarchar] (1000) COLLATE
> SQL_Latin1_General_CP1_CI_AS NULL ,
> [Win32_LogicalDisk_FreeSpace] [nvarchar] (1000) COLLATE
> SQL_Latin1_General_CP1_CI_AS NULL ,
> [Win32_LogicalDisk_Size] [nvarchar] (1000) COLLATE
> SQL_Latin1_General_CP1_CI_AS NULL ,
> [Win32_POTSModem_Description] [nvarchar] (1000) COLLATE
> SQL_Latin1_General_CP1_CI_AS NULL ,
> [LTSPOS_ModemFlashDate] [nvarchar] (1000) COLLATE
> SQL_Latin1_General_CP1_CI_AS NULL ,
> [Win32_Processor_CurrentClockSpeed] [nvarchar] (1000) COLLATE
> SQL_Latin1_General_CP1_CI_AS NULL ,
> [SystemName] [nvarchar] (1000) COLLATE SQL_Latin1_General_CP1_CI_AS NULL
Questions:
1. Which one of these columns is the computername column you identified in
your original post?
2. Is there a primary key on either of these tables?
3. Do all of these columns need to be NVARCHAR?
4. Did you try to apply the pseudocode I provided?
5. Can you post your replies either inline or below the quoted text?
Otherwise, it makes the flow of this thread difficult to follow.|||The computername is the SystemName.
The SystemName is the Primary Key.
No all the columns do not have to be varchar.
"Chris Hohmann" <nospam@.thankyou.com> wrote in message
news:OBtEtICWFHA.1200@.TK2MSFTNGP14.phx.gbl...
> "Big D" <BigDaddy@.newsgroup.nospam> wrote in message
> news:%23m1a8V0VFHA.2128@.TK2MSFTNGP15.phx.gbl...
> Questions:
> 1. Which one of these columns is the computername column you identified in
> your original post?
> 2. Is there a primary key on either of these tables?
> 3. Do all of these columns need to be NVARCHAR?
> 4. Did you try to apply the pseudocode I provided?
> 5. Can you post your replies either inline or below the quoted text?
> Otherwise, it makes the flow of this thread difficult to follow.
>|||"Big D" <BigDaddy@.newsgroup.nospam> wrote in message
news:OYLxXTCWFHA.2540@.tk2msftngp13.phx.gbl...
> "Chris Hohmann" <nospam@.thankyou.com> wrote in message
> news:OBtEtICWFHA.1200@.TK2MSFTNGP14.phx.gbl...
> The computername is the SystemName.
> The SystemName is the Primary Key.
> No all the columns do not have to be varchar.
>
What about questions 4 and 5? Did you try the pseudocode? Can you please
post your replies either inline or below the quoted text? Here's the results
of cutting and pasting from the DDL you provided into the pseudocode.
UPDATE SystemInfo
SET
IBDI_IBDIVersion = (SELECT IBDI_IBDIVersion FROM StagingSystemInfo WHERE
SystemInfo.SystemName = StagingSystemInfo.SystemName),
Win32_BIOS_Name = (SELECT Win32_BIOS_Name FROM StagingSystemInfo WHERE
SystemInfo.SystemName = StagingSystemInfo.SystemName),
Win32_BIOS_SMBIOSBIOSVersion = (SELECT Win32_BIOS_SMBIOSBIOSVersion FROM
StagingSystemInfo WHERE SystemInfo.SystemName =
StagingSystemInfo.SystemName),
Win32_ComputerSystem_Model = (SELECT Win32_ComputerSystem_Model FROM
StagingSystemInfo WHERE SystemInfo.SystemName =
StagingSystemInfo.SystemName),
Win32_ComputerSystem_TotalPhysicalMemory
= (SELECT
Win32_ComputerSystem_TotalPhysicalMemory
FROM StagingSystemInfo WHERE
SystemInfo.SystemName = StagingSystemInfo.SystemName),
Win32_ComputerSystem_TimeZone = (SELECT Win32_ComputerSystem_TimeZone FROM
StagingSystemInfo WHERE SystemInfo.SystemName =
StagingSystemInfo.SystemName),
Win32_DiskDrive_Model = (SELECT Win32_DiskDrive_Model FROM
StagingSystemInfo WHERE SystemInfo.SystemName =
StagingSystemInfo.SystemName),
Win32_DiskDrive_FirmWare = (SELECT Win32_DiskDrive_FirmWare FROM
StagingSystemInfo WHERE SystemInfo.SystemName =
StagingSystemInfo.SystemName),
Win32_LogicalDisk_FreeSpace = (SELECT Win32_LogicalDisk_FreeSpace FROM
StagingSystemInfo WHERE SystemInfo.SystemName =
StagingSystemInfo.SystemName),
Win32_LogicalDisk_Size = (SELECT Win32_LogicalDisk_Size FROM
StagingSystemInfo WHERE SystemInfo.SystemName =
StagingSystemInfo.SystemName),
Win32_POTSModem_Description = (SELECT Win32_POTSModem_Description FROM
StagingSystemInfo WHERE SystemInfo.SystemName =
StagingSystemInfo.SystemName),
LTSPOS_ModemFlashDate = (SELECT LTSPOS_ModemFlashDate FROM
StagingSystemInfo WHERE SystemInfo.SystemName =
StagingSystemInfo.SystemName),
Win32_Processor_CurrentClockSpeed = (SELECT
Win32_Processor_CurrentClockSpeed FROM StagingSystemInfo WHERE
SystemInfo.SystemName = StagingSystemInfo.SystemName),
WHERE EXISTS (SELECT * FROM StagingSystemInfo WHERE SystemInfo.SystemName =
StagingSystemInfo.SystemName)
INSERT INTO SystemInfo(IBDI_IBDIVersion, Win32_BIOS_Name,
Win32_BIOS_SMBIOSBIOSVersion, Win32_ComputerSystem_Model,
Win32_ComputerSystem_TotalPhysicalMemory
, Win32_ComputerSystem_TimeZone,
Win32_DiskDrive_Model, Win32_DiskDrive_FirmWare,
Win32_LogicalDisk_FreeSpace, Win32_LogicalDisk_Size,
Win32_POTSModem_Description, LTSPOS_ModemFlashDate,
Win32_Processor_CurrentClockSpeed, SystemName)
SELECT IBDI_IBDIVersion, Win32_BIOS_Name, Win32_BIOS_SMBIOSBIOSVersion,
Win32_ComputerSystem_Model, Win32_ComputerSystem_TotalPhysicalMemory
,
Win32_ComputerSystem_TimeZone, Win32_DiskDrive_Model,
Win32_DiskDrive_FirmWare, Win32_LogicalDisk_FreeSpace,
Win32_LogicalDisk_Size, Win32_POTSModem_Description, LTSPOS_ModemFlashDate,
Win32_Processor_CurrentClockSpeed, SystemName
FROM StagingSystemInfo
WHERE NOT EXISTS (SELECT * FROM SystemInfo WHERE SystemInfo.SystemName =
StagingSystemInfo.SystemName)

Friday, March 23, 2012

mmc.exe - .dll files are corrupted

Windows NT 4.0 operating system SQL 7.0 is loaded. Sql enterprise manager is opend mmc.exe - .dll files are corrupted. Please giveme advice

ThankyouHi there,

welcome to thescipts, take care my fren.. :)

MMC recovery

We recently lost our hard disk on disk c: It contained
Windows 2000 system files, but no SQL Server 7.0 files.
Our program files, data, and backups were on drive d:.
After rebuilding the W2K server, we ran regrebld.exe to
reestabish the W2K registry entries. We were able to
restart SQL Server and the Agent, but MMC (Microsoft
Management Console) will not start due to problems with
missing CLSIDs. We are able to access the database and
Agent info from remote MMCs, but not on the local server.
I don't see any option to reinstall/register MMC. Any
ideas of what to do?I found instmmc.exe on the installation disk. I'll try it
in the morning.
>--Original Message--
>We recently lost our hard disk on disk c: It contained
>Windows 2000 system files, but no SQL Server 7.0 files.
>Our program files, data, and backups were on drive d:.
>After rebuilding the W2K server, we ran regrebld.exe to
>reestabish the W2K registry entries. We were able to
>restart SQL Server and the Agent, but MMC (Microsoft
>Management Console) will not start due to problems with
>missing CLSIDs. We are able to access the database and
>Agent info from remote MMCs, but not on the local
server.
>I don't see any option to reinstall/register MMC. Any
>ideas of what to do?
>.
>

Monday, March 12, 2012

missing tables

I upgraded SQL Server 2000 with 2005 Developer. Now, I have only 6 system
tables in the master database. All the others disappeared. I need them for
running my old stored procedures. Do I have to reinstall 2000 to get back
the functionality?
AntoninWhat we used to call system tables are not implemented as views. Read in Books Online about
"compatibility views".
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Antonin" <antonin@.comphub.com> wrote in message news:uoQXFfwgHHA.1244@.TK2MSFTNGP04.phx.gbl...
>I upgraded SQL Server 2000 with 2005 Developer. Now, I have only 6 system tables in the master
>database. All the others disappeared. I need them for running my old stored procedures. Do I have
>to reinstall 2000 to get back the functionality?
> Antonin
>|||Thanks Tibor,
I can not find any how to fix this:
'Invalid object name 'master.dbo.sysxlogins'
Antonin
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:uZKmhnxgHHA.4892@.TK2MSFTNGP03.phx.gbl...
> What we used to call system tables are not implemented as views. Read in
> Books Online about "compatibility views".
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Antonin" <antonin@.comphub.com> wrote in message
> news:uoQXFfwgHHA.1244@.TK2MSFTNGP04.phx.gbl...
>>I upgraded SQL Server 2000 with 2005 Developer. Now, I have only 6 system
>>tables in the master database. All the others disappeared. I need them for
>>running my old stored procedures. Do I have to reinstall 2000 to get back
>>the functionality?
>> Antonin
>|||When you use undocumented features in a product you need to expect things like these. Sysxlogins
wasn't documented.
The old system tables (what was documented) are now called compatibility views. The new views has a
high degree of backwards compatibility, but again for what was documented in the first plans. These
are meant for backwards compatibility and the replacement are the new catalog views.
So, you need to go through your code and find what code uses old undocumented stuff, and fix it
before it will run (well) on 2005.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Antonin" <antonin@.comphub.com> wrote in message news:%23cXL6rygHHA.4992@.TK2MSFTNGP06.phx.gbl...
> Thanks Tibor,
> I can not find any how to fix this:
> 'Invalid object name 'master.dbo.sysxlogins'
> Antonin
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:uZKmhnxgHHA.4892@.TK2MSFTNGP03.phx.gbl...
>> What we used to call system tables are not implemented as views. Read in Books Online about
>> "compatibility views".
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Antonin" <antonin@.comphub.com> wrote in message news:uoQXFfwgHHA.1244@.TK2MSFTNGP04.phx.gbl...
>>I upgraded SQL Server 2000 with 2005 Developer. Now, I have only 6 system tables in the master
>>database. All the others disappeared. I need them for running my old stored procedures. Do I have
>>to reinstall 2000 to get back the functionality?
>> Antonin
>>
>|||> When you use undocumented features in a product you need to expect things
> like these. Sysxlogins wasn't documented.
Sadly, though, Microsoft does talk about it in their documentation. In SQL
Server 2000 Books Online, look at these topics:
Resolving Permission Conflicts
SQL Profiler Data Columns
And in 2005, there is a topic (Breaking Changes to Database Engine Features
in SQL Server 2005, ironically!) that says:
<snip>
You can identify dormant SQL Server 6.5 logins by using the following query:
SELECT * FROM sysxlogins WHERE (xstatus & 2048) = 2048;
</snip>
They corrected a similar issue I brought up on connect a while back, where
sp_who2 was mentioned in a single Books Online article. I just entered a
new one for this omission, which will at least correct the 2005 issue.
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=272245|||I found somewhere that I should use syslogins view in 2005 instead of
sysxlogins. Now I get when running this
SELECT 'ServerRole' = A.name, 'MemberName' = B.name
FROM master.dbo.spt_values A, master.dbo.syslogins B
WHERE A.low = 0
AND A.type = 'SRV'
AND B.srvid IS NULL
AND A.number & B.xstatus = A.number
Server: Msg 207, Level 16, State 1, Line 6
Invalid column name 'srvid'.
Server: Msg 207, Level 16, State 1, Line 7
Invalid column name 'xstatus'.
Where can I find the mappings between sysxlogins and syslogins columns?
Antonin
"Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:%239yaPC1gHHA.4872@.TK2MSFTNGP03.phx.gbl...
>> When you use undocumented features in a product you need to expect things
>> like these. Sysxlogins wasn't documented.
> Sadly, though, Microsoft does talk about it in their documentation. In
> SQL Server 2000 Books Online, look at these topics:
> Resolving Permission Conflicts
> SQL Profiler Data Columns
> And in 2005, there is a topic (Breaking Changes to Database Engine
> Features in SQL Server 2005, ironically!) that says:
> <snip>
> You can identify dormant SQL Server 6.5 logins by using the following
> query:
> SELECT * FROM sysxlogins WHERE (xstatus & 2048) = 2048;
> </snip>
> They corrected a similar issue I brought up on connect a while back, where
> sp_who2 was mentioned in a single Books Online article. I just entered a
> new one for this omission, which will at least correct the 2005 issue.
> http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=272245
>|||"Antonin" <Antonin.Koudelka@.fmc.sa.gov.au> wrote in message
news:%23Sm1vyVhHHA.1240@.TK2MSFTNGP04.phx.gbl...
>I found somewhere that I should use syslogins view in 2005 instead of
>sysxlogins. Now I get when running this
> SELECT 'ServerRole' = A.name, 'MemberName' = B.name
> FROM master.dbo.spt_values A, master.dbo.syslogins B
> WHERE A.low = 0
> AND A.type = 'SRV'
> AND B.srvid IS NULL
> AND A.number & B.xstatus = A.number
> Server: Msg 207, Level 16, State 1, Line 6
> Invalid column name 'srvid'.
> Server: Msg 207, Level 16, State 1, Line 7
> Invalid column name 'xstatus'.
> Where can I find the mappings between sysxlogins and syslogins columns?
Perhaps you can tell us what you're trying to do and someone can suggest a
better way to do that in SQL 2005.
In general, any time you mess with system tables, you risk running into
issues like this.
> Antonin
>
> "Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in
> message news:%239yaPC1gHHA.4872@.TK2MSFTNGP03.phx.gbl...
>> When you use undocumented features in a product you need to expect
>> things like these. Sysxlogins wasn't documented.
>> Sadly, though, Microsoft does talk about it in their documentation. In
>> SQL Server 2000 Books Online, look at these topics:
>> Resolving Permission Conflicts
>> SQL Profiler Data Columns
>> And in 2005, there is a topic (Breaking Changes to Database Engine
>> Features in SQL Server 2005, ironically!) that says:
>> <snip>
>> You can identify dormant SQL Server 6.5 logins by using the following
>> query:
>> SELECT * FROM sysxlogins WHERE (xstatus & 2048) = 2048;
>> </snip>
>> They corrected a similar issue I brought up on connect a while back,
>> where sp_who2 was mentioned in a single Books Online article. I just
>> entered a new one for this omission, which will at least correct the 2005
>> issue.
>> http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=272245
>
--
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html|||Below is the whole code. I inherited this. It runs a security report every
morning at six o'clock. I tried to work out what it is doing by running it.
However, I was not able to do it. I thing that there are some much smarter
guys than I am in this group and for them it would be obvious. I know,
everybody has other things to do than debugging someone else's code.
Nevertheless I would appreciate help. Thank you.
Antonin
SET QUOTED_IDENTIFIER ON
GO
SET ANSI_NULLS ON
GO
CREATE PROCEDURE dbo.usp_GenerateSecurityReport
AS
SET NOCOUNT ON
PRINT 'SERVER: ' + CAST(SERVERPROPERTY('servername') AS Varchar) + '\' +
ISNULL(CONVERT(char(20),SERVERPROPERTY('InstanceName')),'DEFAULT')
PRINT ''
PRINT 'Server Role members'
PRINT ''
SELECT 'ServerRole' = A.name, 'MemberName' = B.name
FROM master.dbo.spt_values A, master.dbo.sysxlogins B
WHERE A.low = 0
AND A.type = 'SRV'
AND B.srvid IS NULL
AND A.number & B.xstatus = A.number
PRINT ''
PRINT 'Database Role members'
PRINT ''
DECLARE curSecurity CURSOR FAST_FORWARD FOR
SELECT [name] FROM master..sysdatabases
DECLARE @.vchName varchar(50)
DECLARE @.vchSQL varchar(3000)
OPEN curSecurity
FETCH NEXT FROM curSecurity INTO @.vchName
WHILE @.@.FETCH_STATUS = 0
BEGIN
PRINT 'Database Name: ' + @.vchName
PRINT ''
SET @.vchSQL = 'select substring(r.[name], 1, 30) AS RoleName,
SUBSTRING(u.[name], 1, 50) AS DB_User
from ' + @.vchName + '.dbo.sysusers r
inner join ' + @.vchName + '.dbo.sysmembers m on m.groupuid = r.uid
inner join ' + @.vchName + '.dbo.sysusers u on u.uid = m.memberuid
where r.issqlrole=1
order by 1, 2'
--print @.vchSQL
exec(@.vchSQL)
PRINT ''
FETCH NEXT FROM curSecurity INTO @.vchName
END
CLOSE curSecurity
DEALLOCATE curSecurity
GO
SET QUOTED_IDENTIFIER OFF
GO
SET ANSI_NULLS ON
GO
"Greg D. Moore (Strider)" <mooregr_deleteth1s@.greenms.com> wrote in message
news:Ooy303VhHHA.4300@.TK2MSFTNGP05.phx.gbl...
> "Antonin" <Antonin.Koudelka@.fmc.sa.gov.au> wrote in message
> news:%23Sm1vyVhHHA.1240@.TK2MSFTNGP04.phx.gbl...
>>I found somewhere that I should use syslogins view in 2005 instead of
>>sysxlogins. Now I get when running this
>> SELECT 'ServerRole' = A.name, 'MemberName' = B.name
>> FROM master.dbo.spt_values A, master.dbo.syslogins B
>> WHERE A.low = 0
>> AND A.type = 'SRV'
>> AND B.srvid IS NULL
>> AND A.number & B.xstatus = A.number
>> Server: Msg 207, Level 16, State 1, Line 6
>> Invalid column name 'srvid'.
>> Server: Msg 207, Level 16, State 1, Line 7
>> Invalid column name 'xstatus'.
>> Where can I find the mappings between sysxlogins and syslogins columns?
> Perhaps you can tell us what you're trying to do and someone can suggest a
> better way to do that in SQL 2005.
> In general, any time you mess with system tables, you risk running into
> issues like this.
>
>> Antonin
>>
>> "Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in
>> message news:%239yaPC1gHHA.4872@.TK2MSFTNGP03.phx.gbl...
>> When you use undocumented features in a product you need to expect
>> things like these. Sysxlogins wasn't documented.
>> Sadly, though, Microsoft does talk about it in their documentation. In
>> SQL Server 2000 Books Online, look at these topics:
>> Resolving Permission Conflicts
>> SQL Profiler Data Columns
>> And in 2005, there is a topic (Breaking Changes to Database Engine
>> Features in SQL Server 2005, ironically!) that says:
>> <snip>
>> You can identify dormant SQL Server 6.5 logins by using the following
>> query:
>> SELECT * FROM sysxlogins WHERE (xstatus & 2048) = 2048;
>> </snip>
>> They corrected a similar issue I brought up on connect a while back,
>> where sp_who2 was mentioned in a single Books Online article. I just
>> entered a new one for this omission, which will at least correct the
>> 2005 issue.
>> http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=272245
>>
> --
> Greg Moore
> SQL Server DBA Consulting Remote and Onsite available!
> Email: sql (at) greenms.com
> http://www.greenms.com/sqlserver.html
>

Missing System Stored Procedures

I have a server that has a few system stored procedures missing, among them
sp_grantdbaccess, sp_droplogin, etc. I think this may be from a failed
installation of a service pack. This server is going away in a couple of
weeks, but in the meatime, I would like to get put these system stored
procedures back, but have been unsuccessful doing so.
Does any have a suggestion, besides restoring master?
Copy them from another SQL Server. Script them out and execute in the server
where they are missing.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"RogerT" <RogerT@.discussions.microsoft.com> wrote in message
news:2840B89F-C2FF-46D1-ACE3-F48CD2A9CF06@.microsoft.com...
>I have a server that has a few system stored procedures missing, among them
> sp_grantdbaccess, sp_droplogin, etc. I think this may be from a failed
> installation of a service pack. This server is going away in a couple of
> weeks, but in the meatime, I would like to get put these system stored
> procedures back, but have been unsuccessful doing so.
> Does any have a suggestion, besides restoring master?
|||What did you do to try to get the procedures back? Did you
try reapplying the latest Service Pack? If you had problems
with applying one of the service packs, you'd probably want
to make sure nothing else has been impacted.
-Sue
On Fri, 6 Oct 2006 15:40:02 -0700, RogerT
<RogerT@.discussions.microsoft.com> wrote:

>I have a server that has a few system stored procedures missing, among them
>sp_grantdbaccess, sp_droplogin, etc. I think this may be from a failed
>installation of a service pack. This server is going away in a couple of
>weeks, but in the meatime, I would like to get put these system stored
>procedures back, but have been unsuccessful doing so.
>Does any have a suggestion, besides restoring master?

Missing System Stored Procedures

I have a server that has a few system stored procedures missing, among them
sp_grantdbaccess, sp_droplogin, etc. I think this may be from a failed
installation of a service pack. This server is going away in a couple of
weeks, but in the meatime, I would like to get put these system stored
procedures back, but have been unsuccessful doing so.
Does any have a suggestion, besides restoring master?Copy them from another SQL Server. Script them out and execute in the server
where they are missing.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"RogerT" <RogerT@.discussions.microsoft.com> wrote in message
news:2840B89F-C2FF-46D1-ACE3-F48CD2A9CF06@.microsoft.com...
>I have a server that has a few system stored procedures missing, among them
> sp_grantdbaccess, sp_droplogin, etc. I think this may be from a failed
> installation of a service pack. This server is going away in a couple of
> weeks, but in the meatime, I would like to get put these system stored
> procedures back, but have been unsuccessful doing so.
> Does any have a suggestion, besides restoring master?|||What did you do to try to get the procedures back? Did you
try reapplying the latest Service Pack? If you had problems
with applying one of the service packs, you'd probably want
to make sure nothing else has been impacted.
-Sue
On Fri, 6 Oct 2006 15:40:02 -0700, RogerT
<RogerT@.discussions.microsoft.com> wrote:

>I have a server that has a few system stored procedures missing, among them
>sp_grantdbaccess, sp_droplogin, etc. I think this may be from a failed
>installation of a service pack. This server is going away in a couple of
>weeks, but in the meatime, I would like to get put these system stored
>procedures back, but have been unsuccessful doing so.
>Does any have a suggestion, besides restoring master?

Missing system stored procedures

When I create a new database, the system stored procedures are missing;
dt_addtosourcecontrol_u
dt_checkinobject_u
etc.
I'm logged in as sa.Is that the only 2?

I've never used them before...but the appear in all the databases I've created.

What version are you using?

And can you see them in master?|||Those procedures are magically created by Enterprise Manager, as far as I can tell. Even if you are logged into EM as someone with no create procedure rights. I would not worry over them, unless you have errors. You may need to apply a service pack to the client, at worst.|||Whatdya know...I gotta script that for often...it's the only thing I don't script

CREATE DATABASE [myDB99]
ON (NAME = N'myDB99'
, FILENAME = N'd:\database\njros1d151dev\MSSQL$NJROS1D151DEV\da ta\myDB99.mdf'
, SIZE = 209, FILEGROWTH = 10%)
LOG ON (NAME = N'myDB99_log', FILENAME = N'd:\database\njros1d151dev\MSSQL$NJROS1D151DEV\da ta\myDB99.ldf'
, SIZE = 61
, FILEGROWTH = 10%)
COLLATE SQL_Latin1_General_CP1_CI_AS
GO|||These procs are created automagically when you use the database diagrams feature in EM. These procedures have something to do with the creation of the diagrams (though i do not exactly know what).

I would not worry about them ... i have not ever seen anybody use them ... except the Enterprise Manager.|||I thought they had more to do with Visual Source Safe then with the DB Diagram feature...

Missing system stored procedures

I developed a Pocket PC app that uses merge replication in an isolated
development environment. It worked fine. The I moved to the operational
environment. Synchronization fails with error 2812, "Could not find stored
procedure 'sp_MSgetmakegenerationapplock'". A little investigation shows that
in the development environment, that stored procedure exists, but it does not
exist on the operational SQL Server. (The total sp count on the development
server is 969, on the operational server 930, so other sp's are also
missing). I disabled replication on the operational server and then
reconfigured it, but that didn't help.
The operational SQL Server is SQL Server 2000 Standard Edition running sp3a.
Any ideas why those sp's didn't get created, and how to fix this problem?
There's a message thread out there that suggests that xp_cmdshell is needed
to properly create some replication-related sp's. Is it possible that
xp_cmdshell is missing or disabled? However, when I configure the server for
replication, I don't get any error messages.
You need to reapply the sp. This problem has been observed before.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"PGallez" <PGallez@.discussions.microsoft.com> wrote in message
news:8A112E32-D0BB-4FB5-9A51-B62BBAFBAB01@.microsoft.com...
> I developed a Pocket PC app that uses merge replication in an isolated
> development environment. It worked fine. The I moved to the operational
> environment. Synchronization fails with error 2812, "Could not find stored
> procedure 'sp_MSgetmakegenerationapplock'". A little investigation shows
that
> in the development environment, that stored procedure exists, but it does
not
> exist on the operational SQL Server. (The total sp count on the
development
> server is 969, on the operational server 930, so other sp's are also
> missing). I disabled replication on the operational server and then
> reconfigured it, but that didn't help.
> The operational SQL Server is SQL Server 2000 Standard Edition running
sp3a.
> Any ideas why those sp's didn't get created, and how to fix this problem?
> There's a message thread out there that suggests that xp_cmdshell is
needed
> to properly create some replication-related sp's. Is it possible that
> xp_cmdshell is missing or disabled? However, when I configure the server
for
> replication, I don't get any error messages.
|||Thanks much, I'll give that a try.
"Hilary Cotter" wrote:

> You need to reapply the sp. This problem has been observed before.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "PGallez" <PGallez@.discussions.microsoft.com> wrote in message
> news:8A112E32-D0BB-4FB5-9A51-B62BBAFBAB01@.microsoft.com...
> that
> not
> development
> sp3a.
> needed
> for
>
>

Missing System Stored Procedures

I have a server that has a few system stored procedures missing, among them
sp_grantdbaccess, sp_droplogin, etc. I think this may be from a failed
installation of a service pack. This server is going away in a couple of
weeks, but in the meatime, I would like to get put these system stored
procedures back, but have been unsuccessful doing so.
Does any have a suggestion, besides restoring master?Copy them from another SQL Server. Script them out and execute in the server
where they are missing.
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"RogerT" <RogerT@.discussions.microsoft.com> wrote in message
news:2840B89F-C2FF-46D1-ACE3-F48CD2A9CF06@.microsoft.com...
>I have a server that has a few system stored procedures missing, among them
> sp_grantdbaccess, sp_droplogin, etc. I think this may be from a failed
> installation of a service pack. This server is going away in a couple of
> weeks, but in the meatime, I would like to get put these system stored
> procedures back, but have been unsuccessful doing so.
> Does any have a suggestion, besides restoring master?|||What did you do to try to get the procedures back? Did you
try reapplying the latest Service Pack? If you had problems
with applying one of the service packs, you'd probably want
to make sure nothing else has been impacted.
-Sue
On Fri, 6 Oct 2006 15:40:02 -0700, RogerT
<RogerT@.discussions.microsoft.com> wrote:
>I have a server that has a few system stored procedures missing, among them
>sp_grantdbaccess, sp_droplogin, etc. I think this may be from a failed
>installation of a service pack. This server is going away in a couple of
>weeks, but in the meatime, I would like to get put these system stored
>procedures back, but have been unsuccessful doing so.
>Does any have a suggestion, besides restoring master?

missing system databases folder from management studio

Hi All
My view of database on management studio does not have folder with system
databases. I am sysadmin on server and member of local admins group. Do you
know what could be a problem?In Management Studio take a look at Tools, Options, Hide system objects in
Object Explorer. Is the box checked?
Hope this helps,
Ben Nevarez
"Gene." wrote:
> Hi All
> My view of database on management studio does not have folder with system
> databases. I am sysadmin on server and member of local admins group. Do you
> know what could be a problem?|||Hi Gene
There is an option available that turns system objects visible or invisible.
Look at the Options in the Tools menu. The General tab has the checkbox
"Hide system objects in Object Explorer"
--
HTH
Kalen Delaney, SQL Server MVP
www.InsideSQLServer.com
http://blog.kalendelaney.com
"Gene." <Gene@.discussions.microsoft.com> wrote in message
news:FAEC8F2B-9E3E-467C-B368-756773D1BD16@.microsoft.com...
> Hi All
> My view of database on management studio does not have folder with system
> databases. I am sysadmin on server and member of local admins group. Do
> you
> know what could be a problem?|||Hi Ben, Kalen
This is genious!
I did not change those settings but that was a fix!
Thank you so much. I am happy again now.
"Kalen Delaney" wrote:
> Hi Gene
> There is an option available that turns system objects visible or invisible.
> Look at the Options in the Tools menu. The General tab has the checkbox
> "Hide system objects in Object Explorer"
> --
> HTH
> Kalen Delaney, SQL Server MVP
> www.InsideSQLServer.com
> http://blog.kalendelaney.com
>
> "Gene." <Gene@.discussions.microsoft.com> wrote in message
> news:FAEC8F2B-9E3E-467C-B368-756773D1BD16@.microsoft.com...
> > Hi All
> > My view of database on management studio does not have folder with system
> > databases. I am sysadmin on server and member of local admins group. Do
> > you
> > know what could be a problem?
>
>
>

Friday, March 9, 2012

Missing Sql Server node

I have just installed Visual Studio 2005 team system beta 2 on an XP machine which had a sql server 2000 previously installed. However I do not see the Sql Servers node in Solution explorer. I do have the data connections node and can make conenctions to the server. Does anyone know what I can do to make the Sql Servers node available?

Hi Asim Shah,

You should register again almost one SQL Server there.

Good Coding!

Javier Luna
http://guydotnetxmlwebservices.blogspot.com/

Missing Sql Server node

Hi Asim Shah,

You should register again almost one SQL Server there.

Good Coding!

Javier Luna
http://guydotnetxmlwebservices.blogspot.com/

Wednesday, March 7, 2012

Missing RAM

My server has Windows 2000 Advanced Server as the operating system with 4GB
of RAM and SQL Server 2000 as the database server. In perfmon the SQL Server
target server memory and SQL Server total server memory list at 1.68 GB.
What could be reducing the memory to 1.68 GB. How can I resolve this issue.
Thank You,
What edition of SQL Server?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Joe K." <Joe K.@.discussions.microsoft.com> wrote in message
news:693A66FC-45B1-482E-B59D-FC068E4B6218@.microsoft.com...
> My server has Windows 2000 Advanced Server as the operating system with 4GB
> of RAM and SQL Server 2000 as the database server. In perfmon the SQL Server
> target server memory and SQL Server total server memory list at 1.68 GB.
> What could be reducing the memory to 1.68 GB. How can I resolve this issue.
> Thank You,
|||Joe,
Check the memory setting (esp the max memory) for the SQL Server. In EM
right click the SQL Server -->Properties--> Memory.
HTH
Jerry
"Joe K." <Joe K.@.discussions.microsoft.com> wrote in message
news:693A66FC-45B1-482E-B59D-FC068E4B6218@.microsoft.com...
> My server has Windows 2000 Advanced Server as the operating system with
> 4GB
> of RAM and SQL Server 2000 as the database server. In perfmon the SQL
> Server
> target server memory and SQL Server total server memory list at 1.68 GB.
> What could be reducing the memory to 1.68 GB. How can I resolve this
> issue.
> Thank You,

Missing RAM

My server has Windows 2000 Advanced Server as the operating system with 4GB
of RAM and SQL Server 2000 as the database server. In perfmon the SQL Server
target server memory and SQL Server total server memory list at 1.68 GB.
What could be reducing the memory to 1.68 GB. How can I resolve this issue.
Thank You,What edition of SQL Server?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Joe K." <Joe K.@.discussions.microsoft.com> wrote in message
news:693A66FC-45B1-482E-B59D-FC068E4B6218@.microsoft.com...
> My server has Windows 2000 Advanced Server as the operating system with 4GB
> of RAM and SQL Server 2000 as the database server. In perfmon the SQL Server
> target server memory and SQL Server total server memory list at 1.68 GB.
> What could be reducing the memory to 1.68 GB. How can I resolve this issue.
> Thank You,|||Joe,
Check the memory setting (esp the max memory) for the SQL Server. In EM
right click the SQL Server -->Properties--> Memory.
HTH
Jerry
"Joe K." <Joe K.@.discussions.microsoft.com> wrote in message
news:693A66FC-45B1-482E-B59D-FC068E4B6218@.microsoft.com...
> My server has Windows 2000 Advanced Server as the operating system with
> 4GB
> of RAM and SQL Server 2000 as the database server. In perfmon the SQL
> Server
> target server memory and SQL Server total server memory list at 1.68 GB.
> What could be reducing the memory to 1.68 GB. How can I resolve this
> issue.
> Thank You,

Missing RAM

My server has Windows 2000 Advanced Server as the operating system with 4GB
of RAM and SQL Server 2000 as the database server. In perfmon the SQL Serve
r
target server memory and SQL Server total server memory list at 1.68 GB.
What could be reducing the memory to 1.68 GB. How can I resolve this issue.
Thank You,What edition of SQL Server?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Joe K." <Joe K.@.discussions.microsoft.com> wrote in message
news:693A66FC-45B1-482E-B59D-FC068E4B6218@.microsoft.com...
> My server has Windows 2000 Advanced Server as the operating system with 4G
B
> of RAM and SQL Server 2000 as the database server. In perfmon the SQL Ser
ver
> target server memory and SQL Server total server memory list at 1.68 GB.
> What could be reducing the memory to 1.68 GB. How can I resolve this issu
e.
> Thank You,|||Joe,
Check the memory setting (esp the max memory) for the SQL Server. In EM
right click the SQL Server -->Properties--> Memory.
HTH
Jerry
"Joe K." <Joe K.@.discussions.microsoft.com> wrote in message
news:693A66FC-45B1-482E-B59D-FC068E4B6218@.microsoft.com...
> My server has Windows 2000 Advanced Server as the operating system with
> 4GB
> of RAM and SQL Server 2000 as the database server. In perfmon the SQL
> Server
> target server memory and SQL Server total server memory list at 1.68 GB.
> What could be reducing the memory to 1.68 GB. How can I resolve this
> issue.
> Thank You,

Saturday, February 25, 2012

Missing Join Predicate error

All,
We did an inplace upgrade of our "SQLServer 2000 SP3a" production server to
"SQLServer 2005 SP2 Enterprise Edition" on saturday. The system has 8 CPUs
and 4GB of RAM. This evening, the server crashed and I had to reboot the box.
I checked the eventvwr and this is what I get. I also found a stack dump in
the log. I checked the blackbox trace for any signs and I found "MIssing Join
Predicate" in the EventClass for one of the databases. This leads me to
believe that this is the reason why SQLServer crashed though we never
encountered this problem in the SQLServer 2000 installation before we
upgraded -- the application has been working fine without any problem over
the past several years. I could have trouble shooted this issue more but
unfortunately the text of the code that resulted in the "MIssing Join
Predicate" is empty in the Text column.
Event Type:Error
Event Source:MSSQLSERVER
Event Category:(2)
Event ID:17311
Date:1/14/2008
Time:5:59:11 PM
User:N/A
Computer:ENSQLP2
Description:
SQL Server is terminating because of fatal exception c0000005. This error
may be caused by an unhandled Win32 or C++ exception, or by an access
violation encountered during exception handling. Check the SQL error log for
any related stack dumps or messages. This exception forces SQL Server to
shutdown. To recover from this error, restart the server (unless SQLAgent is
configured to auto restart).
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 9f 43 00 00 10 00 00 00 ?C.....
0008: 08 00 00 00 45 00 4e 00 ...E.N.
0010: 53 00 51 00 4c 00 50 00 S.Q.L.P.
0018: 32 00 00 00 00 00 00 00 2......
Has anyone encountered this problem before? I will start a user defined
trace and get to the core tomorrow. Neverthless, I was wondering if anyone
has encountered this issue before
Here is the stack dump. Note that at this point I also dont know which
query/SP caused the crash.
================================================== ===================
BugCheck Dump
================================================== ===================
This file is generated by Microsoft SQL Server
version 9.00.3042.00
upon detection of fatal unexpected error. Please return this file,
the query or program that produced the bugcheck, the database and
the error log, and any other pertinent information with a Service Request.
Computer type is AT/AT COMPATIBLE.
Bios Version is HP - 2
Current time is 17:59:12 01/14/08.
8 Intel x86 level 15, 2833 Mhz processor (s).
Windows NT 5.2 Build 3790 CSD Service Pack 1.
Memory
MemoryLoad = 51%
Total Physical = 4094 MB
Available Physical = 1986 MB
Total Page File = 10069 MB
Available Page File = 7980 MB
Total Virtual = 2047 MB
Available Virtual = 217 MB
**Dump thread - spid = 0, PSS = 0x00000000, EC = 0x00000000
***Stack Dump being sent to e:\MSSQL\MSSQL\LOG\SQLDump0005.txt
*
************************************************** *****************************
*
* BEGIN STACK DUMP:
* 01/14/08 17:59:12 spid 0
*
* ex_handle_except encountered exception C0000005 - Server terminating
*
*
* MODULE BASE END SIZE
* sqlservr 01000000 02C09FFF 01c0a000
* ntdll 7C800000 7C8BFFFF 000c0000
* kernel32 77E40000 77F41FFF 00102000
* MSVCR80 78130000 781CAFFF 0009b000
* msvcrt 77BA0000 77BF9FFF 0005a000
* MSVCP80 7C420000 7C4A6FFF 00087000
* ADVAPI32 77F50000 77FEBFFF 0009c000
* RPCRT4 77C50000 77CEEFFF 0009f000
* USER32 77380000 77411FFF 00092000
* GDI32 77C00000 77C48FFF 00049000
* CRYPT32 761B0000 76242FFF 00093000
* MSASN1 76190000 761A1FFF 00012000
* Secur32 76F50000 76F62FFF 00013000
* MSWSOCK 71B20000 71B60FFF 00041000
* WS2_32 71C00000 71C16FFF 00017000
* WS2HELP 71BF0000 71BF7FFF 00008000
* USERENV 76920000 769E3FFF 000c4000
* opends60 333E0000 333E6FFF 00007000
* NETAPI32 71C40000 71C97FFF 00058000
* SHELL32 7C8D0000 7D0D3FFF 00804000
* SHLWAPI 77DA0000 77DF1FFF 00052000
* comctl32 77420000 77522FFF 00103000
* psapi 76B70000 76B7AFFF 0000b000
* instapi 48060000 48069FFF 0000a000
* sqlevn70 4F610000 4F7B8FFF 001a9000
* SQLOS 344D0000 344D4FFF 00005000
* rsaenh 68000000 6802EFFF 0002f000
* AUTHZ 76C40000 76C53FFF 00014000
* MSCOREE 79000000 79044FFF 00045000
* ole32 77670000 777A3FFF 00134000
* msv1_0 76C90000 76CB6FFF 00027000
* iphlpapi 76CF0000 76D09FFF 0001a000
* kerberos 62810000 62867FFF 00058000
* cryptdll 766E0000 766EBFFF 0000c000
* schannel 76750000 76776FFF 00027000
* COMRES 77010000 770D5FFF 000c6000
* XOLEHLP 628D0000 628D5FFF 00006000
* MSDTCPRX 628E0000 62957FFF 00078000
* msvcp60 780C0000 78120FFF 00061000
* MTXCLU 62960000 62978FFF 00019000
* VERSION 77B90000 77B97FFF 00008000
* WSOCK32 71BB0000 71BB8FFF 00009000
* OLEAUT32 77D00000 77D8BFFF 0008c000
* CLUSAPI 62980000 62991FFF 00012000
* RESUTILS 629A0000 629B2FFF 00013000
* DNSAPI 76ED0000 76EFEFFF 0002f000
* winrnr 76F70000 76F76FFF 00007000
* WLDAP32 76F10000 76F3DFFF 0002e000
* rasadhlp 76F80000 76F87FFF 00008000
* security 62DF0000 62DF3FFF 00004000
* msfte 63750000 639A8FFF 00259000
* dbghelp 639B0000 63AC4FFF 00115000
* WINTRUST 76BB0000 76BDAFFF 0002b000
* imagehlp 76C10000 76C38FFF 00029000
* dssenh 68100000 68123FFF 00024000
* hnetcfg 63D20000 63D78FFF 00059000
* wshtcpip 71AE0000 71AE7FFF 00008000
* NTMARTA 77E00000 77E21FFF 00022000
* SAMLIB 63DC0000 63DCEFFF 0000f000
* ntdsapi 766F0000 76704FFF 00015000
* xpsp2res 63E50000 64114FFF 002c5000
* CLBCatQ 777B0000 77832FFF 00083000
* sqlncli 64120000 64343FFF 00224000
* COMCTL32 77530000 775C6FFF 00097000
* comdlg32 762B0000 762F9FFF 0004a000
* SQLNCLIR 007A0000 007D2FFF 00033000
* msftepxy 645D0000 645E4FFF 00015000
* EntApi 65E90000 65EA2FFF 00013000
* WININET 77210000 772B7FFF 000a8000
* xpsqlbot 66100000 66105FFF 00006000
* xpstar90 66120000 66168FFF 00049000
* SQLSCM90 66180000 66188FFF 00009000
* ODBC32 661A0000 661DCFFF 0003d000
* BatchParser90 661E0000 661FEFFF 0001f000
* ATL80 7C630000 7C64AFFF 0001b000
* odbcint 664D0000 664E6FFF 00017000
* xpstar90 664F0000 66515FFF 00026000
* xplog70 66520000 6652BFFF 0000c000
* xplog70 66540000 66542FFF 00003000
* odsole70 66550000 6655EFFF 0000f000
* SXS 66BD0000 66C8BFFF 000bc000
* oledb32 668E0000 66958FFF 00079000
* MSDART 64510000 64529FFF 0001a000
* OLEDB32R 64530000 64540FFF 00011000
* msdaora 66FF0000 67030FFF 00041000
* MSDATL3 66BA0000 66BB4FFF 00015000
* MSDAORAR 644F0000 644F3FFF 00004000
* oci 67040000 67096FFF 00057000
* MSVCR71 7C340000 7C395FFF 00056000
* OCIW32 670A0000 670F5FFF 00056000
* ORACLIENT10 67100000 67351FFF 00252000
* oracore10 67360000 67442FFF 000e3000
* oranls10 67450000 67513FFF 000c4000
* oraunls10 67520000 67537FFF 00018000
* orauts 66BC0000 66BC6FFF 00007000
* WINMM 76AA0000 76ACCFFF 0002d000
* oravsn10 67540000 67545FFF 00006000
* oracommon10 67550000 67641FFF 000f2000
* orageneric10 67650000 67BA6FFF 00557000
* orasnls10 67BB0000 67BD6FFF 00027000
* oraxml10 67BE0000 67D3FFFF 00160000
* MSVCIRT 67D40000 67D4FFFF 00010000
* oran10 67D50000 67E5CFFF 0010d000
* oranl10 67E60000 67E9CFFF 0003d000
* oranldap10 67EA0000 67EB6FFF 00017000
* orannzsbb10 67EC0000 67FC8FFF 00109000
* oraldapclnt10 68030000 68082FFF 00053000
* orancrypt10 67FD0000 67FEAFFF 0001b000
* oranro10 68090000 680DBFFF 0004c000
* oranhost10 67FF0000 67FF6FFF 00007000
* orancds10 680E0000 680E5FFF 00006000
* orantns10 680F0000 680F7FFF 00008000
* orapls10 68130000 68487FFF 00358000
* oraslax10 68490000 68498FFF 00009000
* oraplp10 684A0000 686A3FFF 00204000
* orahasgen10 686B0000 6873AFFF 0008b000
* oraocr10 68740000 687A9FFF 0006a000
* oraocrb10 687B0000 687EFFFF 00040000
* orantcp10 687F0000 687FFFFF 00010000
* orasql10 68800000 68899FFF 0009a000
* comsvcs 68B10000 68C48FFF 00139000
* activeds 76DF0000 76E22FFF 00033000
* adsldpc 76DC0000 76DE6FFF 00027000
* credui 76B80000 76BADFFF 0002e000
* ATL 76A80000 76A97FFF 00018000
* msadce 68DD0000 68E27FFF 00058000
* msadcer 68D70000 68D74FFF 00005000
* sqlmap90 6A090000 6A0ADFFF 0001e000
* MAPI32 6A0C0000 6A0DEFFF 0001f000
* sqlmap90 6A0E0000 6A0E5FFF 00006000
* MSMAPI32 6A0F0000 6A24BFFF 0015c000
* MAPIR 6A570000 6A62FFFF 000c0000
* mso 6AAC0000 6B67CFFF 00bbd000
* EMSABP32 6B690000 6B6D2FFF 00043000
* MPRAPI 76CD0000 76CE8FFF 00019000
* rtutils 76E30000 76E3BFFF 0000c000
* SETUPAPI 770E0000 771E9FFF 0010a000
* netman 77840000 77882FFF 00043000
* netshell 76300000 764C0FFF 001c1000
* RASAPI32 76E90000 76ECEFFF 0003f000
* rasman 76E40000 76E51FFF 00012000
* TAPI32 76E60000 76E8EFFF 0002f000
* WZCSAPI 6B820000 6B82CFFF 0000d000
* WZCSvc 77890000 77900FFF 00071000
* WMI 76CC0000 76CC4FFF 00005000
* DHCPCSVC 76D10000 76D2EFFF 0001f000
* WTSAPI32 76F00000 76F07FFF 00008000
* WINSTA 771F0000 77200FFF 00011000
* ESENT 6B830000 6B934FFF 00105000
* contab32 6C4E0000 6C4FEFFF 0001f000
* EMSMDB32 6C510000 6C5BEFFF 000af000
* encryption 6C930000 6C936FFF 00007000
* MSVBVM60 6C940000 6CA91FFF 00152000
* Dciph32 02C40000 02C4DFFF 0000e000
* dbghelp 69530000 69644FFF 00115000
*
* Edi: 6995E178: 6533D2F8 77F5E95E 00000000 6995E2C8 00000000
77FC2190
* Esi: 00000000:
* Eax: 6995E05C: 000042AC 00000000 00000000 77E55E02 00000000
0000000C
* Ebx: 0000003F:
* Ecx: 6995E6CC: 00000000 00010007 00000000 00460044 6533D2FC
6995E08C
* Edx: 0000003D:
* Eip: 77E55E02: 10C2C95E 90909000 A1649090 00000018 C334408B
891C428B
* Ebp: 6995E0AC: 6995E0F0 021A29C4 000042AC 00000000 00000000
00000000
* SegCs: 0000001B:
* EFlags: 00000246:
* Esp: 6995E058: 00000000 000042AC 00000000 00000000 77E55E02
00000000
* SegSs: 78130023: 00000000 00000000 00000000 00000000 00000000
00000000
*
************************************************** *****************************
*
* Short Stack Dump
77E55E02 Module(kernel32+00015E02)
021A29C4 Module(sqlservr+011A29C4)
021A6880 Module(sqlservr+011A6880)
021A642D Module(sqlservr+011A642D)
02414429 Module(sqlservr+01414429)
77E99F7A Module(kernel32+00059F7A)
78138B5E Module(MSVCR80+00008B5E)
781329C1 Module(MSVCR80+000029C1)
78132A36 Module(MSVCR80+00002A36)

Missing Join Predicate error

All,
We did an inplace upgrade of our "SQLServer 2000 SP3a" production server to
"SQLServer 2005 SP2 Enterprise Edition" on saturday. The system has 8 CPUs
and 4GB of RAM. This evening, the server crashed and I had to reboot the box.
I checked the eventvwr and this is what I get. I also found a stack dump in
the log. I checked the blackbox trace for any signs and I found "MIssing Join
Predicate" in the EventClass for one of the databases. This leads me to
believe that this is the reason why SQLServer crashed though we never
encountered this problem in the SQLServer 2000 installation before we
upgraded -- the application has been working fine without any problem over
the past several years. I could have trouble shooted this issue more but
unfortunately the text of the code that resulted in the "MIssing Join
Predicate" is empty in the Text column.
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17311
Date: 1/14/2008
Time: 5:59:11 PM
User: N/A
Computer: ENSQLP2
Description:
SQL Server is terminating because of fatal exception c0000005. This error
may be caused by an unhandled Win32 or C++ exception, or by an access
violation encountered during exception handling. Check the SQL error log for
any related stack dumps or messages. This exception forces SQL Server to
shutdown. To recover from this error, restart the server (unless SQLAgent is
configured to auto restart).
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 9f 43 00 00 10 00 00 00 Â?C.....
0008: 08 00 00 00 45 00 4e 00 ...E.N.
0010: 53 00 51 00 4c 00 50 00 S.Q.L.P.
0018: 32 00 00 00 00 00 00 00 2......
Has anyone encountered this problem before? I will start a user defined
trace and get to the core tomorrow. Neverthless, I was wondering if anyone
has encountered this issue beforeHere is the stack dump. Note that at this point I also dont know which
query/SP caused the crash.
=====================================================================
BugCheck Dump
=====================================================================
This file is generated by Microsoft SQL Server
version 9.00.3042.00
upon detection of fatal unexpected error. Please return this file,
the query or program that produced the bugcheck, the database and
the error log, and any other pertinent information with a Service Request.
Computer type is AT/AT COMPATIBLE.
Bios Version is HP - 2
Current time is 17:59:12 01/14/08.
8 Intel x86 level 15, 2833 Mhz processor (s).
Windows NT 5.2 Build 3790 CSD Service Pack 1.
Memory
MemoryLoad = 51%
Total Physical = 4094 MB
Available Physical = 1986 MB
Total Page File = 10069 MB
Available Page File = 7980 MB
Total Virtual = 2047 MB
Available Virtual = 217 MB
**Dump thread - spid = 0, PSS = 0x00000000, EC = 0x00000000
***Stack Dump being sent to e:\MSSQL\MSSQL\LOG\SQLDump0005.txt
*
*******************************************************************************
*
* BEGIN STACK DUMP:
* 01/14/08 17:59:12 spid 0
*
* ex_handle_except encountered exception C0000005 - Server terminating
*
*
* MODULE BASE END SIZE
* sqlservr 01000000 02C09FFF 01c0a000
* ntdll 7C800000 7C8BFFFF 000c0000
* kernel32 77E40000 77F41FFF 00102000
* MSVCR80 78130000 781CAFFF 0009b000
* msvcrt 77BA0000 77BF9FFF 0005a000
* MSVCP80 7C420000 7C4A6FFF 00087000
* ADVAPI32 77F50000 77FEBFFF 0009c000
* RPCRT4 77C50000 77CEEFFF 0009f000
* USER32 77380000 77411FFF 00092000
* GDI32 77C00000 77C48FFF 00049000
* CRYPT32 761B0000 76242FFF 00093000
* MSASN1 76190000 761A1FFF 00012000
* Secur32 76F50000 76F62FFF 00013000
* MSWSOCK 71B20000 71B60FFF 00041000
* WS2_32 71C00000 71C16FFF 00017000
* WS2HELP 71BF0000 71BF7FFF 00008000
* USERENV 76920000 769E3FFF 000c4000
* opends60 333E0000 333E6FFF 00007000
* NETAPI32 71C40000 71C97FFF 00058000
* SHELL32 7C8D0000 7D0D3FFF 00804000
* SHLWAPI 77DA0000 77DF1FFF 00052000
* comctl32 77420000 77522FFF 00103000
* psapi 76B70000 76B7AFFF 0000b000
* instapi 48060000 48069FFF 0000a000
* sqlevn70 4F610000 4F7B8FFF 001a9000
* SQLOS 344D0000 344D4FFF 00005000
* rsaenh 68000000 6802EFFF 0002f000
* AUTHZ 76C40000 76C53FFF 00014000
* MSCOREE 79000000 79044FFF 00045000
* ole32 77670000 777A3FFF 00134000
* msv1_0 76C90000 76CB6FFF 00027000
* iphlpapi 76CF0000 76D09FFF 0001a000
* kerberos 62810000 62867FFF 00058000
* cryptdll 766E0000 766EBFFF 0000c000
* schannel 76750000 76776FFF 00027000
* COMRES 77010000 770D5FFF 000c6000
* XOLEHLP 628D0000 628D5FFF 00006000
* MSDTCPRX 628E0000 62957FFF 00078000
* msvcp60 780C0000 78120FFF 00061000
* MTXCLU 62960000 62978FFF 00019000
* VERSION 77B90000 77B97FFF 00008000
* WSOCK32 71BB0000 71BB8FFF 00009000
* OLEAUT32 77D00000 77D8BFFF 0008c000
* CLUSAPI 62980000 62991FFF 00012000
* RESUTILS 629A0000 629B2FFF 00013000
* DNSAPI 76ED0000 76EFEFFF 0002f000
* winrnr 76F70000 76F76FFF 00007000
* WLDAP32 76F10000 76F3DFFF 0002e000
* rasadhlp 76F80000 76F87FFF 00008000
* security 62DF0000 62DF3FFF 00004000
* msfte 63750000 639A8FFF 00259000
* dbghelp 639B0000 63AC4FFF 00115000
* WINTRUST 76BB0000 76BDAFFF 0002b000
* imagehlp 76C10000 76C38FFF 00029000
* dssenh 68100000 68123FFF 00024000
* hnetcfg 63D20000 63D78FFF 00059000
* wshtcpip 71AE0000 71AE7FFF 00008000
* NTMARTA 77E00000 77E21FFF 00022000
* SAMLIB 63DC0000 63DCEFFF 0000f000
* ntdsapi 766F0000 76704FFF 00015000
* xpsp2res 63E50000 64114FFF 002c5000
* CLBCatQ 777B0000 77832FFF 00083000
* sqlncli 64120000 64343FFF 00224000
* COMCTL32 77530000 775C6FFF 00097000
* comdlg32 762B0000 762F9FFF 0004a000
* SQLNCLIR 007A0000 007D2FFF 00033000
* msftepxy 645D0000 645E4FFF 00015000
* EntApi 65E90000 65EA2FFF 00013000
* WININET 77210000 772B7FFF 000a8000
* xpsqlbot 66100000 66105FFF 00006000
* xpstar90 66120000 66168FFF 00049000
* SQLSCM90 66180000 66188FFF 00009000
* ODBC32 661A0000 661DCFFF 0003d000
* BatchParser90 661E0000 661FEFFF 0001f000
* ATL80 7C630000 7C64AFFF 0001b000
* odbcint 664D0000 664E6FFF 00017000
* xpstar90 664F0000 66515FFF 00026000
* xplog70 66520000 6652BFFF 0000c000
* xplog70 66540000 66542FFF 00003000
* odsole70 66550000 6655EFFF 0000f000
* SXS 66BD0000 66C8BFFF 000bc000
* oledb32 668E0000 66958FFF 00079000
* MSDART 64510000 64529FFF 0001a000
* OLEDB32R 64530000 64540FFF 00011000
* msdaora 66FF0000 67030FFF 00041000
* MSDATL3 66BA0000 66BB4FFF 00015000
* MSDAORAR 644F0000 644F3FFF 00004000
* oci 67040000 67096FFF 00057000
* MSVCR71 7C340000 7C395FFF 00056000
* OCIW32 670A0000 670F5FFF 00056000
* ORACLIENT10 67100000 67351FFF 00252000
* oracore10 67360000 67442FFF 000e3000
* oranls10 67450000 67513FFF 000c4000
* oraunls10 67520000 67537FFF 00018000
* orauts 66BC0000 66BC6FFF 00007000
* WINMM 76AA0000 76ACCFFF 0002d000
* oravsn10 67540000 67545FFF 00006000
* oracommon10 67550000 67641FFF 000f2000
* orageneric10 67650000 67BA6FFF 00557000
* orasnls10 67BB0000 67BD6FFF 00027000
* oraxml10 67BE0000 67D3FFFF 00160000
* MSVCIRT 67D40000 67D4FFFF 00010000
* oran10 67D50000 67E5CFFF 0010d000
* oranl10 67E60000 67E9CFFF 0003d000
* oranldap10 67EA0000 67EB6FFF 00017000
* orannzsbb10 67EC0000 67FC8FFF 00109000
* oraldapclnt10 68030000 68082FFF 00053000
* orancrypt10 67FD0000 67FEAFFF 0001b000
* oranro10 68090000 680DBFFF 0004c000
* oranhost10 67FF0000 67FF6FFF 00007000
* orancds10 680E0000 680E5FFF 00006000
* orantns10 680F0000 680F7FFF 00008000
* orapls10 68130000 68487FFF 00358000
* oraslax10 68490000 68498FFF 00009000
* oraplp10 684A0000 686A3FFF 00204000
* orahasgen10 686B0000 6873AFFF 0008b000
* oraocr10 68740000 687A9FFF 0006a000
* oraocrb10 687B0000 687EFFFF 00040000
* orantcp10 687F0000 687FFFFF 00010000
* orasql10 68800000 68899FFF 0009a000
* comsvcs 68B10000 68C48FFF 00139000
* activeds 76DF0000 76E22FFF 00033000
* adsldpc 76DC0000 76DE6FFF 00027000
* credui 76B80000 76BADFFF 0002e000
* ATL 76A80000 76A97FFF 00018000
* msadce 68DD0000 68E27FFF 00058000
* msadcer 68D70000 68D74FFF 00005000
* sqlmap90 6A090000 6A0ADFFF 0001e000
* MAPI32 6A0C0000 6A0DEFFF 0001f000
* sqlmap90 6A0E0000 6A0E5FFF 00006000
* MSMAPI32 6A0F0000 6A24BFFF 0015c000
* MAPIR 6A570000 6A62FFFF 000c0000
* mso 6AAC0000 6B67CFFF 00bbd000
* EMSABP32 6B690000 6B6D2FFF 00043000
* MPRAPI 76CD0000 76CE8FFF 00019000
* rtutils 76E30000 76E3BFFF 0000c000
* SETUPAPI 770E0000 771E9FFF 0010a000
* netman 77840000 77882FFF 00043000
* netshell 76300000 764C0FFF 001c1000
* RASAPI32 76E90000 76ECEFFF 0003f000
* rasman 76E40000 76E51FFF 00012000
* TAPI32 76E60000 76E8EFFF 0002f000
* WZCSAPI 6B820000 6B82CFFF 0000d000
* WZCSvc 77890000 77900FFF 00071000
* WMI 76CC0000 76CC4FFF 00005000
* DHCPCSVC 76D10000 76D2EFFF 0001f000
* WTSAPI32 76F00000 76F07FFF 00008000
* WINSTA 771F0000 77200FFF 00011000
* ESENT 6B830000 6B934FFF 00105000
* contab32 6C4E0000 6C4FEFFF 0001f000
* EMSMDB32 6C510000 6C5BEFFF 000af000
* encryption 6C930000 6C936FFF 00007000
* MSVBVM60 6C940000 6CA91FFF 00152000
* Dciph32 02C40000 02C4DFFF 0000e000
* dbghelp 69530000 69644FFF 00115000
*
* Edi: 6995E178: 6533D2F8 77F5E95E 00000000 6995E2C8 00000000
77FC2190
* Esi: 00000000:
* Eax: 6995E05C: 000042AC 00000000 00000000 77E55E02 00000000
0000000C
* Ebx: 0000003F:
* Ecx: 6995E6CC: 00000000 00010007 00000000 00460044 6533D2FC
6995E08C
* Edx: 0000003D:
* Eip: 77E55E02: 10C2C95E 90909000 A1649090 00000018 C334408B
891C428B
* Ebp: 6995E0AC: 6995E0F0 021A29C4 000042AC 00000000 00000000
00000000
* SegCs: 0000001B:
* EFlags: 00000246:
* Esp: 6995E058: 00000000 000042AC 00000000 00000000 77E55E02
00000000
* SegSs: 78130023: 00000000 00000000 00000000 00000000 00000000
00000000
*
*******************************************************************************
*
----
* Short Stack Dump
77E55E02 Module(kernel32+00015E02)
021A29C4 Module(sqlservr+011A29C4)
021A6880 Module(sqlservr+011A6880)
021A642D Module(sqlservr+011A642D)
02414429 Module(sqlservr+01414429)
77E99F7A Module(kernel32+00059F7A)
78138B5E Module(MSVCR80+00008B5E)
781329C1 Module(MSVCR80+000029C1)
78132A36 Module(MSVCR80+00002A36)

Monday, February 20, 2012

Missing files after using File System Task

Hi All,

I don't know if anyone faced this issue. We are having a strange problem. Our process was working well when it was implemented on 32 bit processor.IT ran perfectly for 6 months with out a problem. But when we moved the packages to a 64 bit machine, this issue along with some other issues started to show up.

The issue is we are missing files in the source folder.

Our process is designed such that a source process, brings in a file and updates a status for the file in a audit table. The ETL process picks up the file, then assigns the status as ‘running’ when SRC process is complete and loads into Target DB, and updates ETL status to complete. But current problem is the ETL is losing files after it assigns the status as running. When we looked into the DB weather the data is loaded, we could not find any data related to these files.

we are have mapping level parameters for source path and target path.

We are using a For Each Loop task, and processing files(which are simple flat files) in the source path. The file name is stored in the mapping level parameter. Once the file is process we are moving them into a target path.

Our src and target file paths are on the same drive, just have src folder, inside src folder we have processed folder and failed folder. So files are picked from the source folder and moved into processed folder after processing. The files are not even moved to a failed folder.

There are lot other processing going on this box, and the trend observed is that when more processors are running at peak hour, the missing files’ count is more.

Right now we are refetching those files, as a work around, but does any one has any suggestion why this is happening or any better implementation suggestions?

Thanks

We solved our problem. This was due to the combination of problems.

1. Environment setup for our new 64 bit server

2. Use of event handler for 'On Error' instead of 'On task failure'.

3. Overwrite destination in move file task properties in Event handler.

4. Consistent connection (I don't exactly remember the word, but its in the properties of the connections in connection manager)

1st and 4th issue: The sympotom was the missing files were more when the system was too busy, also processing other packages. When we set up our initial 32 bit machine, we had our named pipes enabled on both client and server. so no issues. But in our new 64 bit environment, the server named pipes was disabled (Shared Memory, TCP/IP were enabled) and client's was enabled, so when client wants a connection, it looks in the same order, 1st Shared Memory, 2nd TCP/IP and last named pipes. But the server, only gives connection on first 2. So the connection were timing out in peak processing.
Added to that the connection properties in the package(4th issue), was not stable state, so every time, its encounters a task in the package which needs DB connection, its requests new connection. So this issue multiplied because the named pipes were disabled. So the solution to this both issues is, just enable named pipes on the server (or disable on client, enable is better since the process has extra options for connections). In the package conection properties, select connection as stable state. This option helps to have stable connection from the start of package execution to the end, instead of connection and disconnecting for each task.

2nd & 3rd issue: This issue was already present in our 32 bit also, but did not show up since we did not have connection failure error due to named pipes. Since connection was timing out on our new environment, each failure consitues to an error, so when the first error raised, the src file was moved to the destination folder(with overwrite destination option true). But due to connection failures, we had often multiple error events, so for subsequest error events, its tries to moved again the src file which is not present since it was moved the first time. So for subsequest errors, since we had overwrite destination option to true, the package first deletes the target files, and tries to move the file and fails, since the src file is not present. This leads to the missing file problem.
The solution to this problem is, just set overwrite destination option to false in file task. Based on your requirement, you can also have the event handler on the 'On Task Failure' event instead of 'on Error event'.
Hope this helps a lot of pains to lot of people, and saves lot of bucks to many companies.
Excuse my spelling mistakes if any.
Thanks,
Venkat

Monday, March 26, 2012

Model backup failed

Model backup failed

mobing data-posting again

Friday, March 23, 2012

mmc.exe - .dll files are corrupted

MMC recovery

Monday, March 12, 2012

missing tables

Missing System Stored Procedures

Missing System Stored Procedures

Missing system stored procedures

Missing system stored procedures

Missing System Stored Procedures

missing system databases folder from management studio

Friday, March 9, 2012

Missing Sql Server node

Missing Sql Server node

Wednesday, March 7, 2012

Missing RAM

Missing RAM

Missing RAM

Saturday, February 25, 2012

Missing Join Predicate error

Missing Join Predicate error

Monday, February 20, 2012

Missing files after using File System Task

Missing dll file

Blog Archive

About Me