Can't shrink log file

I have an SQL Server 2000 database where the data file is 120 MB and the log
file is 330 MB. For some reason I am now unable to shrink the log file,
which has never been a problem before. I am doing this in Enterprise
Manager, selecting Shrink Database then selecting the log file and the
"compress pages and truncate free space" option. It says that the entire 330
MB is being used and won't shrink it. How can I fix this? Is it OK to close
down SQL Server and just delete the log file?
GlennDon't delete the file. Check out http://www.karaszi.com/SQLServer/in...ink
.asp where you
find some information about shrinking log file.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Glenn Alcott" <galcott@.nyc.rr.com> wrote in message news:47616ac1$0$2353$4c368faf@.roadrunne
r.com...
>I have an SQL Server 2000 database where the data file is 120 MB and the lo
g
> file is 330 MB. For some reason I am now unable to shrink the log file,
> which has never been a problem before. I am doing this in Enterprise
> Manager, selecting Shrink Database then selecting the log file and the
> "compress pages and truncate free space" option. It says that the entire 3
30
> MB is being used and won't shrink it. How can I fix this? Is it OK to clos
e
> down SQL Server and just delete the log file?
> Glenn
>|||You most likely have an open transaction preventing the log from reusing the
space. Run DBCC OPENTRAN() in that db to see. If not you probably have the
recovery set to FULL but are not doing log backups.
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Glenn Alcott" <galcott@.nyc.rr.com> wrote in message
news:47616ac1$0$2353$4c368faf@.roadrunner
.com...
>I have an SQL Server 2000 database where the data file is 120 MB and the
>log
> file is 330 MB. For some reason I am now unable to shrink the log file,
> which has never been a problem before. I am doing this in Enterprise
> Manager, selecting Shrink Database then selecting the log file and the
> "compress pages and truncate free space" option. It says that the entire
> 330
> MB is being used and won't shrink it. How can I fix this? Is it OK to
> close
> down SQL Server and just delete the log file?
> Glenn
>|||Glenn,
You can always shrink the log using t-sql as well.
First you need to backup the log but in this case its for the purpose of
reducing the size and not actually saving the log.
BACKUP LOG WITH TRUNCATE_ONLY
then you need to use the dbcc shrink file command
DBCC SHRINKFILE (LogicalFilename, size you would like to reduce it to);
http://msdn2.microsoft.com/en-us/library/ms189493.aspx
that should take care of it.
--
/*
Warren Brunk - MCITP,MCTS,MCDBA
www.techintsolutions.com
*/
"Glenn Alcott" <galcott@.nyc.rr.com> wrote in message
news:47616ac1$0$2353$4c368faf@.roadrunner
.com...
>I have an SQL Server 2000 database where the data file is 120 MB and the
>log
> file is 330 MB. For some reason I am now unable to shrink the log file,
> which has never been a problem before. I am doing this in Enterprise
> Manager, selecting Shrink Database then selecting the log file and the
> "compress pages and truncate free space" option. It says that the entire
> 330
> MB is being used and won't shrink it. How can I fix this? Is it OK to
> close
> down SQL Server and just delete the log file?
> Glenn
>|||Try to Dump Tran Databasename with no_log command then selecting Shrink
Database
"Glenn Alcott" <galcott@.nyc.rr.com> wrote in message
news:47616ac1$0$2353$4c368faf@.roadrunner
.com...
> I have an SQL Server 2000 database where the data file is 120 MB and the
> log
> file is 330 MB. For some reason I am now unable to shrink the log file,
> which has never been a problem before. I am doing this in Enterprise
> Manager, selecting Shrink Database then selecting the log file and the
> "compress pages and truncate free space" option. It says that the entire
> 330
> MB is being used and won't shrink it. How can I fix this? Is it OK to
> close
> down SQL Server and just delete the log file?
> Glenn
>

Can't shrink log file

I have an SQL Server 2000 database where the data file is 120 MB and the log
file is 330 MB. For some reason I am now unable to shrink the log file,
which has never been a problem before. I am doing this in Enterprise
Manager, selecting Shrink Database then selecting the log file and the
"compress pages and truncate free space" option. It says that the entire 330
MB is being used and won't shrink it. How can I fix this? Is it OK to close
down SQL Server and just delete the log file?
Glenn
You most likely have an open transaction preventing the log from reusing the
space. Run DBCC OPENTRAN() in that db to see. If not you probably have the
recovery set to FULL but are not doing log backups.
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Glenn Alcott" <galcott@.nyc.rr.com> wrote in message
news:47616ac1$0$2353$4c368faf@.roadrunner.com...
>I have an SQL Server 2000 database where the data file is 120 MB and the
>log
> file is 330 MB. For some reason I am now unable to shrink the log file,
> which has never been a problem before. I am doing this in Enterprise
> Manager, selecting Shrink Database then selecting the log file and the
> "compress pages and truncate free space" option. It says that the entire
> 330
> MB is being used and won't shrink it. How can I fix this? Is it OK to
> close
> down SQL Server and just delete the log file?
> Glenn
>
|||Glenn,
You can always shrink the log using t-sql as well.
First you need to backup the log but in this case its for the purpose of
reducing the size and not actually saving the log.
BACKUP LOG WITH TRUNCATE_ONLY
then you need to use the dbcc shrink file command
DBCC SHRINKFILE (LogicalFilename, size you would like to reduce it to);
http://msdn2.microsoft.com/en-us/library/ms189493.aspx
that should take care of it.
/*
Warren Brunk - MCITP,MCTS,MCDBA
www.techintsolutions.com
*/
"Glenn Alcott" <galcott@.nyc.rr.com> wrote in message
news:47616ac1$0$2353$4c368faf@.roadrunner.com...
>I have an SQL Server 2000 database where the data file is 120 MB and the
>log
> file is 330 MB. For some reason I am now unable to shrink the log file,
> which has never been a problem before. I am doing this in Enterprise
> Manager, selecting Shrink Database then selecting the log file and the
> "compress pages and truncate free space" option. It says that the entire
> 330
> MB is being used and won't shrink it. How can I fix this? Is it OK to
> close
> down SQL Server and just delete the log file?
> Glenn
>
|||Try to Dump Tran Databasename with no_log command then selecting Shrink
Database
"Glenn Alcott" <galcott@.nyc.rr.com> wrote in message
news:47616ac1$0$2353$4c368faf@.roadrunner.com...
> I have an SQL Server 2000 database where the data file is 120 MB and the
> log
> file is 330 MB. For some reason I am now unable to shrink the log file,
> which has never been a problem before. I am doing this in Enterprise
> Manager, selecting Shrink Database then selecting the log file and the
> "compress pages and truncate free space" option. It says that the entire
> 330
> MB is being used and won't shrink it. How can I fix this? Is it OK to
> close
> down SQL Server and just delete the log file?
> Glenn
>

