2GB Limitation question

Is the 2 GB limitation the combination of the .MDF and .LDF or only the
..MDF?
If both, can you turn off the LOG file?
Thanks,
Jack T.
I believe it doesn't include the log file
Michael Culley
"Jack T." <71045.3122_No_Spam_Here@.compuserve.com> wrote in message
news:efwFmaQmEHA.2340@.TK2MSFTNGP11.phx.gbl...
> Is the 2 GB limitation the combination of the .MDF and .LDF or only the
> .MDF?
> If both, can you turn off the LOG file?
> Thanks,
> Jack T.
>
|||see
http://msdn.microsoft.com/library/de...ar_ts_8dbn.asp
3 The data portion of a database cannot exceed 2 GB in size when using the
SQL Server 2000 Desktop Engine (MSDE 2000) or the Microsoft Data Engine
(MSDE) 1.0. The total size of the database, including log files, can exceed 2
GB provided the sum of the sizes of the data files remains 2 GB or lower.
"Jack T." wrote:

> Is the 2 GB limitation the combination of the .MDF and .LDF or only the
> ..MDF?
> If both, can you turn off the LOG file?
> Thanks,
> Jack T.
>
>
|||Awesome! As long as the MDF's per instances don't exceed the 2GB limit. I
can live with that.
Thanks,
Jack T.
|||Does MSDE support SHRINK in the same way that SQL Server 2000 does?
If so you might want to shrink the database and reclaim any unsed space each
night
Rich
"Jack T." wrote:

> Awesome! As long as the MDF's per instances don't exceed the 2GB limit. I
> can live with that.
> Thanks,
> Jack T.
>
>
|||Yes, but why would that be necessary? SQL Server will re-use the deallocated
space within the database automatically so there's no need to play with the
file size. Shrinking and expanding are expensive in terms of performance.
Sincerely,
Stephen Dybing
This posting is provided "AS IS" with no warranties, and confers no rights.
"Richard Yeo" <RichardYeo@.discussions.microsoft.com> wrote in message
news:6DABD8E8-06E3-4035-A8C1-3AC71AF48453@.microsoft.com...[vbcol=seagreen]
> Does MSDE support SHRINK in the same way that SQL Server 2000 does?
> If so you might want to shrink the database and reclaim any unsed space
> each
> night
> Rich
>
> "Jack T." wrote:
|||Stephen
If SQL Server automatically reuses ALL space from deleted records whats the
point of the SHRINK command?
Rich
"Stephen Dybing [MSFT]" wrote:

> Yes, but why would that be necessary? SQL Server will re-use the deallocated
> space within the database automatically so there's no need to play with the
> file size. Shrinking and expanding are expensive in terms of performance.
> --
> Sincerely,
> Stephen Dybing
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "Richard Yeo" <RichardYeo@.discussions.microsoft.com> wrote in message
> news:6DABD8E8-06E3-4035-A8C1-3AC71AF48453@.microsoft.com...
>
>
|||hi Richard,
"Richard Yeo" <RichardYeo@.discussions.microsoft.com> ha scritto nel
messaggio news:F1BD0469-6F9C-40A5-956F-D568B9200B3E@.microsoft.com...
> Stephen
> If SQL Server automatically reuses ALL space from deleted records whats
the
> point of the SHRINK command?
to reduce it's size once a lot of delete operations have drastically reduced
the used data pages... so that unused pages will be release to the
underlying OS...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||So SHRINK is important ;)
Sorry just pulling Stephens leg I knew this all along.
MSDE is often used as a log and therefore lots of deletes will be used when
the old log information is no longer required. Therefore shrink is important.
Don't forget to backup your transaction logs regularly to prevent them
growing continuously.
You should also consider running an integrity check regularly.
Rich
"Jack T." wrote:

> Is the 2 GB limitation the combination of the .MDF and .LDF or only the
> ..MDF?
> If both, can you turn off the LOG file?
> Thanks,
> Jack T.
>
>
|||Uh no, the log file size does not factor into that 2GB database limitation.
When the rows are deleted from your table, they are gone and new rows can
use that space. SHRINK is still not necessary for this situation and if
performance is an issue, please remember that shrinking and growing the file
is expensive. It's possible that SHRINK is necessary in some situations for
some people, but I think it's highly overrated.
Sincerely,
Stephen Dybing
This posting is provided "AS IS" with no warranties, and confers no rights.
"Richard Yeo" <RichardYeo@.discussions.microsoft.com> wrote in message
news:55CC05A1-238C-4FB3-A117-466C3A6F0570@.microsoft.com...[vbcol=seagreen]
> So SHRINK is important ;)
> Sorry just pulling Stephens leg I knew this all along.
> MSDE is often used as a log and therefore lots of deletes will be used
> when
> the old log information is no longer required. Therefore shrink is
> important.
> Don't forget to backup your transaction logs regularly to prevent them
> growing continuously.
> You should also consider running an integrity check regularly.
> Rich
> "Jack T." wrote:

2005 install ques re owner of database?

Hello -
I just installed Sql Server 2005 on a company server. I copied and attached
database mdf and ldf files. The database runs okay with my application on
my developer machine. I just started setting up security on the server and
it is indicating the owner of the database is "MyOrganization"\MyName. My
login name (user name) on the network is MyName. I tried to change to chang
e
the Owner of the database under Files and I'm getting the message:
...The login 'MyName' does not exist on this server.
How can I fix this?
Any help will be greatly appreciated!
--
SandyHow do you connect to the company server? If you connect via SQL login, then
execute the below should do it (assuming the sql login is part of sysadmin).
exec <the_database_name>..sp_changedbowner 'the_sql_login'
If you're login as a NT user/acct and is part of the administrators group,
your NT user name is implicitly granted permission. If you really want to
use your NT user name/acct as the db_owner, you will have to explicitly add
your NT acct to sql sysadmin role.
e.g.
create login [domain\nt_acct] from windows;
exec sp_addsrvrolemember 'domain\nt_acct', 'sysadmin'
then you can change dbowner
exec <the_database_name>..sp_changedbowner 'domain\nt_acct'
-oj
"Sandy" <Sandy@.discussions.microsoft.com> wrote in message
news:CCFAE0DB-7208-4189-B9B4-F5A3B1EDCD0B@.microsoft.com...
> Hello -
> I just installed Sql Server 2005 on a company server. I copied and
> attached
> database mdf and ldf files. The database runs okay with my application on
> my developer machine. I just started setting up security on the server
> and
> it is indicating the owner of the database is "MyOrganization"\MyName. My
> login name (user name) on the network is MyName. I tried to change to
> change
> the Owner of the database under Files and I'm getting the message:
> ...The login 'MyName' does not exist on this server.
> How can I fix this?
> Any help will be greatly appreciated!
> --
> Sandy

2005 install ques re owner of database?

Hello -
I just installed Sql Server 2005 on a company server. I copied and attached
database mdf and ldf files. The database runs okay with my application on
my developer machine. I just started setting up security on the server and
it is indicating the owner of the database is "MyOrganization"\MyName. My
login name (user name) on the network is MyName. I tried to change to change
the Owner of the database under Files and I'm getting the message:
...The login 'MyName' does not exist on this server.
How can I fix this?
Any help will be greatly appreciated!
--
SandyHow do you connect to the company server? If you connect via SQL login, then
execute the below should do it (assuming the sql login is part of sysadmin).
exec <the_database_name>..sp_changedbowner 'the_sql_login'
If you're login as a NT user/acct and is part of the administrators group,
your NT user name is implicitly granted permission. If you really want to
use your NT user name/acct as the db_owner, you will have to explicitly add
your NT acct to sql sysadmin role.
e.g.
create login [domain\nt_acct] from windows;
exec sp_addsrvrolemember 'domain\nt_acct', 'sysadmin'
then you can change dbowner
exec <the_database_name>..sp_changedbowner 'domain\nt_acct'
-oj
"Sandy" <Sandy@.discussions.microsoft.com> wrote in message
news:CCFAE0DB-7208-4189-B9B4-F5A3B1EDCD0B@.microsoft.com...
> Hello -
> I just installed Sql Server 2005 on a company server. I copied and
> attached
> database mdf and ldf files. The database runs okay with my application on
> my developer machine. I just started setting up security on the server
> and
> it is indicating the owner of the database is "MyOrganization"\MyName. My
> login name (user name) on the network is MyName. I tried to change to
> change
> the Owner of the database under Files and I'm getting the message:
> ...The login 'MyName' does not exist on this server.
> How can I fix this?
> Any help will be greatly appreciated!
> --
> Sandy