Viewing 15 posts - 481 through 495 (of 499 total)
Chris,
I don;t know of another way to do this within SSIS, but there are several scripts available that will generate a CREATE TABLE statement for you on SQL Server -...
July 10, 2008 at 8:04 am
Parameters are a bit of a minefield in my experience.
How you specify them depends on the connection type
e.g. OLE DB connection requires the symbol '?' and parameter names should...
July 10, 2008 at 7:42 am
You probably need a "Transfer SQL Server Objects" Task
you need to specify an SMO connection,
There are a whole load of options
including the drop and re-create objects, and CopySchema.
Its was...
July 10, 2008 at 7:36 am
🙂 At last! the answer to Transfer Server Objects
Set CopySchema to True!
Many thanks I've been looking for this for a while.
July 4, 2008 at 4:11 am
OK So I have a copy of the database in question on my laptop, and developer edition, so I tried first DBCC UPDATEUSAGE - this told me it had fixed...
July 3, 2008 at 4:30 pm
Mani Singh (7/3/2008)
Always after and upgrade run the following statements.
DBCC UPDATEUSAGE (aspnetdb) and DBCC CHECKDB(dbname). This makes sure nothing went/is wrong in...
July 3, 2008 at 1:07 pm
Thanks. Good video I found it useful. Keep burning the midnight oil 🙂
July 3, 2008 at 2:10 am
If you want to improve performance by adding indexes and keys to the tables - then a good start would be chapter 3 of "Inside Microsoft SQL Server 2005: T-SQL...
July 2, 2008 at 5:16 am
It may be possible to write INSERT/UPDATE/DELETE triggers in the source database tables to update the equivalent destination database tables
However, I'd guess it could put a strain on resources...
July 2, 2008 at 3:53 am
Thanks for your suggestions. Our DBA would not turn off logging, but did change it to 'simple' - but it didn't make much difference.
Symptoms are: First 1000 items...
July 1, 2008 at 4:40 am
Thanks,
I've decided to put USE TEMPDB at the top of my script files - followed by a RAISEERROR as a harm reduction strategy in case of accidental execution
June 26, 2008 at 8:21 am
Those of us used to procedural languages like cursors in SQL - at least to start with. They are easy to understand, when the set-based solution isn't always obvious. Cursors...
June 29, 2007 at 6:31 am
Hi Paul,
Heres a bunch of suggestions: Use Select/print statements inside the cursor to see whats going on
e.g. -- see if the count is non-zero
SELECT COUNT(*) FROM FollowUpTbl WHERE ...
If the...
June 29, 2007 at 3:16 am
When using .NET 2003, I used to step up to the SQL call, then transfer to Query analyser to initiate debugging, setting up the stored procedure parameters manually - its...
June 8, 2007 at 2:13 am
First Ninja's point: I'm porting a "shadow IT" application written in Access and VB6 - Its a production line sequencing program to keep a balanced workload on the assembly track. ...
June 6, 2007 at 7:29 am
Viewing 15 posts - 481 through 495 (of 499 total)