Database Size Bloating after SP4.

Has anyone had any issues with a database doubling or tripling in size after
SP4 is installed? We have several databases that are structurely the same
however certain DB's have grown enormously in size without a large increase
in data. Whenever we try to shrink the Database it won't shrink to the
approximate size we are expecting. For example...
We have a DB that is 12.3GB with 3GB in data, 1 GB in indexes.
We have a DB that is 17.1GB with 3GB in data, 740MB in indexes.
We have a DB that is 7.8 GB with 4.6GB in data, 2.4GB in indexes.
The last one I understand.. it is where it should be.. However the first two
don't make any sense..
Can someone give me an idea.. I have tried defragging, shrinking.. etc.. Any
known problems that would cause this? Thanks for your help in advance!
You didn't say what sizes you log files are.
Have you looked at the DB Option 'trunc. log on chkpt.'? Is it on or off? If
it's off, then you log files could be growning and be the cause of your
large database sizes.
It's just a thought.
"Sam Davis" <SamDavis@.discussions.microsoft.com> wrote in message
news:CB4F5891-67A2-4535-BE1A-DAA3C0FE4FB1@.microsoft.com...
> Has anyone had any issues with a database doubling or tripling in size
> after
> SP4 is installed? We have several databases that are structurely the same
> however certain DB's have grown enormously in size without a large
> increase
> in data. Whenever we try to shrink the Database it won't shrink to the
> approximate size we are expecting. For example...
> We have a DB that is 12.3GB with 3GB in data, 1 GB in indexes.
> We have a DB that is 17.1GB with 3GB in data, 740MB in indexes.
> We have a DB that is 7.8 GB with 4.6GB in data, 2.4GB in indexes.
> The last one I understand.. it is where it should be.. However the first
> two
> don't make any sense..
> Can someone give me an idea.. I have tried defragging, shrinking.. etc..
> Any
> known problems that would cause this? Thanks for your help in advance!
|||Francis,
I have ran the shrinkfile however it returns a limited result. Such that I
can get the file down from 12GB to 10GB however it still seems like the
unused space that is reported isn't ever freed up..
"Francis" wrote:
[vbcol=seagreen]
> I have had SP4 running on 4 production servers and a couple of test servers
> for several months now without any of the issues that you mention. If you
> need to shrink your database and EM or the DBCC SHRINKDATABASE of DBCC
> SHRINKFILE isn't working then try this script:
> http://www.sqlservercentral.com/scri...p?scriptid=666
> I usuall find the DBCC SHRINKFILE works better than SHRINKDATABASE since I
> can control which file I want to schrink.
> Have you noticed that the database grows after doing a DBCC REINDEX? If so
> you may need extra free space, although 8-14 G seems excessive.
> "Sam Davis" wrote:
|||The log files are small 100-200 MB...
"Joe D" wrote:

> You didn't say what sizes you log files are.
> Have you looked at the DB Option 'trunc. log on chkpt.'? Is it on or off? If
> it's off, then you log files could be growning and be the cause of your
> large database sizes.
> It's just a thought.
>
> "Sam Davis" <SamDavis@.discussions.microsoft.com> wrote in message
> news:CB4F5891-67A2-4535-BE1A-DAA3C0FE4FB1@.microsoft.com...
>
>

Database Size Bloating after SP4.

