how to supress instance name while logging to sql server 2005?

Hi,
I am using SQL server 2005 express edition on win XP installed on my machine
.
when I use the SQL server Management studio, I have to enter
machinename\SQLExpress .How can I connect using just machinenname and omit
the SQLExpress instancename?what settings do i need to do?
Thanks for your help.
regards,
tech@.77SQLExpress is the default instance name that is given to that edition when
you indtsll it. You could have changed it during the installation. You can
now only uninstall SQL Express and reintall it as the default instance.
But I would suggest you not to do that and leave it as it is, so that when
you are going for developer edition or any other edition at a later stage,
you might want it to run under default instance.
Hope this helps.

How to stop transaction logging in SQL Server 7

I have a lengthy atomic action in a SQL script that
generates a huge transaction log volume. How can I
essentially stop the transaction logging for SQL Server
7? I know I can use ALTER DATABASE for SQL Server 2000
to change the recovery model to Simple, but SQL Server 7
doesn't have these recovery models. The script action
happens in one call to ALTER TABLE which operates on a
huge table, so I can't break it apart and truncate on
checkpoints inside the action. Any suggestions?
Thanks!The SIMPLE recovery model in SQL 2000 is essentially the same as 'select
into/bulk copy' and 'trunc. log on chkpt.' in SQL 7. In both cases,
committed data are removed from the log when a checkpoint occurs.
Transaction logging is required in order to ensure logical and physical
integrity. You may find it significantly faster to recreate the table with
a minimally logged SELECT ... INTO instead of a fully-logged ALTER TABLE.
Hope this helps.
Dan Guzman
SQL Server MVP
"Paul Clapis" <pclapis@.earthlinkdotnet> wrote in message
news:2bf101c3e13f$ac14f630$a501280a@.phx.gbl...

quote:

---

> I have a lengthy atomic action in a SQL script that
> generates a huge transaction log volume. How can I
> essentially stop the transaction logging for SQL Server
> 7? I know I can use ALTER DATABASE for SQL Server 2000
> to change the recovery model to Simple, but SQL Server 7
> doesn't have these recovery models. The script action
> happens in one call to ALTER TABLE which operates on a
> huge table, so I can't break it apart and truncate on
> checkpoints inside the action. Any suggestions?
> Thanks!

---

How to stop transaction logging in SQL Server 7

I have a lengthy atomic action in a SQL script that
generates a huge transaction log volume. How can I
essentially stop the transaction logging for SQL Server
7? I know I can use ALTER DATABASE for SQL Server 2000
to change the recovery model to Simple, but SQL Server 7
doesn't have these recovery models. The script action
happens in one call to ALTER TABLE which operates on a
huge table, so I can't break it apart and truncate on
checkpoints inside the action. Any suggestions?
Thanks!The SIMPLE recovery model in SQL 2000 is essentially the same as 'select
into/bulk copy' and 'trunc. log on chkpt.' in SQL 7. In both cases,
committed data are removed from the log when a checkpoint occurs.
Transaction logging is required in order to ensure logical and physical
integrity. You may find it significantly faster to recreate the table with
a minimally logged SELECT ... INTO instead of a fully-logged ALTER TABLE.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Paul Clapis" <pclapis@.earthlinkdotnet> wrote in message
news:2bf101c3e13f$ac14f630$a501280a@.phx.gbl...
> I have a lengthy atomic action in a SQL script that
> generates a huge transaction log volume. How can I
> essentially stop the transaction logging for SQL Server
> 7? I know I can use ALTER DATABASE for SQL Server 2000
> to change the recovery model to Simple, but SQL Server 7
> doesn't have these recovery models. The script action
> happens in one call to ALTER TABLE which operates on a
> huge table, so I can't break it apart and truncate on
> checkpoints inside the action. Any suggestions?
> Thanks!

How to Stop Logging?

I was about to ask the same question. But I don't think there is a way. I
am creating a new db setting the option to simple and loading massive data
but transaction logging is still happening.
Hopefully someone has a suggestion for us.
stoney
"Raj" wrote:

> is it possible to stop logging in sql server?
> if it is how we can do that?
> Regards!
> Rajstoney wrote:[vbcol=seagreen]
> I was about to ask the same question. But I don't think there is a way.
I
> am creating a new db setting the option to simple and loading massive data
> but transaction logging is still happening.
> Hopefully someone has a suggestion for us.
> stoney
> "Raj" wrote:
>
You CANNOT, repeat CANNOT bypass the transaction log. If you don't
understand why, I suggest you read up on how the transaction log is used.
To prevent the log from growing excessively during an import, break the
import into batches. Import new records in groups of 1000, 5000, 10000,
whatever works best for you. The point is the keep the transactions as
small as possible (each import "batch" is a transaction). If you're
importing a million new records, you are creating a single transaction
of one million inserts - the transaction log must grow large enough to
hold that entire transaction.|||Hi
You can not turn off transaction log logging in SQL Server. Logging is an
intrinsic part of the data modification process.
http://msdn.microsoft.com/library/d... />
t_4l83.asp
Regards
--
Mike
This posting is provided "AS IS" with no warranties, and confers no rights.
"stoney" <stoney@.discussions.microsoft.com> wrote in message
news:1986C6DB-F764-4023-BEEF-68C354B10085@.microsoft.com...[vbcol=seagreen]
>I was about to ask the same question. But I don't think there is a way. I
> am creating a new db setting the option to simple and loading massive data
> but transaction logging is still happening.
> Hopefully someone has a suggestion for us.
> stoney
> "Raj" wrote:
>|||What's version of SQL Server are you using?
You cannot prevent from loging if the person has a login in SQL Server ,
however you can DENY VIEW DEFINITION, VIEW ANY DATABASE (SQL Server 2005)
In SQL Server 2000 you can deny access to the specific database/s
"Raj" <Raj@.discussions.microsoft.com> wrote in message
news:BC4D1CB5-F603-4B12-BFBF-E3AE939C8048@.microsoft.com...
> is it possible to stop logging in sql server?
> if it is how we can do that?
> Regards!
> Raj|||is it possible to stop logging in sql server?
if it is how we can do that?
Regards!
Raj|||I was about to ask the same question. But I don't think there is a way. I
am creating a new db setting the option to simple and loading massive data
but transaction logging is still happening.
Hopefully someone has a suggestion for us.
stoney
"Raj" wrote:

> is it possible to stop logging in sql server?
> if it is how we can do that?
> Regards!
> Raj|||stoney wrote:[vbcol=seagreen]
> I was about to ask the same question. But I don't think there is a way.
I
> am creating a new db setting the option to simple and loading massive data
> but transaction logging is still happening.
> Hopefully someone has a suggestion for us.
> stoney
> "Raj" wrote:
>
You CANNOT, repeat CANNOT bypass the transaction log. If you don't
understand why, I suggest you read up on how the transaction log is used.
To prevent the log from growing excessively during an import, break the
import into batches. Import new records in groups of 1000, 5000, 10000,
whatever works best for you. The point is the keep the transactions as
small as possible (each import "batch" is a transaction). If you're
importing a million new records, you are creating a single transaction
of one million inserts - the transaction log must grow large enough to
hold that entire transaction.|||Hi
You can not turn off transaction log logging in SQL Server. Logging is an
intrinsic part of the data modification process.
http://msdn.microsoft.com/library/d... />
t_4l83.asp
Regards
--
Mike
This posting is provided "AS IS" with no warranties, and confers no rights.
"stoney" <stoney@.discussions.microsoft.com> wrote in message
news:1986C6DB-F764-4023-BEEF-68C354B10085@.microsoft.com...[vbcol=seagreen]
>I was about to ask the same question. But I don't think there is a way. I
> am creating a new db setting the option to simple and loading massive data
> but transaction logging is still happening.
> Hopefully someone has a suggestion for us.
> stoney
> "Raj" wrote:
>|||What's version of SQL Server are you using?
You cannot prevent from loging if the person has a login in SQL Server ,
however you can DENY VIEW DEFINITION, VIEW ANY DATABASE (SQL Server 2005)
In SQL Server 2000 you can deny access to the specific database/s
"Raj" <Raj@.discussions.microsoft.com> wrote in message
news:BC4D1CB5-F603-4B12-BFBF-E3AE939C8048@.microsoft.com...
> is it possible to stop logging in sql server?
> if it is how we can do that?
> Regards!
> Raj