Can't shrink log file

I have an SQL Server 2000 database where the data file is 120 MB and the log
file is 330 MB. For some reason I am now unable to shrink the log file,
which has never been a problem before. I am doing this in Enterprise
Manager, selecting Shrink Database then selecting the log file and the
"compress pages and truncate free space" option. It says that the entire 330
MB is being used and won't shrink it. How can I fix this? Is it OK to close
down SQL Server and just delete the log file?
GlennDon't delete the file. Check out http://www.karaszi.com/SQLServer/info_dont_shrink.asp where you
find some information about shrinking log file.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Glenn Alcott" <galcott@.nyc.rr.com> wrote in message news:47616ac1$0$2353$4c368faf@.roadrunner.com...
>I have an SQL Server 2000 database where the data file is 120 MB and the log
> file is 330 MB. For some reason I am now unable to shrink the log file,
> which has never been a problem before. I am doing this in Enterprise
> Manager, selecting Shrink Database then selecting the log file and the
> "compress pages and truncate free space" option. It says that the entire 330
> MB is being used and won't shrink it. How can I fix this? Is it OK to close
> down SQL Server and just delete the log file?
> Glenn
>|||You most likely have an open transaction preventing the log from reusing the
space. Run DBCC OPENTRAN() in that db to see. If not you probably have the
recovery set to FULL but are not doing log backups.
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Glenn Alcott" <galcott@.nyc.rr.com> wrote in message
news:47616ac1$0$2353$4c368faf@.roadrunner.com...
>I have an SQL Server 2000 database where the data file is 120 MB and the
>log
> file is 330 MB. For some reason I am now unable to shrink the log file,
> which has never been a problem before. I am doing this in Enterprise
> Manager, selecting Shrink Database then selecting the log file and the
> "compress pages and truncate free space" option. It says that the entire
> 330
> MB is being used and won't shrink it. How can I fix this? Is it OK to
> close
> down SQL Server and just delete the log file?
> Glenn
>|||Glenn,
You can always shrink the log using t-sql as well.
First you need to backup the log but in this case its for the purpose of
reducing the size and not actually saving the log.
BACKUP LOG WITH TRUNCATE_ONLY
then you need to use the dbcc shrink file command
DBCC SHRINKFILE (LogicalFilename, size you would like to reduce it to);
http://msdn2.microsoft.com/en-us/library/ms189493.aspx
that should take care of it.
--
/*
Warren Brunk - MCITP,MCTS,MCDBA
www.techintsolutions.com
*/
"Glenn Alcott" <galcott@.nyc.rr.com> wrote in message
news:47616ac1$0$2353$4c368faf@.roadrunner.com...
>I have an SQL Server 2000 database where the data file is 120 MB and the
>log
> file is 330 MB. For some reason I am now unable to shrink the log file,
> which has never been a problem before. I am doing this in Enterprise
> Manager, selecting Shrink Database then selecting the log file and the
> "compress pages and truncate free space" option. It says that the entire
> 330
> MB is being used and won't shrink it. How can I fix this? Is it OK to
> close
> down SQL Server and just delete the log file?
> Glenn
>|||Try to Dump Tran Databasename with no_log command then selecting Shrink
Database
"Glenn Alcott" <galcott@.nyc.rr.com> wrote in message
news:47616ac1$0$2353$4c368faf@.roadrunner.com...
> I have an SQL Server 2000 database where the data file is 120 MB and the
> log
> file is 330 MB. For some reason I am now unable to shrink the log file,
> which has never been a problem before. I am doing this in Enterprise
> Manager, selecting Shrink Database then selecting the log file and the
> "compress pages and truncate free space" option. It says that the entire
> 330
> MB is being used and won't shrink it. How can I fix this? Is it OK to
> close
> down SQL Server and just delete the log file?
> Glenn
>

Can't see mapped drives

Hi,
Am unable to see mapped drive when going to restore db in
sql 2000 enterprise manager. Service is set to start
with a lan acct. acct is in the local machine admin grp
and remote machine admin grp.
Any suggestions:-)
Thanks in advanceDo not use mapped drives for backup\restore with SQL server. Use UNC names
instead. SQL may or may not see a mapped drive correctly but will always
find a UNC share that it has permission and connection to.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
<anonymous@.discussions.microsoft.com> wrote in message
news:8f9b01c40541$3ade3230$a301280a@.phx.gbl...
> Hi,
> Am unable to see mapped drive when going to restore db in
> sql 2000 enterprise manager. Service is set to start
> with a lan acct. acct is in the local machine admin grp
> and remote machine admin grp.
> Any suggestions:-)
> Thanks in advance|||Hi,
You cant see the mapped drives in Enterprise manager. Rather you can
directly mention the UNC path directly in Enterprise manager or use
Restore database command from Query Analyzer.
Restore database <dbname> from disk='\\machinename\share\backupfile.bak'
with stats=10 With
Move 'logicaldatafile' to physcaldatafile',
Move 'logiallogfile' to physcallogfile'
stats will show the restore status
Thanks
Hari
MCDBA
<anonymous@.discussions.microsoft.com> wrote in message
news:8f9b01c40541$3ade3230$a301280a@.phx.gbl...
> Hi,
> Am unable to see mapped drive when going to restore db in
> sql 2000 enterprise manager. Service is set to start
> with a lan acct. acct is in the local machine admin grp
> and remote machine admin grp.
> Any suggestions:-)
> Thanks in advance|||It is possible to get SQL Server to use mapped network drives, through the u
se of trace flag 1807.
Check out knowledge base article #304261 for full details
http://support.microsoft.com/defaul...1&Product=sql2k