Has anyone had any issues with a database doubling or tripling in size after
SP4 is installed? We have several databases that are structurely the same
however certain DB's have grown enormously in size without a large increase
in data. Whenever we try to shrink the Database it won't shrink to the
approximate size we are expecting. For example...
We have a DB that is 12.3GB with 3GB in data, 1 GB in indexes.
We have a DB that is 17.1GB with 3GB in data, 740MB in indexes.
We have a DB that is 7.8 GB with 4.6GB in data, 2.4GB in indexes.
The last one I understand.. it is where it should be.. However the first two
don't make any sense..
Can someone give me an idea.. I have tried defragging, shrinking.. etc.. Any
known problems that would cause this? Thanks for your help in advance!You didn't say what sizes you log files are.
Have you looked at the DB Option 'trunc. log on chkpt.'? Is it on or off? If
it's off, then you log files could be growning and be the cause of your
large database sizes.
It's just a thought.
"Sam Davis" <SamDavis@.discussions.microsoft.com> wrote in message
news:CB4F5891-67A2-4535-BE1A-DAA3C0FE4FB1@.microsoft.com...
> Has anyone had any issues with a database doubling or tripling in size
> after
> SP4 is installed? We have several databases that are structurely the same
> however certain DB's have grown enormously in size without a large
> increase
> in data. Whenever we try to shrink the Database it won't shrink to the
> approximate size we are expecting. For example...
> We have a DB that is 12.3GB with 3GB in data, 1 GB in indexes.
> We have a DB that is 17.1GB with 3GB in data, 740MB in indexes.
> We have a DB that is 7.8 GB with 4.6GB in data, 2.4GB in indexes.
> The last one I understand.. it is where it should be.. However the first
> two
> don't make any sense..
> Can someone give me an idea.. I have tried defragging, shrinking.. etc..
> Any
> known problems that would cause this? Thanks for your help in advance!|||Francis,
I have ran the shrinkfile however it returns a limited result. Such that I
can get the file down from 12GB to 10GB however it still seems like the
unused space that is reported isn't ever freed up..
"Francis" wrote:
[vbcol=seagreen]
> I have had SP4 running on 4 production servers and a couple of test server
s
> for several months now without any of the issues that you mention. If you
> need to shrink your database and EM or the DBCC SHRINKDATABASE of DBCC
> SHRINKFILE isn't working then try this script:
> http://www.sqlservercentral.com/scr...sp?scriptid=666
> I usuall find the DBCC SHRINKFILE works better than SHRINKDATABASE since I
> can control which file I want to schrink.
> Have you noticed that the database grows after doing a DBCC REINDEX? If s
o
> you may need extra free space, although 8-14 G seems excessive.
> "Sam Davis" wrote:
>|||The log files are small 100-200 MB...
"Joe D" wrote:

> You didn't say what sizes you log files are.
> Have you looked at the DB Option 'trunc. log on chkpt.'? Is it on or off?
If
> it's off, then you log files could be growning and be the cause of your
> large database sizes.
> It's just a thought.
>
> "Sam Davis" <SamDavis@.discussions.microsoft.com> wrote in message
> news:CB4F5891-67A2-4535-BE1A-DAA3C0FE4FB1@.microsoft.com...
>
>sql

Database Size Bloating after SP4.

