Changing to Simple may not make any difference for index maintenance. To rebuild an index, you need log space approximately equal to the size of that index. It...

I would recommend you don't install client or management tools on a server at all. Run them remotely. Stuff like that on a server uses up processor cycles...

Well, if Powershell doesn't work for you, you could consider SQLCMD (either like this or like this), or SSIS.

John

INSERT INTO MyTable (<column list>)

SELECT <column list>

FROM MyView

WHERE <whatever>

It's probably easier to write it manually than to attempt to script it. If the column list is long then you...

Open the packages in the version of BIDS that ships with SQL Server 2008. The packages will be automatically converted. Beware, though - once converted, they may not...

Where are you finding the Task option? And are you sure you want to create INSERT scripts for a view and not a table? I'm not saying you...

Does the program run on the same computer as SSMS and Visual Studio? Do you have an alias set up in SSMS that your program would not be able...

Isn't "Query from variable" or something like that one of the options? If you choose that, you can build the value of the variable with an expression and set...

Well, it's your problem; you tell us what you don't understand.

I think you will need a script task to determine which one...

Yes, you do need to check SSIS is installed on both nodes. As you'll have read, it's not cluster aware.

As long as you save an old copy of the...

Dwain

I think the danger with that is you end up with something like a catch-all query and you risk having a less than optimal execution plan cached. That's why...

I think what's happening is that the WHERE clause on the dates is turning your outer join into an inner join. It's difficult to visualise with no sample data,...

Jared

I know you've posted in the SQL Server 2005 forum, but if you have access to SQL Server 2008 and above, it's worth considering Filestream. There's a very thorough...

No. You'd have to export the whole result set and then remove the columns you don't want. If it's something you do regularly then it's worth considering writing...

SELECT

contact_id

,FtgNr

FROM

#testEnvironment

WHERE

FtgNr NOT LIKE '[A-Z][A-Z]%1'

John