Can't remove SA account or delete xp_cmdshell ext stored proc?

I'm trying to make my SQL Server a tad more secure, but I'm unable to remove
SA (I'm running Mixed mode) -- can the SA account only be removed when using
windows Authentication? When I try to remove SA I get "selected user
cannot be dropped because the user owns objects". When I try to delect
xp_cmdshell I get the following error "You tried to delete one or more
system objects. They were not deleted."
I must admit, I'm a little confused, I'm trying to implement Microsofts
security recommendations, but either the documention is not
detailed/accurate or I'm missing something?
Any suggestions?
Thanks, Rob.Hi
You can not remove the SA account. Set a very complicated password for it,
write it down and put it in a safe.
For the xp_ look at
http://support.microsoft.com/defaul...kb;en-us;891984
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Rob R. Ainscough" wrote:

> I'm trying to make my SQL Server a tad more secure, but I'm unable to remo
ve
> SA (I'm running Mixed mode) -- can the SA account only be removed when usi
ng
> windows Authentication? When I try to remove SA I get "selected user
> cannot be dropped because the user owns objects". When I try to delect
> xp_cmdshell I get the following error "You tried to delete one or more
> system objects. They were not deleted."
> I must admit, I'm a little confused, I'm trying to implement Microsofts
> security recommendations, but either the documention is not
> detailed/accurate or I'm missing something?
> Any suggestions?
> Thanks, Rob.
>
>
>|||> I'm trying to make my SQL Server a tad more secure, but I'm unable to
> remove SA (I'm running Mixed mode) -- can the SA account only be removed
> when using windows Authentication? When I try to remove SA I get
> "selected user cannot be dropped because the user owns objects". When I
> try to delect xp_cmdshell I get the following error "You tried to delete
> one or more system objects. They were not deleted."
The sa login account cannot be deleted or renameed, nor it can't be revoked
any permission.

> I must admit, I'm a little confused, I'm trying to implement Microsofts
> security recommendations, but either the documention is not
> detailed/accurate or I'm missing something?
I don't think MS ever mentioned droping the sa account (as it can't be
done). Here are recommendations from Operations Guide: "
The sa account in a production environment should be given a complex
password, made up of uppercase and lowercase letters, symbols, spaces, and
numbers. The sa account should have a complex password, even if the SQL
Server is running in only Windows Authentication Mode. A complex password
protects SQL Server from someone easily getting administrative access to SQL
Server. This also protects the server in the event that an administrator
changes the security authentication mode to Mixed Mode.
Do not use the sa login account in a production environment. Instead, place
each DBA's network user account into a Windows group, create a single SQL
Server login account for the group then add the login account to the
sysadmin fixed server role. "
(http://www.microsoft.com/technet/pr...in/sqlops3.mspx
).
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com|||Thank you for the information.
The book I was reading is Microsoft Press and the authors are Ed Robinson
and Michael James Bond.
I have the SA password complex so no worries there.
I guess I'll leave the xp_cmdshell alone as it seems to be more trouble that
it is worth to remove it.
Should I think about installing URLScan ?
"Dejan Sarka" <dejan_please_reply_to_newsgroups.sarka@.avtenta.si> wrote in
message news:%23BAAU89pFHA.3112@.TK2MSFTNGP12.phx.gbl...
> The sa login account cannot be deleted or renameed, nor it can't be
> revoked any permission.
>
> I don't think MS ever mentioned droping the sa account (as it can't be
> done). Here are recommendations from Operations Guide: "
> The sa account in a production environment should be given a complex
> password, made up of uppercase and lowercase letters, symbols, spaces, and
> numbers. The sa account should have a complex password, even if the SQL
> Server is running in only Windows Authentication Mode. A complex password
> protects SQL Server from someone easily getting administrative access to
> SQL Server. This also protects the server in the event that an
> administrator changes the security authentication mode to Mixed Mode.
> Do not use the sa login account in a production environment. Instead,
> place each DBA's network user account into a Windows group, create a
> single SQL Server login account for the group then add the login account
> to the sysadmin fixed server role. "
> (http://www.microsoft.com/technet/pr...ityLearning.com
>|||> Should I think about installing URLScan ?
Why don't you ask this in some IIS group, with explanation why do you think
you need it?
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com

Can't register remote SQL

When I try to register a remote SQL Server from a local desktop XP Pro PC, I
get the error:
"Client unable to establish connection. Named Pipes Provider: the network
path was not found. Timeout expired."
I checked and this is not a firewall problem because SQL ports are open. We
normally don't have a problem registering SQL servers like this; just this
one server. Any clues?
Thanks!!!
Is that particular server using Named Pipes, or is it set for TCP/IP? Check
the Server Network Utility to ensure Named Pipes is turned on on the server,
since your client appears to be using Named Pipes instead of TCP/IP.
"Dean J Garrett" <info@.amuletc.com> wrote in message
news:e4otsANKFHA.904@.tk2msftngp13.phx.gbl...
> When I try to register a remote SQL Server from a local desktop XP Pro PC,
> I
> get the error:
> "Client unable to establish connection. Named Pipes Provider: the network
> path was not found. Timeout expired."
> I checked and this is not a firewall problem because SQL ports are open.
> We
> normally don't have a problem registering SQL servers like this; just this
> one server. Any clues?
> Thanks!!!
>
|||Hello,
Yes, I thought of that before, but I just checked again and the Server
Network Util says enabled protocols:
Named Pipes
TCP/IP
We are trying to register the SQL server remotely using the server's IP addr
which has always worked in the past. Anyone know what is wrong?
Thanks!!!
"Michael C#" <xyz@.yomomma.com> wrote in message
news:#HM9QONKFHA.3064@.TK2MSFTNGP12.phx.gbl...
> Is that particular server using Named Pipes, or is it set for TCP/IP?
Check
> the Server Network Utility to ensure Named Pipes is turned on on the
server,[vbcol=seagreen]
> since your client appears to be using Named Pipes instead of TCP/IP.
> "Dean J Garrett" <info@.amuletc.com> wrote in message
> news:e4otsANKFHA.904@.tk2msftngp13.phx.gbl...
PC,[vbcol=seagreen]
network[vbcol=seagreen]
this
>
|||Interesting. You're using the TCP/IP address, but it's trying to connect
via Named Pipes? Have you checked the Client Network Utility on your client
box to see if TCP/IP is enabled locally? Also have you established
connectivity to the remote server? i.e., can you Ping the remote box? It
sounds like you're trying to connect via TCP/IP, but it's falling back to
Named Pipes. I'd check the network settings on the server and make sure
it's reachable from the local box. There's a utility called SQLPing at
http://sqlsecurity.com/DesktopDefault.aspx (w/ source code) that can help
determine if you can see the other server from the local box.
"Dean J Garrett" <info@.amuletc.com> wrote in message
news:OYoG%236NKFHA.2812@.TK2MSFTNGP15.phx.gbl...
> Hello,
> Yes, I thought of that before, but I just checked again and the Server
> Network Util says enabled protocols:
> Named Pipes
> TCP/IP
> We are trying to register the SQL server remotely using the server's IP
> addr
> which has always worked in the past. Anyone know what is wrong?
> Thanks!!!
>
> "Michael C#" <xyz@.yomomma.com> wrote in message
> news:#HM9QONKFHA.3064@.TK2MSFTNGP12.phx.gbl...
> Check
> server,
> PC,
> network
> this
>

Can't register remote SQL

When I try to register a remote SQL Server from a local desktop XP Pro PC, I
get the error:
"Client unable to establish connection. Named Pipes Provider: the network
path was not found. Timeout expired."
I checked and this is not a firewall problem because SQL ports are open. We
normally don't have a problem registering SQL servers like this; just this
one server. Any clues?
Thanks!!!Is that particular server using Named Pipes, or is it set for TCP/IP? Check
the Server Network Utility to ensure Named Pipes is turned on on the server,
since your client appears to be using Named Pipes instead of TCP/IP.
"Dean J Garrett" <info@.amuletc.com> wrote in message
news:e4otsANKFHA.904@.tk2msftngp13.phx.gbl...
> When I try to register a remote SQL Server from a local desktop XP Pro PC,
> I
> get the error:
> "Client unable to establish connection. Named Pipes Provider: the network
> path was not found. Timeout expired."
> I checked and this is not a firewall problem because SQL ports are open.
> We
> normally don't have a problem registering SQL servers like this; just this
> one server. Any clues?
> Thanks!!!
>|||Hello,
Yes, I thought of that before, but I just checked again and the Server
Network Util says enabled protocols:
Named Pipes
TCP/IP
We are trying to register the SQL server remotely using the server's IP addr
which has always worked in the past. Anyone know what is wrong?
Thanks!!!
"Michael C#" <xyz@.yomomma.com> wrote in message
news:#HM9QONKFHA.3064@.TK2MSFTNGP12.phx.gbl...
> Is that particular server using Named Pipes, or is it set for TCP/IP?
Check
> the Server Network Utility to ensure Named Pipes is turned on on the
server,
> since your client appears to be using Named Pipes instead of TCP/IP.
> "Dean J Garrett" <info@.amuletc.com> wrote in message
> news:e4otsANKFHA.904@.tk2msftngp13.phx.gbl...
> > When I try to register a remote SQL Server from a local desktop XP Pro
PC,
> > I
> > get the error:
> >
> > "Client unable to establish connection. Named Pipes Provider: the
network
> > path was not found. Timeout expired."
> >
> > I checked and this is not a firewall problem because SQL ports are open.
> > We
> > normally don't have a problem registering SQL servers like this; just
this
> > one server. Any clues?
> >
> > Thanks!!!
> >
> >
>|||Interesting. You're using the TCP/IP address, but it's trying to connect
via Named Pipes? Have you checked the Client Network Utility on your client
box to see if TCP/IP is enabled locally? Also have you established
connectivity to the remote server? i.e., can you Ping the remote box? It
sounds like you're trying to connect via TCP/IP, but it's falling back to
Named Pipes. I'd check the network settings on the server and make sure
it's reachable from the local box. There's a utility called SQLPing at
http://sqlsecurity.com/DesktopDefault.aspx (w/ source code) that can help
determine if you can see the other server from the local box.
"Dean J Garrett" <info@.amuletc.com> wrote in message
news:OYoG%236NKFHA.2812@.TK2MSFTNGP15.phx.gbl...
> Hello,
> Yes, I thought of that before, but I just checked again and the Server
> Network Util says enabled protocols:
> Named Pipes
> TCP/IP
> We are trying to register the SQL server remotely using the server's IP
> addr
> which has always worked in the past. Anyone know what is wrong?
> Thanks!!!
>
> "Michael C#" <xyz@.yomomma.com> wrote in message
> news:#HM9QONKFHA.3064@.TK2MSFTNGP12.phx.gbl...
>> Is that particular server using Named Pipes, or is it set for TCP/IP?
> Check
>> the Server Network Utility to ensure Named Pipes is turned on on the
> server,
>> since your client appears to be using Named Pipes instead of TCP/IP.
>> "Dean J Garrett" <info@.amuletc.com> wrote in message
>> news:e4otsANKFHA.904@.tk2msftngp13.phx.gbl...
>> > When I try to register a remote SQL Server from a local desktop XP Pro
> PC,
>> > I
>> > get the error:
>> >
>> > "Client unable to establish connection. Named Pipes Provider: the
> network
>> > path was not found. Timeout expired."
>> >
>> > I checked and this is not a firewall problem because SQL ports are
>> > open.
>> > We
>> > normally don't have a problem registering SQL servers like this; just
> this
>> > one server. Any clues?
>> >
>> > Thanks!!!
>> >
>> >
>>
>

Can't register remote SQL

When I try to register a remote SQL Server from a local desktop XP Pro PC, I
get the error:
"Client unable to establish connection. Named Pipes Provider: the network
path was not found. Timeout expired."
I checked and this is not a firewall problem because SQL ports are open. We
normally don't have a problem registering SQL servers like this; just this
one server. Any clues?
Thanks!!!Is that particular server using Named Pipes, or is it set for TCP/IP? Check
the Server Network Utility to ensure Named Pipes is turned on on the server,
since your client appears to be using Named Pipes instead of TCP/IP.
"Dean J Garrett" <info@.amuletc.com> wrote in message
news:e4otsANKFHA.904@.tk2msftngp13.phx.gbl...
> When I try to register a remote SQL Server from a local desktop XP Pro PC,
> I
> get the error:
> "Client unable to establish connection. Named Pipes Provider: the network
> path was not found. Timeout expired."
> I checked and this is not a firewall problem because SQL ports are open.
> We
> normally don't have a problem registering SQL servers like this; just this
> one server. Any clues?
> Thanks!!!
>|||Hello,
Yes, I thought of that before, but I just checked again and the Server
Network Util says enabled protocols:
Named Pipes
TCP/IP
We are trying to register the SQL server remotely using the server's IP addr
which has always worked in the past. Anyone know what is wrong?
Thanks!!!
"Michael C#" <xyz@.yomomma.com> wrote in message
news:#HM9QONKFHA.3064@.TK2MSFTNGP12.phx.gbl...
> Is that particular server using Named Pipes, or is it set for TCP/IP?
Check
> the Server Network Utility to ensure Named Pipes is turned on on the
server,
> since your client appears to be using Named Pipes instead of TCP/IP.
> "Dean J Garrett" <info@.amuletc.com> wrote in message
> news:e4otsANKFHA.904@.tk2msftngp13.phx.gbl...
PC,[vbcol=seagreen]
network[vbcol=seagreen]
this[vbcol=seagreen]
>|||Interesting. You're using the TCP/IP address, but it's trying to connect
via Named Pipes? Have you checked the Client Network Utility on your client
box to see if TCP/IP is enabled locally? Also have you established
connectivity to the remote server? i.e., can you Ping the remote box? It
sounds like you're trying to connect via TCP/IP, but it's falling back to
Named Pipes. I'd check the network settings on the server and make sure
it's reachable from the local box. There's a utility called SQLPing at
http://sqlsecurity.com/DesktopDefault.aspx (w/ source code) that can help
determine if you can see the other server from the local box.
"Dean J Garrett" <info@.amuletc.com> wrote in message
news:OYoG%236NKFHA.2812@.TK2MSFTNGP15.phx.gbl...
> Hello,
> Yes, I thought of that before, but I just checked again and the Server
> Network Util says enabled protocols:
> Named Pipes
> TCP/IP
> We are trying to register the SQL server remotely using the server's IP
> addr
> which has always worked in the past. Anyone know what is wrong?
> Thanks!!!
>
> "Michael C#" <xyz@.yomomma.com> wrote in message
> news:#HM9QONKFHA.3064@.TK2MSFTNGP12.phx.gbl...
> Check
> server,
> PC,
> network
> this
>

Can't re-attach database to sql server 2000

Hi,

My last post was terminated without the error message. To recap, I am unable to re-attach a database to a SQL server 2000 server after I detached it and attached it to a 2005 Server. When I detached it from the 2005 server and tried to re-attach it to the 2000 server I got the following error message:

" Error 5123: CREATE FILE encountered operating system error 5(Access denied) while attempting to create the physical file ..."

I tried using both the 2005 Server Management Studio and the 2000 Enterprise manager to do the re-attachement but got the same error message.

Any ideas on how I can reattach the files?

Thanks for your help.

Ken McLean

You can′t. During attaching the database to the SQL 2k5, the internal structure is migrated to SQL Server 2005 specific requirements which are not understanable for the SQL 2000 instance. This is one way only.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

Can't login to Enterprise Manager or Query Analyzer

Hello,
We are running SQL Server 7.0 databases on 3 separate
systems. We have found that recently we are unable to log
into these databases via Enterprise Manager (Enterprise
Manager will run by when you attempt to connect to the
database it will lock up). We were able to work around
that by just using Query Analyzer, but now that has
stopped working. The same problem: after being prompted
for user name/password (we are using SQL Server Security)
it hangs while displaying the "Connecting to..." message.
Has anyone encountered this before? We initially copied
the Query Analyzer executable (isqlw.exe) from the CD to
the server and that fixed it for a short time. Any ideas
on how to fix this permenantly and what is causing the
problem?
Thanks.Did you remove the default database for the logins? If so, you can change
it using sp_defaultdb via QA.
"Todd Biggar" <tbiggar@.nelcomail.com> wrote in message
news:03cb01c38dd0$3f9e7890$a301280a@.phx.gbl...
> Hello,
> We are running SQL Server 7.0 databases on 3 separate
> systems. We have found that recently we are unable to log
> into these databases via Enterprise Manager (Enterprise
> Manager will run by when you attempt to connect to the
> database it will lock up). We were able to work around
> that by just using Query Analyzer, but now that has
> stopped working. The same problem: after being prompted
> for user name/password (we are using SQL Server Security)
> it hangs while displaying the "Connecting to..." message.
> Has anyone encountered this before? We initially copied
> the Query Analyzer executable (isqlw.exe) from the CD to
> the server and that fixed it for a short time. Any ideas
> on how to fix this permenantly and what is causing the
> problem?
> Thanks.
>|||Unfortunately we can't log in with QA either; it hangs on
us too. The actual applications we wrote to hit the
database seem to be connecting without any problems, but
neither Enterprise Manager nor Query Analyzer will respond
when we try to connect.
>--Original Message--
>Did you remove the default database for the logins? If
so, you can change
>it using sp_defaultdb via QA.
>"Todd Biggar" <tbiggar@.nelcomail.com> wrote in message
>news:03cb01c38dd0$3f9e7890$a301280a@.phx.gbl...
>> Hello,
>> We are running SQL Server 7.0 databases on 3 separate
>> systems. We have found that recently we are unable to
log
>> into these databases via Enterprise Manager (Enterprise
>> Manager will run by when you attempt to connect to the
>> database it will lock up). We were able to work around
>> that by just using Query Analyzer, but now that has
>> stopped working. The same problem: after being prompted
>> for user name/password (we are using SQL Server
Security)
>> it hangs while displaying the "Connecting to..."
message.
>> Has anyone encountered this before? We initially copied
>> the Query Analyzer executable (isqlw.exe) from the CD to
>> the server and that fixed it for a short time. Any
ideas
>> on how to fix this permenantly and what is causing the
>> problem?
>> Thanks.
>
>.
>|||I think what Scott was getting at was to try to log on using
osql from the command line and change the default database
if that's what the issue is. You can at least try to log in
using osql from the command line. If you need to change the
default database, you can use something along the lines of:
OSQL -S YourServer -E -Q "EXEC sp_defaultdb 'YourLogin',
'master'"
-Sue
On Wed, 8 Oct 2003 13:30:30 -0700, "Todd Biggar"
<tbiggar@.nelcomail.com> wrote:
>Unfortunately we can't log in with QA either; it hangs on
>us too. The actual applications we wrote to hit the
>database seem to be connecting without any problems, but
>neither Enterprise Manager nor Query Analyzer will respond
>when we try to connect.
>>--Original Message--
>>Did you remove the default database for the logins? If
>so, you can change
>>it using sp_defaultdb via QA.
>>"Todd Biggar" <tbiggar@.nelcomail.com> wrote in message
>>news:03cb01c38dd0$3f9e7890$a301280a@.phx.gbl...
>> Hello,
>> We are running SQL Server 7.0 databases on 3 separate
>> systems. We have found that recently we are unable to
>log
>> into these databases via Enterprise Manager (Enterprise
>> Manager will run by when you attempt to connect to the
>> database it will lock up). We were able to work around
>> that by just using Query Analyzer, but now that has
>> stopped working. The same problem: after being prompted
>> for user name/password (we are using SQL Server
>Security)
>> it hangs while displaying the "Connecting to..."
>message.
>> Has anyone encountered this before? We initially copied
>> the Query Analyzer executable (isqlw.exe) from the CD to
>> the server and that fixed it for a short time. Any
>ideas
>> on how to fix this permenantly and what is causing the
>> problem?
>> Thanks.
>>
>>.|||Unfortunately this doesn't work either; I've tried various combinations of
usernames, database names and login names but even running osql is
non-responsive. It will just sit there at the prompt until I break out.
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:8r09ovouoej90ecvvgtn3taunct8t8rohi@.4ax.com...
> I think what Scott was getting at was to try to log on using
> osql from the command line and change the default database
> if that's what the issue is. You can at least try to log in
> using osql from the command line. If you need to change the
> default database, you can use something along the lines of:
> OSQL -S YourServer -E -Q "EXEC sp_defaultdb 'YourLogin',
> 'master'"
> -Sue
> On Wed, 8 Oct 2003 13:30:30 -0700, "Todd Biggar"
> <tbiggar@.nelcomail.com> wrote:
> >Unfortunately we can't log in with QA either; it hangs on
> >us too. The actual applications we wrote to hit the
> >database seem to be connecting without any problems, but
> >neither Enterprise Manager nor Query Analyzer will respond
> >when we try to connect.
> >
> >>--Original Message--
> >>Did you remove the default database for the logins? If
> >so, you can change
> >>it using sp_defaultdb via QA.
> >>
> >>"Todd Biggar" <tbiggar@.nelcomail.com> wrote in message
> >>news:03cb01c38dd0$3f9e7890$a301280a@.phx.gbl...
> >> Hello,
> >>
> >> We are running SQL Server 7.0 databases on 3 separate
> >> systems. We have found that recently we are unable to
> >log
> >> into these databases via Enterprise Manager (Enterprise
> >> Manager will run by when you attempt to connect to the
> >> database it will lock up). We were able to work around
> >> that by just using Query Analyzer, but now that has
> >> stopped working. The same problem: after being prompted
> >> for user name/password (we are using SQL Server
> >Security)
> >> it hangs while displaying the "Connecting to..."
> >message.
> >>
> >> Has anyone encountered this before? We initially copied
> >> the Query Analyzer executable (isqlw.exe) from the CD to
> >> the server and that fixed it for a short time. Any
> >ideas
> >> on how to fix this permenantly and what is causing the
> >> problem?
> >>
> >> Thanks.
> >>
> >>
> >>
> >>.
> >>
>|||You'll probably want to go through your SQL Server error
logs and try to find out what the problem is. Also, check
the status of the service in the services applet - I've seen
something similar when the service was hung up in a
"Starting" status (it should say "Started" not starting).
-Sue
On Thu, 9 Oct 2003 10:44:21 -0500, "Todd Biggar"
<tbiggar@.new.rr.com> wrote:
>Unfortunately this doesn't work either; I've tried various combinations of
>usernames, database names and login names but even running osql is
>non-responsive. It will just sit there at the prompt until I break out.
>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
>news:8r09ovouoej90ecvvgtn3taunct8t8rohi@.4ax.com...
>> I think what Scott was getting at was to try to log on using
>> osql from the command line and change the default database
>> if that's what the issue is. You can at least try to log in
>> using osql from the command line. If you need to change the
>> default database, you can use something along the lines of:
>> OSQL -S YourServer -E -Q "EXEC sp_defaultdb 'YourLogin',
>> 'master'"
>> -Sue
>> On Wed, 8 Oct 2003 13:30:30 -0700, "Todd Biggar"
>> <tbiggar@.nelcomail.com> wrote:
>> >Unfortunately we can't log in with QA either; it hangs on
>> >us too. The actual applications we wrote to hit the
>> >database seem to be connecting without any problems, but
>> >neither Enterprise Manager nor Query Analyzer will respond
>> >when we try to connect.
>> >
>> >>--Original Message--
>> >>Did you remove the default database for the logins? If
>> >so, you can change
>> >>it using sp_defaultdb via QA.
>> >>
>> >>"Todd Biggar" <tbiggar@.nelcomail.com> wrote in message
>> >>news:03cb01c38dd0$3f9e7890$a301280a@.phx.gbl...
>> >> Hello,
>> >>
>> >> We are running SQL Server 7.0 databases on 3 separate
>> >> systems. We have found that recently we are unable to
>> >log
>> >> into these databases via Enterprise Manager (Enterprise
>> >> Manager will run by when you attempt to connect to the
>> >> database it will lock up). We were able to work around
>> >> that by just using Query Analyzer, but now that has
>> >> stopped working. The same problem: after being prompted
>> >> for user name/password (we are using SQL Server
>> >Security)
>> >> it hangs while displaying the "Connecting to..."
>> >message.
>> >>
>> >> Has anyone encountered this before? We initially copied
>> >> the Query Analyzer executable (isqlw.exe) from the CD to
>> >> the server and that fixed it for a short time. Any
>> >ideas
>> >> on how to fix this permenantly and what is causing the
>> >> problem?
>> >>
>> >> Thanks.
>> >>
>> >>
>> >>
>> >>.
>> >>
>|||Turns out the default network libary got changed to Named Pipes somehow. I
removed all the entries in the Client Utility and readded them and now it
works.
Thanks for all the help!
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:8r09ovouoej90ecvvgtn3taunct8t8rohi@.4ax.com...
> I think what Scott was getting at was to try to log on using
> osql from the command line and change the default database
> if that's what the issue is. You can at least try to log in
> using osql from the command line. If you need to change the
> default database, you can use something along the lines of:
> OSQL -S YourServer -E -Q "EXEC sp_defaultdb 'YourLogin',
> 'master'"
> -Sue
> On Wed, 8 Oct 2003 13:30:30 -0700, "Todd Biggar"
> <tbiggar@.nelcomail.com> wrote:
> >Unfortunately we can't log in with QA either; it hangs on
> >us too. The actual applications we wrote to hit the
> >database seem to be connecting without any problems, but
> >neither Enterprise Manager nor Query Analyzer will respond
> >when we try to connect.
> >
> >>--Original Message--
> >>Did you remove the default database for the logins? If
> >so, you can change
> >>it using sp_defaultdb via QA.
> >>
> >>"Todd Biggar" <tbiggar@.nelcomail.com> wrote in message
> >>news:03cb01c38dd0$3f9e7890$a301280a@.phx.gbl...
> >> Hello,
> >>
> >> We are running SQL Server 7.0 databases on 3 separate
> >> systems. We have found that recently we are unable to
> >log
> >> into these databases via Enterprise Manager (Enterprise
> >> Manager will run by when you attempt to connect to the
> >> database it will lock up). We were able to work around
> >> that by just using Query Analyzer, but now that has
> >> stopped working. The same problem: after being prompted
> >> for user name/password (we are using SQL Server
> >Security)
> >> it hangs while displaying the "Connecting to..."
> >message.
> >>
> >> Has anyone encountered this before? We initially copied
> >> the Query Analyzer executable (isqlw.exe) from the CD to
> >> the server and that fixed it for a short time. Any
> >ideas
> >> on how to fix this permenantly and what is causing the
> >> problem?
> >>
> >> Thanks.
> >>
> >>
> >>
> >>.
> >>
>

Cant Kill Process

Hi All,

I have a table called Test1 on a MS SQL 7 Database. Wes ran an insert on the table however it is now locking the table, so we are unable to do anything with the table.

We have tried to kill the process through both Enterprise Manager as well as Query Ananlyser however it still appears. If we try to drop the table it just sits there trying to complete this with no luck.

Is there anyway possible to be able to kill this??

Thanks
AnthonyROLLBACK can sometimes take hours. Try stop and restart MSSQLSERVER service.

Can't Install Integration Services on SQL 2005 (Windows Server 2003)

Hello - We have been unable to successfully install Integration Services with an instance of SQL 2005 running on a Windows Small Business Server 2003. Installation proceeds with no errors, but when you attempt to connect to the Integrations Services and browse to where it apparently exists, the SQL Server Managment Studio returns the following error:

TITLE: Connect to Server

Cannot connect to ABDI04.

ADDITIONAL INFORMATION:

Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476

Connect to SSIS Service on machine "ABDI04" failed:
The specified service does not exist as an installed service.
.

Connect to SSIS Service on machine "ABDI04" failed:
The specified service does not exist as an installed service.
.

BUTTONS:

OK

We have tried uninstalling the Integration Services, then reinstalling it and again applying SP2 with the same results.

Thank you.

did you check in the sql server configuration manager? were you able to view the SSIS service there?if yes, is the service started ? ? ?if not just start the services and try to logon

also did you check in C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt file if the installation was successful ? ? ?

|||

Hello Deepak -

I am not able to view SSIS in configuration manager and the service is not present with the other system services. Using your suggestion, I also verified the Summary txt file:

Microsoft SQL Server 2005 9.00.3042.00
==============================
OS Version : Microsoft Windows Server 2003 family, Service Pack 2 (Build 3790)
Time : Sat Jul 14 15:57:47 2007
ABDI04 : To change an existing instance of Microsoft SQL Server 2005 to a different edition of SQL Server 2005, you must run SQL Server 2005 Setup from the command prompt and include the SKUUPGRADE=1 parameter.
Machine : ABDI04
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.3042.00
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0016_ABDI04_SQLSupport_1.log
--
Machine : ABDI04
Product : Microsoft SQL Server Native Client
Product Version : 9.00.3042.00
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0016_ABDI04_SQLNCLI_1.log
--
Machine : ABDI04
Product : Microsoft Office 2003 Web Components
Product Version : 11.0.6558.0
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0016_ABDI04_OWC11_1.log
--
Machine : ABDI04
Product : Microsoft SQL Server 2005 Backward compatibility
Product Version : 8.05.2004
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0016_ABDI04_BackwardsCompat_1.log
--
Machine : ABDI04
Product : MSXML 6.0 Parser
Product Version : 6.10.1129.0
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0016_ABDI04_MSXML6_1.log
--
Machine : ABDI04
Product : Microsoft SQL Server 2005 Integration Services
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0016_ABDI04_DTS.log
--
Setup succeeded with the installation, inspect the log file completely for status on all the components.

Time : Sat Jul 14 16:03:43 2007

and it seems to confirm that the installation proceeded to a successful conclusion.

Do you have any other suggestions? Thank you very much - Bryan

|||Hi,

look if the "SQL Server Integration Services" is installed. If not, which version of SQL Server are you running on the machine (Therefore examine the "SQL Server (InstanceNamehere)" services mentioned in the SCM.

Jens K. Suessmeyer.

-
http:://www.sqlserver2005.de
-|||Hello,

we have exactly the same problem. We installed completely new installation of SQL 2005 Server to a new installation of Small Business 2003. We ensured that the "Integration Services" option in the installation was set to "install entirely" mark. After no error reported installation we found out that the "SSIS Service" is not present among the system services, not even in the SQL configuration manager services.

However, the installation log file reports:

Product : Microsoft SQL Server 2005 Integration Services
Product Version : 9.00.1399.06
Install : Successful

Of course, we are not able to connect or using the Integration services. So, the question is, how can we install the Integration Service into the system?

Can anyone help?
|||Is the service started ? Can be found in the Service control manager (SCM) in Windows.

Jens K. Suessmeyer

http://www.sqlserver2005.de
|||Well, as I said, the service did NOT install into the system. (We checked both the Windows System Services and SQL Service control manager). So the answer is NO, the service is not started (because is not installed).

Jonas
|||One more thing: could anyone provide us the information, what executable file is related to SSIS servise to launch (with the the proper command line switches, if any)?

We would like to locate this executable on the drive and try to launch it manually.

thanks

Cant insert new record to database.

SOS
I am working with SQL 2000 located on a Networksolutions server and I have a Test record I inserted manually, but I am unable to insert a new record and get this error "can't insert new record to database".
No doubt this is a no brainer, but I can't solve it.
Many Thanks
Who ever you are.SOS
I am working with SQL 2000 located on a Networksolutions server and I have a Test record I inserted manually, but I am unable to insert a new record and get this error "can't insert new record to database".
No doubt this is a no brainer, but I can't solve it.
Many Thanks
Who ever you are.
Its too little info,plz provide more.This can occur due to lots of reason.|||The Table was manually created in Enterprise Manager.
This is the Script :
= = =
if exists (select * from dbo.sysobjects where id = object_id(N'[dbo].[tblProfile]') and OBJECTPROPERTY(id, N'IsUserTable') = 1)
drop table [dbo].[tblProfile]
GO

CREATE TABLE [dbo].[tblProfile] (
[ID] [int] IDENTITY (1, 1) NOT NULL ,
[Password] [varchar] (50) COLLATE Latin1_General_CI_AS NOT NULL ,
[FirstName] [varchar] (50) COLLATE Latin1_General_CI_AS NOT NULL ,
[LastName] [varchar] (50) COLLATE Latin1_General_CI_AS NOT NULL ,
[ZipCode] [varchar] (10) COLLATE Latin1_General_CI_AS NOT NULL ,
[Email] [varchar] (100) COLLATE Latin1_General_CI_AS NOT NULL ,
[Digit9] [varchar] (9) COLLATE Latin1_General_CI_AS NOT NULL ,
[Digit81] [varchar] (2) COLLATE Latin1_General_CI_AS NOT NULL ,
[Digit16] [varchar] (2) COLLATE Latin1_General_CI_AS NOT NULL ,
[StateAffiliation] [varchar] (9) COLLATE Latin1_General_CI_AS NOT NULL ,
[DateCreated] [datetime] NOT NULL ,
[DateUpdated] [datetime] NOT NULL
) ON [PRIMARY]
GO
The Connection String has been tested and is OK.
===
Thank you for your response|||Do you have insert statements for the record you inserted and the one you are attempting to insert?|||Hello and Thank you
I'm not sure what you mean by "insert statement"|||Let me make sure we are talking about the same thing. You have created the table that is scripted above. Now you are attempting to add data to this table by typing it into the table in enterprise manager. Is this correct?|||No.
The Table is for a Registration form.
Can't insert new record to database is the Error Message I get when I try to register a new user.
Sorry I was not clear.|||OK, as rudra said, could be lots of things. Here's my first suggestion, maybe the form is trying to put a value in the [ID] field.

Another thing, does the form retrieve data from the table before trying to write to it so you know it is not a security problem?

Is there any way you can display the output of the form before it sends it to the database. This sort of problem can be really hard to diagnose from a distance!!

Cant get SQL Server 2005 to work

Hello ia m trying to install SQL Server 2005 but i am unable to run it. I installed Net Framework 2.0
Then i have tried the following files:
SQLEXPR.EXE
SQLEXPR_ADV.EXE
Then i installed Service PAck 1 for that but an error occoured during the install.

Basiclly i have no idea what i am doing here. It creates a configuration tools start menu item but it seems just like configuration. In C:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Binn there is a file called sqlservr.exe but all it does is create a black console window and does nothing.

OS: XP Pro + SP2

How to get it to work?

Thank You

SQLEXPR.EXE is the installer for the edition SQL Express. SQLEXPR_ADV.exe is the installer for SQL Express Advanced. So if you ran both installers, you will now have two different editions on your machine. SQL Express Advanced comes with the option of installing Management Studio Express, a set of client tools available to view/edit/manage your database on your machine (or on remote machines). I'd suggest going through the Getting Started section of Books Online (the SQL documentation) for some suggested exercises.

Thanks,
Sam Lester (MSFT)

|||Thank You for Your reply.
I did not install them at the same time, i tried them both. I could not find the exe file to run the program. Is there such a thing. Ill read the getting started section also.|||

Which one did you fully install? If you installed Express, then it has no client tools (I think that's what you are searching for). If you installed Express Advanced, you have the option of installing Management Studio Express. Once this is installed, it will launch the UI-based tool that will allow you to browse through your instance.

Thanks,
Sam