Has anyone had any issues with a database doubling or tripling in size after
SP4 is installed? We have several databases that are structurely the same
however certain DB's have grown enormously in size without a large increase
in data. Whenever we try to shrink the Database it won't shrink to the
approximate size we are expecting. For example...
We have a DB that is 12.3GB with 3GB in data, 1 GB in indexes.
We have a DB that is 17.1GB with 3GB in data, 740MB in indexes.
We have a DB that is 7.8 GB with 4.6GB in data, 2.4GB in indexes.
The last one I understand.. it is where it should be.. However the first two
don't make any sense..
Can someone give me an idea.. I have tried defragging, shrinking.. etc.. Any
known problems that would cause this? Thanks for your help in advance!I have had SP4 running on 4 production servers and a couple of test servers
for several months now without any of the issues that you mention. If you
need to shrink your database and EM or the DBCC SHRINKDATABASE of DBCC
SHRINKFILE isn't working then try this script:
http://www.sqlservercentral.com/scripts/viewscript.asp?scriptid=666
I usuall find the DBCC SHRINKFILE works better than SHRINKDATABASE since I
can control which file I want to schrink.
Have you noticed that the database grows after doing a DBCC REINDEX? If so
you may need extra free space, although 8-14 G seems excessive.
"Sam Davis" wrote:
> Has anyone had any issues with a database doubling or tripling in size after
> SP4 is installed? We have several databases that are structurely the same
> however certain DB's have grown enormously in size without a large increase
> in data. Whenever we try to shrink the Database it won't shrink to the
> approximate size we are expecting. For example...
> We have a DB that is 12.3GB with 3GB in data, 1 GB in indexes.
> We have a DB that is 17.1GB with 3GB in data, 740MB in indexes.
> We have a DB that is 7.8 GB with 4.6GB in data, 2.4GB in indexes.
> The last one I understand.. it is where it should be.. However the first two
> don't make any sense..
> Can someone give me an idea.. I have tried defragging, shrinking.. etc.. Any
> known problems that would cause this? Thanks for your help in advance!|||You didn't say what sizes you log files are.
Have you looked at the DB Option 'trunc. log on chkpt.'? Is it on or off? If
it's off, then you log files could be growning and be the cause of your
large database sizes.
It's just a thought.
"Sam Davis" <SamDavis@.discussions.microsoft.com> wrote in message
news:CB4F5891-67A2-4535-BE1A-DAA3C0FE4FB1@.microsoft.com...
> Has anyone had any issues with a database doubling or tripling in size
> after
> SP4 is installed? We have several databases that are structurely the same
> however certain DB's have grown enormously in size without a large
> increase
> in data. Whenever we try to shrink the Database it won't shrink to the
> approximate size we are expecting. For example...
> We have a DB that is 12.3GB with 3GB in data, 1 GB in indexes.
> We have a DB that is 17.1GB with 3GB in data, 740MB in indexes.
> We have a DB that is 7.8 GB with 4.6GB in data, 2.4GB in indexes.
> The last one I understand.. it is where it should be.. However the first
> two
> don't make any sense..
> Can someone give me an idea.. I have tried defragging, shrinking.. etc..
> Any
> known problems that would cause this? Thanks for your help in advance!|||Francis,
I have ran the shrinkfile however it returns a limited result. Such that I
can get the file down from 12GB to 10GB however it still seems like the
unused space that is reported isn't ever freed up..
"Francis" wrote:
> I have had SP4 running on 4 production servers and a couple of test servers
> for several months now without any of the issues that you mention. If you
> need to shrink your database and EM or the DBCC SHRINKDATABASE of DBCC
> SHRINKFILE isn't working then try this script:
> http://www.sqlservercentral.com/scripts/viewscript.asp?scriptid=666
> I usuall find the DBCC SHRINKFILE works better than SHRINKDATABASE since I
> can control which file I want to schrink.
> Have you noticed that the database grows after doing a DBCC REINDEX? If so
> you may need extra free space, although 8-14 G seems excessive.
> "Sam Davis" wrote:
> > Has anyone had any issues with a database doubling or tripling in size after
> > SP4 is installed? We have several databases that are structurely the same
> > however certain DB's have grown enormously in size without a large increase
> > in data. Whenever we try to shrink the Database it won't shrink to the
> > approximate size we are expecting. For example...
> >
> > We have a DB that is 12.3GB with 3GB in data, 1 GB in indexes.
> > We have a DB that is 17.1GB with 3GB in data, 740MB in indexes.
> > We have a DB that is 7.8 GB with 4.6GB in data, 2.4GB in indexes.
> >
> > The last one I understand.. it is where it should be.. However the first two
> > don't make any sense..
> >
> > Can someone give me an idea.. I have tried defragging, shrinking.. etc.. Any
> > known problems that would cause this? Thanks for your help in advance!|||The log files are small 100-200 MB...
"Joe D" wrote:
> You didn't say what sizes you log files are.
> Have you looked at the DB Option 'trunc. log on chkpt.'? Is it on or off? If
> it's off, then you log files could be growning and be the cause of your
> large database sizes.
> It's just a thought.
>
> "Sam Davis" <SamDavis@.discussions.microsoft.com> wrote in message
> news:CB4F5891-67A2-4535-BE1A-DAA3C0FE4FB1@.microsoft.com...
> > Has anyone had any issues with a database doubling or tripling in size
> > after
> > SP4 is installed? We have several databases that are structurely the same
> > however certain DB's have grown enormously in size without a large
> > increase
> > in data. Whenever we try to shrink the Database it won't shrink to the
> > approximate size we are expecting. For example...
> >
> > We have a DB that is 12.3GB with 3GB in data, 1 GB in indexes.
> > We have a DB that is 17.1GB with 3GB in data, 740MB in indexes.
> > We have a DB that is 7.8 GB with 4.6GB in data, 2.4GB in indexes.
> >
> > The last one I understand.. it is where it should be.. However the first
> > two
> > don't make any sense..
> >
> > Can someone give me an idea.. I have tried defragging, shrinking.. etc..
> > Any
> > known problems that would cause this? Thanks for your help in advance!
>
>

Database setup script

I have MSDE installed on my machine as was wondering what the NETSDK is in the following commands.

@.rem Uncomment the following line for MSDE
@.rem set DBNAME=(local)\NETSDK
set DBNAME=(local)\NETSDK

Thanks,
Bob HIt would appear that NETSDK is the "instance name" of the MSDE installation.

With SQL Server 2000 (and MSDE), multiple instances of SQL Server can be installed. The first uses the "default instance"; that is, to access it, simply reference the name of the server in a connection string. To reference a non-default instance, follow the server with \<instance name>sql

