I'm using Msde on a PC with XP SP2 acting as "server" and accessing a
database on a PC with XP SP2 acting as "client". I can backup my database
from the "client" using UNC format
"\\client.computer.name\share.name\file.name.b kp" but when trying to restore
it from the "client" PC i get errors. Any ideas about how to restore the bkp
file to server pc from the client without having to copy the bkp file to the
server and perform the restore from there? Thanks
hi,
Dithom wrote:
> I'm using Msde on a PC with XP SP2 acting as "server" and accessing a
> database on a PC with XP SP2 acting as "client". I can backup my
> database from the "client" using UNC format
> "\\client.computer.name\share.name\file.name.b kp" but when trying to
> restore it from the "client" PC i get errors. Any ideas about how to
> restore the bkp file to server pc from the client without having to
> copy the bkp file to the server and perform the restore from there?
> Thanks
what kind of exception do you get?
actually if you can backup on a remote share you should be able to restore
from it too..
the account(s) running the SQL Server and SQL Server Agent must have enought
privileges on the remote share...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
Showing posts with label sp2. Show all posts
Showing posts with label sp2. Show all posts
Friday, March 30, 2012
Monday, March 26, 2012
MSDE 2000 Release A - Instalation Problem in Windows XP SP2
I can't install MSDE release A in Windows XP SP2. I verified if Server
Service is started and it is ok. I also verified if File and Printer sharing
is checked on network properties and it is ok. The windows firewall also is
disabled but the instalation doesn't work. I run the follow comand setup.exe
sapwd="suportebsb." /L*v C:/MSDELog.log.
Anyone can help me?
Regards,
Cicero Galdino
******** This is the lastest lines in log instalation files
*******************
2005-06-01 16:49:35.64 spid4 Default collation successfully changed.
2005-06-01 16:49:35.67 spid4 Recovery complete.
2005-06-01 16:49:35.67 spid4 SQL global counter collection task is
created.
2005-06-01 16:49:35.69 spid4 Warning: override, autoexec procedures
skipped.
2005-06-01 16:49:43.36 spid4 SQL Server is terminating due to 'stop'
request from Service Control Manager.
=== Logging stopped: 01/06/2005 16:59:54 ===
MSI (c) (18:48) [16:59:54:724]: Note: 1: 1708
MSI (c) (18:48) [16:59:54:724]: Product: Microsoft SQL Server Desktop Engine
-- Installation operation failed.
MSI (c) (18:48) [16:59:54:724]: Grabbed execution mutex.
MSI (c) (18:48) [16:59:54:724]: Cleaning up uninstalled install packages, if
any exist
MSI (c) (18:48) [16:59:54:740]: MainEngineThread is returning 1603
=== Verbose logging stopped: 01/06/2005 16:59:54 ===
hi Cicero,
Cicero wrote:
> I can't install MSDE release A in Windows XP SP2. I verified if Server
> Service is started and it is ok. I also verified if File and Printer
> sharing is checked on network properties and it is ok. The windows
> firewall also is disabled but the instalation doesn't work. I run the
> follow comand setup.exe sapwd="suportebsb." /L*v C:/MSDELog.log.
please inspect your C:/MSDELog.log for
RETURN VALUE 3
entrie(s), that reports exeptions duting the install process...
about 10/15 lines before each entry some (sometime cryptic) descritpion of
the problem will be available
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
Service is started and it is ok. I also verified if File and Printer sharing
is checked on network properties and it is ok. The windows firewall also is
disabled but the instalation doesn't work. I run the follow comand setup.exe
sapwd="suportebsb." /L*v C:/MSDELog.log.
Anyone can help me?
Regards,
Cicero Galdino
******** This is the lastest lines in log instalation files
*******************
2005-06-01 16:49:35.64 spid4 Default collation successfully changed.
2005-06-01 16:49:35.67 spid4 Recovery complete.
2005-06-01 16:49:35.67 spid4 SQL global counter collection task is
created.
2005-06-01 16:49:35.69 spid4 Warning: override, autoexec procedures
skipped.
2005-06-01 16:49:43.36 spid4 SQL Server is terminating due to 'stop'
request from Service Control Manager.
=== Logging stopped: 01/06/2005 16:59:54 ===
MSI (c) (18:48) [16:59:54:724]: Note: 1: 1708
MSI (c) (18:48) [16:59:54:724]: Product: Microsoft SQL Server Desktop Engine
-- Installation operation failed.
MSI (c) (18:48) [16:59:54:724]: Grabbed execution mutex.
MSI (c) (18:48) [16:59:54:724]: Cleaning up uninstalled install packages, if
any exist
MSI (c) (18:48) [16:59:54:740]: MainEngineThread is returning 1603
=== Verbose logging stopped: 01/06/2005 16:59:54 ===
hi Cicero,
Cicero wrote:
> I can't install MSDE release A in Windows XP SP2. I verified if Server
> Service is started and it is ok. I also verified if File and Printer
> sharing is checked on network properties and it is ok. The windows
> firewall also is disabled but the instalation doesn't work. I run the
> follow comand setup.exe sapwd="suportebsb." /L*v C:/MSDELog.log.
please inspect your C:/MSDELog.log for
RETURN VALUE 3
entrie(s), that reports exeptions duting the install process...
about 10/15 lines before each entry some (sometime cryptic) descritpion of
the problem will be available
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
Monday, March 19, 2012
MSDE /XP Problem -Please Help
Hi,
I have2 machines connected to each other. Both the systems
have MS XP operating systems with SP2 patch on them. I
have installed MSDE SP3 on both the systems.
I would like to run a query from one machine on a database
on the other using osql.I was unable to. It gives an error
saying "Access denied"
Are there any settings that i will have to change. I want
one to be like a server and another a client. Each has
its own database.
osql -Usa -Ppassword -S<servername> <enter>
Does not work.
-ZS
If you aren't getting a logon failure, check to make sure you have port 1433
(or the MSDE sqlserver exe) set up as an exception in the XP SP2 firewall
settings.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"ZS" <anonymous@.discussions.microsoft.com> wrote in message
news:07f001c4b7af$fc2835f0$a301280a@.phx.gbl...
> Hi,
> I have2 machines connected to each other. Both the systems
> have MS XP operating systems with SP2 patch on them. I
> have installed MSDE SP3 on both the systems.
> I would like to run a query from one machine on a database
> on the other using osql.I was unable to. It gives an error
> saying "Access denied"
> Are there any settings that i will have to change. I want
> one to be like a server and another a client. Each has
> its own database.
> osql -Usa -Ppassword -S<servername> <enter>
> Does not work.
> -ZS
>
>
|||Thanks Greg. Yes the problem was with the firewall.
So it is fixed now. Thanks.
=ZS
>--Original Message--
>If you aren't getting a logon failure, check to make sure
you have port 1433
>(or the MSDE sqlserver exe) set up as an exception in the
XP SP2 firewall
>settings.
>HTH,
>--
>Greg Low [MVP]
>MSDE Manager SQL Tools
>www.whitebearconsulting.com
>"ZS" <anonymous@.discussions.microsoft.com> wrote in
message[vbcol=seagreen]
>news:07f001c4b7af$fc2835f0$a301280a@.phx.gbl...
systems[vbcol=seagreen]
database[vbcol=seagreen]
error[vbcol=seagreen]
want
>
>.
>
I have2 machines connected to each other. Both the systems
have MS XP operating systems with SP2 patch on them. I
have installed MSDE SP3 on both the systems.
I would like to run a query from one machine on a database
on the other using osql.I was unable to. It gives an error
saying "Access denied"
Are there any settings that i will have to change. I want
one to be like a server and another a client. Each has
its own database.
osql -Usa -Ppassword -S<servername> <enter>
Does not work.
-ZS
If you aren't getting a logon failure, check to make sure you have port 1433
(or the MSDE sqlserver exe) set up as an exception in the XP SP2 firewall
settings.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"ZS" <anonymous@.discussions.microsoft.com> wrote in message
news:07f001c4b7af$fc2835f0$a301280a@.phx.gbl...
> Hi,
> I have2 machines connected to each other. Both the systems
> have MS XP operating systems with SP2 patch on them. I
> have installed MSDE SP3 on both the systems.
> I would like to run a query from one machine on a database
> on the other using osql.I was unable to. It gives an error
> saying "Access denied"
> Are there any settings that i will have to change. I want
> one to be like a server and another a client. Each has
> its own database.
> osql -Usa -Ppassword -S<servername> <enter>
> Does not work.
> -ZS
>
>
|||Thanks Greg. Yes the problem was with the firewall.
So it is fixed now. Thanks.
=ZS
>--Original Message--
>If you aren't getting a logon failure, check to make sure
you have port 1433
>(or the MSDE sqlserver exe) set up as an exception in the
XP SP2 firewall
>settings.
>HTH,
>--
>Greg Low [MVP]
>MSDE Manager SQL Tools
>www.whitebearconsulting.com
>"ZS" <anonymous@.discussions.microsoft.com> wrote in
message[vbcol=seagreen]
>news:07f001c4b7af$fc2835f0$a301280a@.phx.gbl...
systems[vbcol=seagreen]
database[vbcol=seagreen]
error[vbcol=seagreen]
want
>
>.
>
msde & windows xp sp2 question
hosting an msde 2000 sp1 instance on a windows xp sp 2 box, what steps can i
take to ensure other workstations can connect? The msde instance was
created with merge modules, and I cannot update to sp3a without the
manufacturer providing an installation, which isn't going to happen
apparently. Currently, none of my workstations can connect; i've attempted
to add sqlsvr.exe to the exception list, and also open port 1433 tcp on the
host system, with no luck.
Any assistance would be greatly appreciated!
S. Purkiss.
Have you tried disabling the firewall & then attempting to connect? Does it
work?
Cheers,
James Goodman
"S Purkiss" <shel@.shel.com> wrote in message
news:MNqdnQgi5cqwVffcRVn-rw@.rogers.com...
> hosting an msde 2000 sp1 instance on a windows xp sp 2 box, what steps can
> i
> take to ensure other workstations can connect? The msde instance was
> created with merge modules, and I cannot update to sp3a without the
> manufacturer providing an installation, which isn't going to happen
> apparently. Currently, none of my workstations can connect; i've
> attempted
> to add sqlsvr.exe to the exception list, and also open port 1433 tcp on
> the
> host system, with no luck.
> Any assistance would be greatly appreciated!
> S. Purkiss.
>
>
|||Hi James
Yep, I've tried this. Disabling the firewall doesn't improve the situation.
I have two theories on this...
1. i've heard it said that sp2's firewall doesn't actually go all the way
down when turned off
2. perhaps some netoworking protocol for sql is turned off when sp2 is
installed?
Take care,
Sheldon
"James Goodman" <jamesATnorton-associates.co.ukREMOVE> wrote in message
news:ux8vBpGsEHA.3896@.TK2MSFTNGP15.phx.gbl...
> Have you tried disabling the firewall & then attempting to connect? Does
> it work?
>
> --
> Cheers,
> James Goodman
> "S Purkiss" <shel@.shel.com> wrote in message
> news:MNqdnQgi5cqwVffcRVn-rw@.rogers.com...
>
|||If you added sqlsvr.exe to the exception list that should open up port 1433
or whatever port your using if it is a named instance and also udp 1434.
Make sure you have file and print sharing enabled as well.
"S Purkiss" wrote:
> Hi James
> Yep, I've tried this. Disabling the firewall doesn't improve the situation.
> I have two theories on this...
> 1. i've heard it said that sp2's firewall doesn't actually go all the way
> down when turned off
> 2. perhaps some netoworking protocol for sql is turned off when sp2 is
> installed?
> Take care,
> Sheldon
>
> "James Goodman" <jamesATnorton-associates.co.ukREMOVE> wrote in message
> news:ux8vBpGsEHA.3896@.TK2MSFTNGP15.phx.gbl...
>
>
take to ensure other workstations can connect? The msde instance was
created with merge modules, and I cannot update to sp3a without the
manufacturer providing an installation, which isn't going to happen
apparently. Currently, none of my workstations can connect; i've attempted
to add sqlsvr.exe to the exception list, and also open port 1433 tcp on the
host system, with no luck.
Any assistance would be greatly appreciated!
S. Purkiss.
Have you tried disabling the firewall & then attempting to connect? Does it
work?
Cheers,
James Goodman
"S Purkiss" <shel@.shel.com> wrote in message
news:MNqdnQgi5cqwVffcRVn-rw@.rogers.com...
> hosting an msde 2000 sp1 instance on a windows xp sp 2 box, what steps can
> i
> take to ensure other workstations can connect? The msde instance was
> created with merge modules, and I cannot update to sp3a without the
> manufacturer providing an installation, which isn't going to happen
> apparently. Currently, none of my workstations can connect; i've
> attempted
> to add sqlsvr.exe to the exception list, and also open port 1433 tcp on
> the
> host system, with no luck.
> Any assistance would be greatly appreciated!
> S. Purkiss.
>
>
|||Hi James
Yep, I've tried this. Disabling the firewall doesn't improve the situation.
I have two theories on this...
1. i've heard it said that sp2's firewall doesn't actually go all the way
down when turned off
2. perhaps some netoworking protocol for sql is turned off when sp2 is
installed?
Take care,
Sheldon
"James Goodman" <jamesATnorton-associates.co.ukREMOVE> wrote in message
news:ux8vBpGsEHA.3896@.TK2MSFTNGP15.phx.gbl...
> Have you tried disabling the firewall & then attempting to connect? Does
> it work?
>
> --
> Cheers,
> James Goodman
> "S Purkiss" <shel@.shel.com> wrote in message
> news:MNqdnQgi5cqwVffcRVn-rw@.rogers.com...
>
|||If you added sqlsvr.exe to the exception list that should open up port 1433
or whatever port your using if it is a named instance and also udp 1434.
Make sure you have file and print sharing enabled as well.
"S Purkiss" wrote:
> Hi James
> Yep, I've tried this. Disabling the firewall doesn't improve the situation.
> I have two theories on this...
> 1. i've heard it said that sp2's firewall doesn't actually go all the way
> down when turned off
> 2. perhaps some netoworking protocol for sql is turned off when sp2 is
> installed?
> Take care,
> Sheldon
>
> "James Goodman" <jamesATnorton-associates.co.ukREMOVE> wrote in message
> news:ux8vBpGsEHA.3896@.TK2MSFTNGP15.phx.gbl...
>
>
msde & windows xp sp2 question
hosting an msde 2000 sp1 instance on a windows xp sp 2 box, what steps can i
take to ensure other workstations can connect? The msde instance was
created with merge modules, and I cannot update to sp3a without the
manufacturer providing an installation, which isn't going to happen
apparently. Currently, none of my workstations can connect; i've attempted
to add sqlsvr.exe to the exception list, and also open port 1433 tcp on the
host system, with no luck.
Any assistance would be greatly appreciated!
S. Purkiss.
S Purkiss wrote:
> hosting an msde 2000 sp1 instance on a windows xp sp 2 box, what steps can i
> take to ensure other workstations can connect? The msde instance was
> created with merge modules, and I cannot update to sp3a without the
> manufacturer providing an installation, which isn't going to happen
> apparently. Currently, none of my workstations can connect; i've attempted
> to add sqlsvr.exe to the exception list, and also open port 1433 tcp on the
> host system, with no luck.
> Any assistance would be greatly appreciated!
> S. Purkiss.
>
Hi Sheldon
For a default instance of MSDE you need to open TCP 1433.
For a named instance you need to open UDP 1434 and the TCP port that the
named instance is using. You can find this port from the registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\YourNamedInstance\MSSQLServer\SuperSocketNe tLib\Tcp, key TcpPort.
Good luck!
take to ensure other workstations can connect? The msde instance was
created with merge modules, and I cannot update to sp3a without the
manufacturer providing an installation, which isn't going to happen
apparently. Currently, none of my workstations can connect; i've attempted
to add sqlsvr.exe to the exception list, and also open port 1433 tcp on the
host system, with no luck.
Any assistance would be greatly appreciated!
S. Purkiss.
S Purkiss wrote:
> hosting an msde 2000 sp1 instance on a windows xp sp 2 box, what steps can i
> take to ensure other workstations can connect? The msde instance was
> created with merge modules, and I cannot update to sp3a without the
> manufacturer providing an installation, which isn't going to happen
> apparently. Currently, none of my workstations can connect; i've attempted
> to add sqlsvr.exe to the exception list, and also open port 1433 tcp on the
> host system, with no luck.
> Any assistance would be greatly appreciated!
> S. Purkiss.
>
Hi Sheldon
For a default instance of MSDE you need to open TCP 1433.
For a named instance you need to open UDP 1434 and the TCP port that the
named instance is using. You can find this port from the registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\YourNamedInstance\MSSQLServer\SuperSocketNe tLib\Tcp, key TcpPort.
Good luck!
Monday, February 20, 2012
msdb database size
My SQL Server 2005 SP2 msdb database is 230 GB. I tried shrinking it several
times and nothing changes. The log file is 1 mb. How can I tell what is
using up this space?USE msdb;
GO
SELECT TOP 10 OBJECT_NAME(id), *
FROM sys.sysindexes
WHERE indid IN (0,1)
ORDER BY used DESC;
--or
SELECT TOP 10 OBJECT_NAME([object_id]), *
FROM sys.dm_db_partition_stats
WHERE index_id IN (0,1)
ORDER BY in_row_reserved_page_count DESC;
"SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
news:771E4963-D5B2-4CEB-9209-00FF3B5F75A4@.microsoft.com...
> My SQL Server 2005 SP2 msdb database is 230 GB. I tried shrinking it
> several
> times and nothing changes. The log file is 1 mb. How can I tell what is
> using up this space?|||Aaron,
Thank you. I ran the second query and got an object with this name:
queue_messages_391672443
I cannot find this object in the tables...
"Aaron Bertrand [SQL Server MVP]" wrote:
> USE msdb;
> GO
> SELECT TOP 10 OBJECT_NAME(id), *
> FROM sys.sysindexes
> WHERE indid IN (0,1)
> ORDER BY used DESC;
> --or
> SELECT TOP 10 OBJECT_NAME([object_id]), *
> FROM sys.dm_db_partition_stats
> WHERE index_id IN (0,1)
> ORDER BY in_row_reserved_page_count DESC;
>
> "SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
> news:771E4963-D5B2-4CEB-9209-00FF3B5F75A4@.microsoft.com...
> > My SQL Server 2005 SP2 msdb database is 230 GB. I tried shrinking it
> > several
> > times and nothing changes. The log file is 1 mb. How can I tell what is
> > using up this space?
>
>|||Probably marked as a system table. This will generate a query that will
show you 10 sample rows from the table.
SELECT 'SELECT TOP 10 * FROM '
+ OBJECT_SCHEMA_NAME(object_id)
+ '.[' + name + ']'
FROM sys.all_objects
WHERE name = 'queue_messages_391672443';
Is it possible you are using service broker or event/query notifications and
messages are being placed on the queue but not sent out?
"SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
news:6F5B5B70-F929-4D5D-8A28-34E3BF84D098@.microsoft.com...
> Aaron,
> Thank you. I ran the second query and got an object with this name:
> queue_messages_391672443
> I cannot find this object in the tables...
> "Aaron Bertrand [SQL Server MVP]" wrote:
>> USE msdb;
>> GO
>> SELECT TOP 10 OBJECT_NAME(id), *
>> FROM sys.sysindexes
>> WHERE indid IN (0,1)
>> ORDER BY used DESC;
>> --or
>> SELECT TOP 10 OBJECT_NAME([object_id]), *
>> FROM sys.dm_db_partition_stats
>> WHERE index_id IN (0,1)
>> ORDER BY in_row_reserved_page_count DESC;
>>
>> "SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
>> news:771E4963-D5B2-4CEB-9209-00FF3B5F75A4@.microsoft.com...
>> > My SQL Server 2005 SP2 msdb database is 230 GB. I tried shrinking it
>> > several
>> > times and nothing changes. The log file is 1 mb. How can I tell what
>> > is
>> > using up this space?
>>|||I cannot find this table. The script returned a SQL statement with table
name that does not exist. We're not using service broker. What can we do to
stop the message and clear up them up?
"Aaron Bertrand [SQL Server MVP]" wrote:
> Probably marked as a system table. This will generate a query that will
> show you 10 sample rows from the table.
>
> SELECT 'SELECT TOP 10 * FROM '
> + OBJECT_SCHEMA_NAME(object_id)
> + '.[' + name + ']'
> FROM sys.all_objects
> WHERE name = 'queue_messages_391672443';
>
> Is it possible you are using service broker or event/query notifications and
> messages are being placed on the queue but not sent out?
>
>
>
> "SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
> news:6F5B5B70-F929-4D5D-8A28-34E3BF84D098@.microsoft.com...
> > Aaron,
> > Thank you. I ran the second query and got an object with this name:
> > queue_messages_391672443
> >
> > I cannot find this object in the tables...
> >
> > "Aaron Bertrand [SQL Server MVP]" wrote:
> >
> >> USE msdb;
> >> GO
> >>
> >> SELECT TOP 10 OBJECT_NAME(id), *
> >> FROM sys.sysindexes
> >> WHERE indid IN (0,1)
> >> ORDER BY used DESC;
> >>
> >> --or
> >>
> >> SELECT TOP 10 OBJECT_NAME([object_id]), *
> >> FROM sys.dm_db_partition_stats
> >> WHERE index_id IN (0,1)
> >> ORDER BY in_row_reserved_page_count DESC;
> >>
> >>
> >>
> >> "SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
> >> news:771E4963-D5B2-4CEB-9209-00FF3B5F75A4@.microsoft.com...
> >> > My SQL Server 2005 SP2 msdb database is 230 GB. I tried shrinking it
> >> > several
> >> > times and nothing changes. The log file is 1 mb. How can I tell what
> >> > is
> >> > using up this space?
> >>
> >>
> >>
>
>|||>I cannot find this table. The script returned a SQL statement with table
> name that does not exist. We're not using service broker. What can we do
> to
> stop the message and clear up them up?
Well if you "can't find the table" it's going to be hard for any of us to
suggest a way to "clear up" anything... maybe you should turn on Profiler
and watch for any T-SQL events that involve an object name like that... then
that might point you to some application you have running that is doing this
to you.
A|||Aaron,
Thank you for your assistance. I seem to be getting nowhere in getting to
the bottom of what is causing this. I don't know how Service Broker works
and whether it is responsible.
I'm running Profiler now and I am not getting anything. How do I view the
sys tables?
"Aaron Bertrand [SQL Server MVP]" wrote:
> >I cannot find this table. The script returned a SQL statement with table
> > name that does not exist. We're not using service broker. What can we do
> > to
> > stop the message and clear up them up?
> Well if you "can't find the table" it's going to be hard for any of us to
> suggest a way to "clear up" anything... maybe you should turn on Profiler
> and watch for any T-SQL events that involve an object name like that... then
> that might point you to some application you have running that is doing this
> to you.
> A
>
>|||> I'm running Profiler now and I am not getting anything. How do I view the
> sys tables?
There are tons of sys tables. Can you be more specific? What *EXACTLY* did
the query I sent earlier return? And what happened when you ran the output?
SELECT 'SELECT TOP 10 * FROM '
+ OBJECT_SCHEMA_NAME(object_id)
+ '.[' + name + ']'
FROM sys.all_objects
WHERE name = 'queue_messages_391672443';|||It generates this sql statement as output:
SELECT TOP 10 * FROM sys.[queue_messages_391672443]
"Aaron Bertrand [SQL Server MVP]" wrote:
> > I'm running Profiler now and I am not getting anything. How do I view the
> > sys tables?
> There are tons of sys tables. Can you be more specific? What *EXACTLY* did
> the query I sent earlier return? And what happened when you ran the output?
> SELECT 'SELECT TOP 10 * FROM '
> + OBJECT_SCHEMA_NAME(object_id)
> + '.[' + name + ']'
> FROM sys.all_objects
> WHERE name = 'queue_messages_391672443';
>
>|||And I'll ask again, what happens when you run *THAT* query?
"SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
news:EFEE4A62-F1A4-4171-81CC-D804033AD2E3@.microsoft.com...
> It generates this sql statement as output:
> SELECT TOP 10 * FROM sys.[queue_messages_391672443]|||Thanks Aaron,
I get an error:
Msg 208, Level 16, State 1, Line 1
Invalid object name 'sys.queue_messages_391672443'.
"Aaron Bertrand [SQL Server MVP]" wrote:
> And I'll ask again, what happens when you run *THAT* query?
>
> "SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
> news:EFEE4A62-F1A4-4171-81CC-D804033AD2E3@.microsoft.com...
> > It generates this sql statement as output:
> > SELECT TOP 10 * FROM sys.[queue_messages_391672443]
>
>|||I don't know, gremlins? Can you try running that query as sa or another
sysadmin? Maybe you can't select from it because you don't have privileges.
"SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
news:9FAB03FA-9A5D-455B-BC15-DDB1A7036A73@.microsoft.com...
> Thanks Aaron,
> I get an error:
> Msg 208, Level 16, State 1, Line 1
> Invalid object name 'sys.queue_messages_391672443'.
>
> "Aaron Bertrand [SQL Server MVP]" wrote:
>> And I'll ask again, what happens when you run *THAT* query?
>>
>> "SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
>> news:EFEE4A62-F1A4-4171-81CC-D804033AD2E3@.microsoft.com...
>> > It generates this sql statement as output:
>> > SELECT TOP 10 * FROM sys.[queue_messages_391672443]
>>|||With the help from Micrsoft, the culprit turned out to be a login
notification service that had gotten turned on (still a mysterie). The
service broker type service usese an internal table called LoginQueue that
was expanding by leaps and bound as result of login events. Since there was
no place for the notifications to be sent or received, the queue continued to
grow. We had to write a program to "receive messages" for 86 million
messages. Once the program received all the message we could then delete the
service and the associated internal table. Shrinking the database reclaimed
all the space.
Aaron, I really apreciate your involvement. Becaue of your query, we're
able to get Microsoft focused on how to identify the source and deal with it.
"Aaron Bertrand [SQL Server MVP]" wrote:
> I don't know, gremlins? Can you try running that query as sa or another
> sysadmin? Maybe you can't select from it because you don't have privileges.
>
> "SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
> news:9FAB03FA-9A5D-455B-BC15-DDB1A7036A73@.microsoft.com...
> > Thanks Aaron,
> > I get an error:
> > Msg 208, Level 16, State 1, Line 1
> > Invalid object name 'sys.queue_messages_391672443'.
> >
> >
> > "Aaron Bertrand [SQL Server MVP]" wrote:
> >
> >> And I'll ask again, what happens when you run *THAT* query?
> >>
> >>
> >>
> >> "SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
> >> news:EFEE4A62-F1A4-4171-81CC-D804033AD2E3@.microsoft.com...
> >> > It generates this sql statement as output:
> >> > SELECT TOP 10 * FROM sys.[queue_messages_391672443]
> >>
> >>
> >>
>
>
times and nothing changes. The log file is 1 mb. How can I tell what is
using up this space?USE msdb;
GO
SELECT TOP 10 OBJECT_NAME(id), *
FROM sys.sysindexes
WHERE indid IN (0,1)
ORDER BY used DESC;
--or
SELECT TOP 10 OBJECT_NAME([object_id]), *
FROM sys.dm_db_partition_stats
WHERE index_id IN (0,1)
ORDER BY in_row_reserved_page_count DESC;
"SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
news:771E4963-D5B2-4CEB-9209-00FF3B5F75A4@.microsoft.com...
> My SQL Server 2005 SP2 msdb database is 230 GB. I tried shrinking it
> several
> times and nothing changes. The log file is 1 mb. How can I tell what is
> using up this space?|||Aaron,
Thank you. I ran the second query and got an object with this name:
queue_messages_391672443
I cannot find this object in the tables...
"Aaron Bertrand [SQL Server MVP]" wrote:
> USE msdb;
> GO
> SELECT TOP 10 OBJECT_NAME(id), *
> FROM sys.sysindexes
> WHERE indid IN (0,1)
> ORDER BY used DESC;
> --or
> SELECT TOP 10 OBJECT_NAME([object_id]), *
> FROM sys.dm_db_partition_stats
> WHERE index_id IN (0,1)
> ORDER BY in_row_reserved_page_count DESC;
>
> "SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
> news:771E4963-D5B2-4CEB-9209-00FF3B5F75A4@.microsoft.com...
> > My SQL Server 2005 SP2 msdb database is 230 GB. I tried shrinking it
> > several
> > times and nothing changes. The log file is 1 mb. How can I tell what is
> > using up this space?
>
>|||Probably marked as a system table. This will generate a query that will
show you 10 sample rows from the table.
SELECT 'SELECT TOP 10 * FROM '
+ OBJECT_SCHEMA_NAME(object_id)
+ '.[' + name + ']'
FROM sys.all_objects
WHERE name = 'queue_messages_391672443';
Is it possible you are using service broker or event/query notifications and
messages are being placed on the queue but not sent out?
"SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
news:6F5B5B70-F929-4D5D-8A28-34E3BF84D098@.microsoft.com...
> Aaron,
> Thank you. I ran the second query and got an object with this name:
> queue_messages_391672443
> I cannot find this object in the tables...
> "Aaron Bertrand [SQL Server MVP]" wrote:
>> USE msdb;
>> GO
>> SELECT TOP 10 OBJECT_NAME(id), *
>> FROM sys.sysindexes
>> WHERE indid IN (0,1)
>> ORDER BY used DESC;
>> --or
>> SELECT TOP 10 OBJECT_NAME([object_id]), *
>> FROM sys.dm_db_partition_stats
>> WHERE index_id IN (0,1)
>> ORDER BY in_row_reserved_page_count DESC;
>>
>> "SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
>> news:771E4963-D5B2-4CEB-9209-00FF3B5F75A4@.microsoft.com...
>> > My SQL Server 2005 SP2 msdb database is 230 GB. I tried shrinking it
>> > several
>> > times and nothing changes. The log file is 1 mb. How can I tell what
>> > is
>> > using up this space?
>>|||I cannot find this table. The script returned a SQL statement with table
name that does not exist. We're not using service broker. What can we do to
stop the message and clear up them up?
"Aaron Bertrand [SQL Server MVP]" wrote:
> Probably marked as a system table. This will generate a query that will
> show you 10 sample rows from the table.
>
> SELECT 'SELECT TOP 10 * FROM '
> + OBJECT_SCHEMA_NAME(object_id)
> + '.[' + name + ']'
> FROM sys.all_objects
> WHERE name = 'queue_messages_391672443';
>
> Is it possible you are using service broker or event/query notifications and
> messages are being placed on the queue but not sent out?
>
>
>
> "SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
> news:6F5B5B70-F929-4D5D-8A28-34E3BF84D098@.microsoft.com...
> > Aaron,
> > Thank you. I ran the second query and got an object with this name:
> > queue_messages_391672443
> >
> > I cannot find this object in the tables...
> >
> > "Aaron Bertrand [SQL Server MVP]" wrote:
> >
> >> USE msdb;
> >> GO
> >>
> >> SELECT TOP 10 OBJECT_NAME(id), *
> >> FROM sys.sysindexes
> >> WHERE indid IN (0,1)
> >> ORDER BY used DESC;
> >>
> >> --or
> >>
> >> SELECT TOP 10 OBJECT_NAME([object_id]), *
> >> FROM sys.dm_db_partition_stats
> >> WHERE index_id IN (0,1)
> >> ORDER BY in_row_reserved_page_count DESC;
> >>
> >>
> >>
> >> "SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
> >> news:771E4963-D5B2-4CEB-9209-00FF3B5F75A4@.microsoft.com...
> >> > My SQL Server 2005 SP2 msdb database is 230 GB. I tried shrinking it
> >> > several
> >> > times and nothing changes. The log file is 1 mb. How can I tell what
> >> > is
> >> > using up this space?
> >>
> >>
> >>
>
>|||>I cannot find this table. The script returned a SQL statement with table
> name that does not exist. We're not using service broker. What can we do
> to
> stop the message and clear up them up?
Well if you "can't find the table" it's going to be hard for any of us to
suggest a way to "clear up" anything... maybe you should turn on Profiler
and watch for any T-SQL events that involve an object name like that... then
that might point you to some application you have running that is doing this
to you.
A|||Aaron,
Thank you for your assistance. I seem to be getting nowhere in getting to
the bottom of what is causing this. I don't know how Service Broker works
and whether it is responsible.
I'm running Profiler now and I am not getting anything. How do I view the
sys tables?
"Aaron Bertrand [SQL Server MVP]" wrote:
> >I cannot find this table. The script returned a SQL statement with table
> > name that does not exist. We're not using service broker. What can we do
> > to
> > stop the message and clear up them up?
> Well if you "can't find the table" it's going to be hard for any of us to
> suggest a way to "clear up" anything... maybe you should turn on Profiler
> and watch for any T-SQL events that involve an object name like that... then
> that might point you to some application you have running that is doing this
> to you.
> A
>
>|||> I'm running Profiler now and I am not getting anything. How do I view the
> sys tables?
There are tons of sys tables. Can you be more specific? What *EXACTLY* did
the query I sent earlier return? And what happened when you ran the output?
SELECT 'SELECT TOP 10 * FROM '
+ OBJECT_SCHEMA_NAME(object_id)
+ '.[' + name + ']'
FROM sys.all_objects
WHERE name = 'queue_messages_391672443';|||It generates this sql statement as output:
SELECT TOP 10 * FROM sys.[queue_messages_391672443]
"Aaron Bertrand [SQL Server MVP]" wrote:
> > I'm running Profiler now and I am not getting anything. How do I view the
> > sys tables?
> There are tons of sys tables. Can you be more specific? What *EXACTLY* did
> the query I sent earlier return? And what happened when you ran the output?
> SELECT 'SELECT TOP 10 * FROM '
> + OBJECT_SCHEMA_NAME(object_id)
> + '.[' + name + ']'
> FROM sys.all_objects
> WHERE name = 'queue_messages_391672443';
>
>|||And I'll ask again, what happens when you run *THAT* query?
"SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
news:EFEE4A62-F1A4-4171-81CC-D804033AD2E3@.microsoft.com...
> It generates this sql statement as output:
> SELECT TOP 10 * FROM sys.[queue_messages_391672443]|||Thanks Aaron,
I get an error:
Msg 208, Level 16, State 1, Line 1
Invalid object name 'sys.queue_messages_391672443'.
"Aaron Bertrand [SQL Server MVP]" wrote:
> And I'll ask again, what happens when you run *THAT* query?
>
> "SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
> news:EFEE4A62-F1A4-4171-81CC-D804033AD2E3@.microsoft.com...
> > It generates this sql statement as output:
> > SELECT TOP 10 * FROM sys.[queue_messages_391672443]
>
>|||I don't know, gremlins? Can you try running that query as sa or another
sysadmin? Maybe you can't select from it because you don't have privileges.
"SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
news:9FAB03FA-9A5D-455B-BC15-DDB1A7036A73@.microsoft.com...
> Thanks Aaron,
> I get an error:
> Msg 208, Level 16, State 1, Line 1
> Invalid object name 'sys.queue_messages_391672443'.
>
> "Aaron Bertrand [SQL Server MVP]" wrote:
>> And I'll ask again, what happens when you run *THAT* query?
>>
>> "SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
>> news:EFEE4A62-F1A4-4171-81CC-D804033AD2E3@.microsoft.com...
>> > It generates this sql statement as output:
>> > SELECT TOP 10 * FROM sys.[queue_messages_391672443]
>>|||With the help from Micrsoft, the culprit turned out to be a login
notification service that had gotten turned on (still a mysterie). The
service broker type service usese an internal table called LoginQueue that
was expanding by leaps and bound as result of login events. Since there was
no place for the notifications to be sent or received, the queue continued to
grow. We had to write a program to "receive messages" for 86 million
messages. Once the program received all the message we could then delete the
service and the associated internal table. Shrinking the database reclaimed
all the space.
Aaron, I really apreciate your involvement. Becaue of your query, we're
able to get Microsoft focused on how to identify the source and deal with it.
"Aaron Bertrand [SQL Server MVP]" wrote:
> I don't know, gremlins? Can you try running that query as sa or another
> sysadmin? Maybe you can't select from it because you don't have privileges.
>
> "SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
> news:9FAB03FA-9A5D-455B-BC15-DDB1A7036A73@.microsoft.com...
> > Thanks Aaron,
> > I get an error:
> > Msg 208, Level 16, State 1, Line 1
> > Invalid object name 'sys.queue_messages_391672443'.
> >
> >
> > "Aaron Bertrand [SQL Server MVP]" wrote:
> >
> >> And I'll ask again, what happens when you run *THAT* query?
> >>
> >>
> >>
> >> "SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
> >> news:EFEE4A62-F1A4-4171-81CC-D804033AD2E3@.microsoft.com...
> >> > It generates this sql statement as output:
> >> > SELECT TOP 10 * FROM sys.[queue_messages_391672443]
> >>
> >>
> >>
>
>
msdb corrupted in sql 2005 sp2, how to start with a new one?
Hi,
I get many errors about SSIS and SQL Agent.
msdb should be corrupted.
is there some way to start with a brand new msdb?
I'm going to
-install a new sql 2005 instance
-upgrade it with sp2
-copy the new msdb from the second instance to the first instance
is that correct?
ThanksI dont think reinstallation is necessary. Totally new msdb database can be
created by executing the script located at your install directory under path
Driveletter\Program files\Microsoft SQL Server\MSSQL\Install
File name is instmsdb.sql.
Lets see what experts recommend......
Manu
"Federico Caselli" wrote:
> Hi,
> I get many errors about SSIS and SQL Agent.
> msdb should be corrupted.
> is there some way to start with a brand new msdb?
> I'm going to
> -install a new sql 2005 instance
> -upgrade it with sp2
> -copy the new msdb from the second instance to the first instance
> is that correct?
> Thanks
>|||How do you know msdb is corrupt? Is there any important information that you
may be losing by replacing msdb? What about a recent backup?
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Federico Caselli" wrote:
> Hi,
> I get many errors about SSIS and SQL Agent.
> msdb should be corrupted.
> is there some way to start with a brand new msdb?
> I'm going to
> -install a new sql 2005 instance
> -upgrade it with sp2
> -copy the new msdb from the second instance to the first instance
> is that correct?
> Thanks
>
I get many errors about SSIS and SQL Agent.
msdb should be corrupted.
is there some way to start with a brand new msdb?
I'm going to
-install a new sql 2005 instance
-upgrade it with sp2
-copy the new msdb from the second instance to the first instance
is that correct?
ThanksI dont think reinstallation is necessary. Totally new msdb database can be
created by executing the script located at your install directory under path
Driveletter\Program files\Microsoft SQL Server\MSSQL\Install
File name is instmsdb.sql.
Lets see what experts recommend......
Manu
"Federico Caselli" wrote:
> Hi,
> I get many errors about SSIS and SQL Agent.
> msdb should be corrupted.
> is there some way to start with a brand new msdb?
> I'm going to
> -install a new sql 2005 instance
> -upgrade it with sp2
> -copy the new msdb from the second instance to the first instance
> is that correct?
> Thanks
>|||How do you know msdb is corrupt? Is there any important information that you
may be losing by replacing msdb? What about a recent backup?
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Federico Caselli" wrote:
> Hi,
> I get many errors about SSIS and SQL Agent.
> msdb should be corrupted.
> is there some way to start with a brand new msdb?
> I'm going to
> -install a new sql 2005 instance
> -upgrade it with sp2
> -copy the new msdb from the second instance to the first instance
> is that correct?
> Thanks
>
msdb corrupted in sql 2005 sp2, how to start with a new one?
Hi,
I get many errors about SSIS and SQL Agent.
msdb should be corrupted.
is there some way to start with a brand new msdb?
I'm going to
-install a new sql 2005 instance
-upgrade it with sp2
-copy the new msdb from the second instance to the first instance
is that correct?
Thanks
I dont think reinstallation is necessary. Totally new msdb database can be
created by executing the script located at your install directory under path
Driveletter\Program files\Microsoft SQL Server\MSSQL\Install
File name is instmsdb.sql.
Lets see what experts recommend......
Manu
"Federico Caselli" wrote:
> Hi,
> I get many errors about SSIS and SQL Agent.
> msdb should be corrupted.
> is there some way to start with a brand new msdb?
> I'm going to
> -install a new sql 2005 instance
> -upgrade it with sp2
> -copy the new msdb from the second instance to the first instance
> is that correct?
> Thanks
>
|||How do you know msdb is corrupt? Is there any important information that you
may be losing by replacing msdb? What about a recent backup?
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Federico Caselli" wrote:
> Hi,
> I get many errors about SSIS and SQL Agent.
> msdb should be corrupted.
> is there some way to start with a brand new msdb?
> I'm going to
> -install a new sql 2005 instance
> -upgrade it with sp2
> -copy the new msdb from the second instance to the first instance
> is that correct?
> Thanks
>
I get many errors about SSIS and SQL Agent.
msdb should be corrupted.
is there some way to start with a brand new msdb?
I'm going to
-install a new sql 2005 instance
-upgrade it with sp2
-copy the new msdb from the second instance to the first instance
is that correct?
Thanks
I dont think reinstallation is necessary. Totally new msdb database can be
created by executing the script located at your install directory under path
Driveletter\Program files\Microsoft SQL Server\MSSQL\Install
File name is instmsdb.sql.
Lets see what experts recommend......
Manu
"Federico Caselli" wrote:
> Hi,
> I get many errors about SSIS and SQL Agent.
> msdb should be corrupted.
> is there some way to start with a brand new msdb?
> I'm going to
> -install a new sql 2005 instance
> -upgrade it with sp2
> -copy the new msdb from the second instance to the first instance
> is that correct?
> Thanks
>
|||How do you know msdb is corrupt? Is there any important information that you
may be losing by replacing msdb? What about a recent backup?
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Federico Caselli" wrote:
> Hi,
> I get many errors about SSIS and SQL Agent.
> msdb should be corrupted.
> is there some way to start with a brand new msdb?
> I'm going to
> -install a new sql 2005 instance
> -upgrade it with sp2
> -copy the new msdb from the second instance to the first instance
> is that correct?
> Thanks
>
msdb corrupted in sql 2005 sp2, how to start with a new one?
Hi,
I get many errors about SSIS and SQL Agent.
msdb should be corrupted.
is there some way to start with a brand new msdb?
I'm going to
-install a new sql 2005 instance
-upgrade it with sp2
-copy the new msdb from the second instance to the first instance
is that correct?
ThanksI dont think reinstallation is necessary. Totally new msdb database can be
created by executing the script located at your install directory under path
Driveletter\Program files\Microsoft SQL Server\MSSQL\Install
File name is instmsdb.sql.
Lets see what experts recommend......
Manu
"Federico Caselli" wrote:
> Hi,
> I get many errors about SSIS and SQL Agent.
> msdb should be corrupted.
> is there some way to start with a brand new msdb?
> I'm going to
> -install a new sql 2005 instance
> -upgrade it with sp2
> -copy the new msdb from the second instance to the first instance
> is that correct?
> Thanks
>|||How do you know msdb is corrupt? Is there any important information that you
may be losing by replacing msdb? What about a recent backup?
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Federico Caselli" wrote:
> Hi,
> I get many errors about SSIS and SQL Agent.
> msdb should be corrupted.
> is there some way to start with a brand new msdb?
> I'm going to
> -install a new sql 2005 instance
> -upgrade it with sp2
> -copy the new msdb from the second instance to the first instance
> is that correct?
> Thanks
>
I get many errors about SSIS and SQL Agent.
msdb should be corrupted.
is there some way to start with a brand new msdb?
I'm going to
-install a new sql 2005 instance
-upgrade it with sp2
-copy the new msdb from the second instance to the first instance
is that correct?
ThanksI dont think reinstallation is necessary. Totally new msdb database can be
created by executing the script located at your install directory under path
Driveletter\Program files\Microsoft SQL Server\MSSQL\Install
File name is instmsdb.sql.
Lets see what experts recommend......
Manu
"Federico Caselli" wrote:
> Hi,
> I get many errors about SSIS and SQL Agent.
> msdb should be corrupted.
> is there some way to start with a brand new msdb?
> I'm going to
> -install a new sql 2005 instance
> -upgrade it with sp2
> -copy the new msdb from the second instance to the first instance
> is that correct?
> Thanks
>|||How do you know msdb is corrupt? Is there any important information that you
may be losing by replacing msdb? What about a recent backup?
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Federico Caselli" wrote:
> Hi,
> I get many errors about SSIS and SQL Agent.
> msdb should be corrupted.
> is there some way to start with a brand new msdb?
> I'm going to
> -install a new sql 2005 instance
> -upgrade it with sp2
> -copy the new msdb from the second instance to the first instance
> is that correct?
> Thanks
>
Subscribe to:
Posts (Atom)