microsoft.public.sqlserver.programming Google Group

Re: creating table on secondery filegroup

2009-11-08T18:22:08Z

SELECT...INTO creates the table on the default filegroup. You'll need to
mark the secondary filegroup as the default one beforehand:
ALTER DATABASE MyDatabase
MODIFY FILEGROUP [MySecondaryGroup] DEFAULT;

Re: Sql Server on VMWare

2009-11-08T18:15:27Z

[link]
[link]

Re: Transaction load

2009-11-08T17:06:46Z

Thanks. I am aware of this but was just speculating that "SqlBulkCopy" is
probably a wrapper for BULK INSERT or some other high-volume (native) SQL
Server statement (possibly internal to MSFT only). My original issue however
is whether running "SqlBulkCopy" (or BULK INSERT directly) will have an

creating table on secondery filegroup

2009-11-08T16:54:32Z

hello there
i have database with two filegroups and for each filegroup there is diffrent
file name
How can I use Select .. into and create new table on secondery filegroup?

Re: Transaction load

2009-11-08T15:12:29Z

BULK INSERT is a Transact-SQL statement whereas the SqlBulkCopy class (and
its unmanaged ODBC/OLEDB cousins) are native client APIs. Unlike BULK
INSERT, the client APIs allow you to load directly from program variables.

Re: Transaction load

2009-11-08T12:48:17Z

Thanks. Can you also briefly elaborate on my last response to him (just
posted). Appreciate your help.
Not familir with this but probably not necessary for my needs unless it
solves some problem specificically related to this issue (resource
exhaustion). The bulk insert I tested ("SqlBulkCopy" in .NET) is very fast

Re: Transaction load

2009-11-08T12:34:21Z

Thanks for you help and I agree. It's hard to appreciate when you're not
really familiar with the details. In this case however it's a fairly simple
situation. Assuming 10,000 customers in the short-term, 100,000 long term,
and each customer will be uploading a single file just once every few weeks

Re: Transaction load

2009-11-08T12:09:16Z

Thanks. I'm actually using the "SqlBulkCopy" class (assuming you're familiar
with .NET) and this presumably wraps BULK INSERT (still researching things).
I also took a quick look at ROWS_PER_BATCH and this may prove useful (thanks
for pointing this out). If possible however, I'd like to insert all data in

Re: Transaction load

2009-11-08T10:52:53Z

Hi
As Andrew said to separate LOG and DATA files must be e first step
Have you considered using SSIS Package to insert the data from the files ,
it hs very nice feature named 'fast load'

Re: Join query returns to many rows

2009-11-08T08:55:30Z

Precisely why you should never code using the original ansi 89 style and use
infix instead...
Never code like this...
FROM {tbl} as a, {tbl} as b
WHERE a.tblkey = b.tblkey
AND a.postertype = 'opinionated'
AND a.postername = '--celko--'
Instead you should write like the majority of other folk do....

Re: Running value but with a string

2009-11-08T08:51:59Z

Wrong - the standards a small subset of the product language available
within MICROSOFT SQL SERVER.
Wrong again - we've already been through this one; there are very few items
of syntax that have been deprecated - legacy code written on SQL Server 6.5
still works on SQL Server 2008 - that allows business to migrate versions of

Sql Server on VMWare

2009-11-08T07:23:59Z

Hi,
Can anybody give me some right direction or usefull link
1. About VMware environment
2. How to Install and configure Sql Server 2005 on VMware.
3. Is there any performance change on VMware.
Regards
Rahul

Re: SSIS hitting FK violation - need to ignore the error rows - have package succeed

2009-11-08T01:32:05Z

oh thanks, i'll consider this also. both pieces of info where very
helpful!

Re: Running value but with a string

2009-11-08T00:29:37Z

You narrow your solutions by writing in dialect; you increase their
scope, maintainability and robustness by sticking to Standards.
Having something that runs in only one release of one version of one
SQL is not a good thing.
But strong dialect code gives you job security. Even better, write
your code in an unsupported version that only you know.

Re: Join query returns to many rows

2009-11-08T00:10:56Z

There are two forms of the SELECT [ALL | DISTINCT]; the SELECT ALL
keeps duplicate rows and the SELECT DISTINCT removes redundant
duplicate rows, leaving one copy. SELECT by itself is a shorthand for
SELECT ALL. You will find these keywords used in other parts of SQL
for this sort of thing.
As a generalization, a SELECT DISTINCT is a symptom of a bad query