Database recovery freezing server?

I'm currently running Windows Server 2003 and just recently installed SQL 2005. I had a few databases that I was attaching from the old SQL 2000 server. I encountered a hard error and when I restarted Management studio, I found 4 of my databases were in recovery. Thinking this would be a short process, I let it run and did work on one of my other machines. Nearly 2 hours later, the databases are still in recovery and nothing appears to have changed. I'm new to sql 2005 and don't know what the best method of bringing those databases back up would be. If it is possible to just detach the databases (or blow them away completely) I have backups that are plenty recent enough, however I find I am unable to make any changes to the databases while one of the system db's is in recovery. Any ideas?

KCanterucci,

I think you can find more accurate answer in sql server engine forum.

database recovery

The SBS 2003 server is blue screening. The client has not done any backup in
several months. I have pluged in another HDD, installed Standard 2003 and
then reconnected the old HDD as a second drive. All the data from the old HDD
is now visible and accessible. I can now comfortably recover all their data
except SQL database. Is there any way? Please help. Thanks in advance.
Chris
You might be able to attach the database files to the new installation. Read about sp_attach_db.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Chris Toffa" <ChrisToffa@.discussions.microsoft.com> wrote in message
news:289C92F0-38BF-40DE-B60D-D464F876DBCC@.microsoft.com...
> The SBS 2003 server is blue screening. The client has not done any backup in
> several months. I have pluged in another HDD, installed Standard 2003 and
> then reconnected the old HDD as a second drive. All the data from the old HDD
> is now visible and accessible. I can now comfortably recover all their data
> except SQL database. Is there any way? Please help. Thanks in advance.
> Chris
|||Tibor Im curious about your response. You say he "might" be able to attach,
what circumstances make this possible?
"Tibor Karaszi" wrote:

> You might be able to attach the database files to the new installation. Read about sp_attach_db.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Chris Toffa" <ChrisToffa@.discussions.microsoft.com> wrote in message
> news:289C92F0-38BF-40DE-B60D-D464F876DBCC@.microsoft.com...
>
|||As long as there was no physical damage to the data or log files it should
work. When it attaches it will go thru recovery and roll forward or back as
needed to make the db consistent.
Andrew J. Kelly SQL MVP
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:ECD839A1-AC24-45BC-94D2-306A82B9397C@.microsoft.com...[vbcol=seagreen]
> Tibor Im curious about your response. You say he "might" be able to
> attach,
> what circumstances make this possible?
> "Tibor Karaszi" wrote:
|||> Tibor Im curious about your response. You say he "might" be able to attach,
> what circumstances make this possible?
Below is a quote from Books Online (2000) , sp_attach_db
"sp_attach_db should only be executed on databases that were previously detached from the database
server using an explicit sp_detach_db operation. "
We see posts almost here daily about "... crash ... attach... doesn't work". Granted, many of these
deleted the log file as well, but still. I like to play safe. Yes, I'd appreciate if MS would
provide a technical elaboration about specifically when attach work and when it doesn't. But without
such, I feel that BOL is the one to trust. Especially based on the posts we see here. Even if attach
(without detach) work in 99.99 % of the cases, it isn't good enough for me. Without knowing why it
won't work, I can't trust it. :-)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:ECD839A1-AC24-45BC-94D2-306A82B9397C@.microsoft.com...[vbcol=seagreen]
> Tibor Im curious about your response. You say he "might" be able to attach,
> what circumstances make this possible?
> "Tibor Karaszi" wrote:

database recovery

The SBS 2003 server is blue screening. The client has not done any backup in
several months. I have pluged in another HDD, installed Standard 2003 and
then reconnected the old HDD as a second drive. All the data from the old HD
D
is now visible and accessible. I can now comfortably recover all their data
except SQL database. Is there any way? Please help. Thanks in advance.
ChrisYou might be able to attach the database files to the new installation. Read
about sp_attach_db.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Chris Toffa" <ChrisToffa@.discussions.microsoft.com> wrote in message
news:289C92F0-38BF-40DE-B60D-D464F876DBCC@.microsoft.com...
> The SBS 2003 server is blue screening. The client has not done any backup
in
> several months. I have pluged in another HDD, installed Standard 2003 and
> then reconnected the old HDD as a second drive. All the data from the old
HDD
> is now visible and accessible. I can now comfortably recover all their dat
a
> except SQL database. Is there any way? Please help. Thanks in advance.
> Chris|||Tibor Im curious about your response. You say he "might" be able to attach,
what circumstances make this possible?
"Tibor Karaszi" wrote:

