Showing posts with label iam. Show all posts
Showing posts with label iam. Show all posts

Wednesday, March 28, 2012

How to transfered the data?

Hai,
this ankan here by this side ,
IAm facing a problem itis that i want to export & import data from sql server 2000 . to & from microsoft Excel . and the data should be in the understanding fromat in which it was exprot or import to sql server 2000.
Reply me asap
With best regards
ANKAN
REPLY ME ASAP

Quote:

Originally Posted by daffurankan

Hai,
this ankan here by this side ,
IAm facing a problem itis that i want to export & import data from sql server 2000 . to & from microsoft Excel . and the data should be in the understanding fromat in which it was exprot or import to sql server 2000.
Reply me asap
With best regards
ANKAN
REPLY ME ASAP


Hey let use "Data Transformation Service Wizard for import/export datas"

Sunday, February 19, 2012

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