How to Stop Logging?

is it possible to stop logging in sql server?
if it is how we can do that?
Regards!
RajI was about to ask the same question. But I don't think there is a way. I
am creating a new db setting the option to simple and loading massive data
but transaction logging is still happening.
Hopefully someone has a suggestion for us.
stoney
"Raj" wrote:
> is it possible to stop logging in sql server?
> if it is how we can do that?
> Regards!
> Raj|||stoney wrote:
> I was about to ask the same question. But I don't think there is a way. I
> am creating a new db setting the option to simple and loading massive data
> but transaction logging is still happening.
> Hopefully someone has a suggestion for us.
> stoney
> "Raj" wrote:
>> is it possible to stop logging in sql server?
>> if it is how we can do that?
>> Regards!
>> Raj
You CANNOT, repeat CANNOT bypass the transaction log. If you don't
understand why, I suggest you read up on how the transaction log is used.
To prevent the log from growing excessively during an import, break the
import into batches. Import new records in groups of 1000, 5000, 10000,
whatever works best for you. The point is the keep the transactions as
small as possible (each import "batch" is a transaction). If you're
importing a million new records, you are creating a single transaction
of one million inserts - the transaction log must grow large enough to
hold that entire transaction.|||Hi
You can not turn off transaction log logging in SQL Server. Logging is an
intrinsic part of the data modification process.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_bkprst_4l83.asp
Regards
--
Mike
This posting is provided "AS IS" with no warranties, and confers no rights.
"stoney" <stoney@.discussions.microsoft.com> wrote in message
news:1986C6DB-F764-4023-BEEF-68C354B10085@.microsoft.com...
>I was about to ask the same question. But I don't think there is a way. I
> am creating a new db setting the option to simple and loading massive data
> but transaction logging is still happening.
> Hopefully someone has a suggestion for us.
> stoney
> "Raj" wrote:
>> is it possible to stop logging in sql server?
>> if it is how we can do that?
>> Regards!
>> Raj|||What's version of SQL Server are you using?
You cannot prevent from loging if the person has a login in SQL Server ,
however you can DENY VIEW DEFINITION, VIEW ANY DATABASE (SQL Server 2005)
In SQL Server 2000 you can deny access to the specific database/s
"Raj" <Raj@.discussions.microsoft.com> wrote in message
news:BC4D1CB5-F603-4B12-BFBF-E3AE939C8048@.microsoft.com...
> is it possible to stop logging in sql server?
> if it is how we can do that?
> Regards!
> Raj

How to Stop Logging

Hi,

I am doing some resource hungry tasks (some extraction and loading
through DTS), for which each time the SQL Server Log files gets filled
up!

Is there any way to stop the logging (like as during restore)?

Thanks in advance.

-surajits_laha@.rediffmail.com (Surajit Laha) wrote in message news:<ba8ee108.0401290212.6defeb00@.posting.google.com>...
> Hi,
> I am doing some resource hungry tasks (some extraction and loading
> through DTS), for which each time the SQL Server Log files gets filled
> up!
> Is there any way to stop the logging (like as during restore)?
> Thanks in advance.
> -surajit

You can't disable logging, but you could set the database recovery
model to simple during the load. You might also be able to load in
batches, instead of in a single transaction, which should require less
log space. The DTS Transform Data Task allows you to specify a batch
size, for example.

Simon