> You might be able to attach the database files to the new installation. Re
ad about sp_attach_db.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Chris Toffa" <ChrisToffa@.discussions.microsoft.com> wrote in message
> news:289C92F0-38BF-40DE-B60D-D464F876DBCC@.microsoft.com...
>|||As long as there was no physical damage to the data or log files it should
work. When it attaches it will go thru recovery and roll forward or back as
needed to make the db consistent.
Andrew J. Kelly SQL MVP
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:ECD839A1-AC24-45BC-94D2-306A82B9397C@.microsoft.com...[vbcol=seagreen]
> Tibor Im curious about your response. You say he "might" be able to
> attach,
> what circumstances make this possible?
> "Tibor Karaszi" wrote:
>|||> Tibor Im curious about your response. You say he "might" be able to attach,">
> what circumstances make this possible?
Below is a quote from Books Online (2000) , sp_attach_db
"sp_attach_db should only be executed on databases that were previously deta
ched from the database
server using an explicit sp_detach_db operation. "
We see posts almost here daily about "... crash ... attach... doesn't work".
Granted, many of these
deleted the log file as well, but still. I like to play safe. Yes, I'd appre
ciate if MS would
provide a technical elaboration about specifically when attach work and when
it doesn't. But without
such, I feel that BOL is the one to trust. Especially based on the posts we
see here. Even if attach
(without detach) work in 99.99 % of the cases, it isn't good enough for me.
Without knowing why it
won't work, I can't trust it. :-)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:ECD839A1-AC24-45BC-94D2-306A82B9397C@.microsoft.com...[vbcol=seagreen]
> Tibor Im curious about your response. You say he "might" be able to attach
,
> what circumstances make this possible?
> "Tibor Karaszi" wrote:
>

database recovery

The SBS 2003 server is blue screening. The client has not done any backup in
several months. I have pluged in another HDD, installed Standard 2003 and
then reconnected the old HDD as a second drive. All the data from the old HDD
is now visible and accessible. I can now comfortably recover all their data
except SQL database. Is there any way? Please help. Thanks in advance.
ChrisYou might be able to attach the database files to the new installation. Read about sp_attach_db.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Chris Toffa" <ChrisToffa@.discussions.microsoft.com> wrote in message
news:289C92F0-38BF-40DE-B60D-D464F876DBCC@.microsoft.com...
> The SBS 2003 server is blue screening. The client has not done any backup in
> several months. I have pluged in another HDD, installed Standard 2003 and
> then reconnected the old HDD as a second drive. All the data from the old HDD
> is now visible and accessible. I can now comfortably recover all their data
> except SQL database. Is there any way? Please help. Thanks in advance.
> Chris|||Tibor Im curious about your response. You say he "might" be able to attach,
what circumstances make this possible?
"Tibor Karaszi" wrote:
> You might be able to attach the database files to the new installation. Read about sp_attach_db.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Chris Toffa" <ChrisToffa@.discussions.microsoft.com> wrote in message
> news:289C92F0-38BF-40DE-B60D-D464F876DBCC@.microsoft.com...
> > The SBS 2003 server is blue screening. The client has not done any backup in
> > several months. I have pluged in another HDD, installed Standard 2003 and
> > then reconnected the old HDD as a second drive. All the data from the old HDD
> > is now visible and accessible. I can now comfortably recover all their data
> > except SQL database. Is there any way? Please help. Thanks in advance.
> >
> > Chris
>|||As long as there was no physical damage to the data or log files it should
work. When it attaches it will go thru recovery and roll forward or back as
needed to make the db consistent.
--
Andrew J. Kelly SQL MVP
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:ECD839A1-AC24-45BC-94D2-306A82B9397C@.microsoft.com...
> Tibor Im curious about your response. You say he "might" be able to
> attach,
> what circumstances make this possible?
> "Tibor Karaszi" wrote:
>> You might be able to attach the database files to the new installation.
>> Read about sp_attach_db.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>> Blog: http://solidqualitylearning.com/blogs/tibor/
>>
>> "Chris Toffa" <ChrisToffa@.discussions.microsoft.com> wrote in message
>> news:289C92F0-38BF-40DE-B60D-D464F876DBCC@.microsoft.com...
>> > The SBS 2003 server is blue screening. The client has not done any
>> > backup in
>> > several months. I have pluged in another HDD, installed Standard 2003
>> > and
>> > then reconnected the old HDD as a second drive. All the data from the
>> > old HDD
>> > is now visible and accessible. I can now comfortably recover all their
>> > data
>> > except SQL database. Is there any way? Please help. Thanks in advance.
>> >
>> > Chris
>>|||> Tibor Im curious about your response. You say he "might" be able to attach,
> what circumstances make this possible?
Below is a quote from Books Online (2000) , sp_attach_db
"sp_attach_db should only be executed on databases that were previously detached from the database
server using an explicit sp_detach_db operation. "
We see posts almost here daily about "... crash ... attach... doesn't work". Granted, many of these
deleted the log file as well, but still. I like to play safe. Yes, I'd appreciate if MS would
provide a technical elaboration about specifically when attach work and when it doesn't. But without
such, I feel that BOL is the one to trust. Especially based on the posts we see here. Even if attach
(without detach) work in 99.99 % of the cases, it isn't good enough for me. Without knowing why it
won't work, I can't trust it. :-)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:ECD839A1-AC24-45BC-94D2-306A82B9397C@.microsoft.com...
> Tibor Im curious about your response. You say he "might" be able to attach,
> what circumstances make this possible?
> "Tibor Karaszi" wrote:
>> You might be able to attach the database files to the new installation. Read about sp_attach_db.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>> Blog: http://solidqualitylearning.com/blogs/tibor/
>>
>> "Chris Toffa" <ChrisToffa@.discussions.microsoft.com> wrote in message
>> news:289C92F0-38BF-40DE-B60D-D464F876DBCC@.microsoft.com...
>> > The SBS 2003 server is blue screening. The client has not done any backup in
>> > several months. I have pluged in another HDD, installed Standard 2003 and
>> > then reconnected the old HDD as a second drive. All the data from the old HDD
>> > is now visible and accessible. I can now comfortably recover all their data
>> > except SQL database. Is there any way? Please help. Thanks in advance.
>> >
>> > Chris
>>

database question

I have forums installed on one database, and a multiuser blog system on
another database. I was wondering if it was possible to synchronize the
databases so that the users' logins and passwords would be the same on
the blogs as on the forums. If so, how would I go about doing that,
without using any programs or spending any money?Search KB for sp_help_revlogins
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
<emosexual@.gmail.com> wrote in message news:1127973055.292397.285460@.g47g2000cwa.googlegrou
ps.com...
>I have forums installed on one database, and a multiuser blog system on
> another database. I was wondering if it was possible to synchronize the
> databases so that the users' logins and passwords would be the same on
> the blogs as on the forums. If so, how would I go about doing that,
> without using any programs or spending any money?
>

Database problem

Hi,

I have MS SQL Server 2005 installed on the computer. I would like to connect to a database in the MS SQL Server from the RS SQL Server I also have got. I have got an instcurtion how to do this but they use MS SQL Server 7.0 which is the problem. When they open MS SQL Server Enterprise Manager they can open up a directory structure and find Databases/Tables which could be find on the computer. Now I wounder how I′ll do the same thing in MS SQL Server 2005?

When I start MS SQL 2005 I can′t find any structure, to find tha database and the tables I want to connect to. I have also got an database in a *.txt-file and I wounder where I should place this file on my hard drive.

Please help me.

Best Regards

Anna

I didn′t get you correctly, could you explain this again please.

HTH, jens SUessmeyer.

http://www.sqlserver2005.de|||"MS SQL server Enterprise Manager" has been renamed to "Microsoft SQL Server Managment Studio" in sql server 2005.

When you open manament studio you will get an "connect to " dialog box. Chose "database engine" and enter you credentials. If in doubt use Server name: (local) and Authentication "Windows Authentication"

On your left hand side you should have "object explorer" in this you should be able to expand a tree like strucutre that is similar to enterprise manager's tree view. If you don't see the object explorer, try pressing F8.

The database you have as a text file is most likely a dump of a table, you can either bulk import using f.eks "bulk insert" or make a import routine using SSIS.|||Just for the common sense, SSMS not just has been renamed, it has been, like other features of SQL Server build from scratch. SSMS relies on SMO as SQL Server EM relies on SQL-DMO. Just for the common understanding of the original poster :-)

HTH, jens Suessmeyer.

http://www.sqlserver2005.de