Viewing 15 posts - 556 through 570 (of 1,413 total)
Could you post the DDL of your table and the procedure you are executing?
July 8, 2005 at 3:22 am
How do you mean the row gets deleted? An UPDATE can never delete a row entirely. Sometimes an update is split into a delete/insert pair of operations, but that is...
July 8, 2005 at 3:00 am
No idea what caused this, but I would do a memory check and possibly look at other hardware items.
July 7, 2005 at 5:05 am
But that is exactly what the view solves.
You have this now: SELECT * FROM BIGTABLE
Now you create SMALLTABLE1 and SMALLTABLE2, move all the rows there and then drop BIGTABLE. Finally...
July 7, 2005 at 4:42 am
Yes, SQL Server Management Studio has integrated support for source control. In fact it also has projects and solutions where you tie scripts, then source control the entire solution. Just...
July 7, 2005 at 2:45 am
There is no alternative, at least not until SQL Server 2005. But why will this cause code changes? The beauty of it is that SQL Server automatically handles reads and...
July 7, 2005 at 2:42 am
No, you need to have a trace running and look it up there to see it. You can use Profiler for this.
July 7, 2005 at 2:39 am
If you are specifying internal physical properties for retrieving rows you are not really querying the database, you are telling it what to do. In fact, I would even say...
July 7, 2005 at 1:52 am
You can separate the BIG_TABLE into SMALL_TABLE1, SMALL_TABLE2 etc. Then create a view called BIG_TABLE that does the UNION ALL of the smaller tables. Your application won't notice any difference.
July 6, 2005 at 11:50 pm
Take a look at Professional SQL Server 2000 DTS
And it is co-authored by SQL Server Central co-founder, Brian Knight.
July 6, 2005 at 2:48 pm
The procedures cannot be owned by his login. Procedures are owned by users. His login might however be mapped to a specific user which owns the procedures. That user might...
July 6, 2005 at 2:43 pm
You should do this on the client side as this is a presentation issue.
July 6, 2005 at 12:17 am
Both the Jet version and the proprietary SQL Server syntax is pretty ugly in my view.
July 5, 2005 at 3:54 pm
Do you have multiple files in the filegroup where the table/index is stored? If so then the output value from DBCC SHOWCONTIG for external fragmentation should not be paid too...
July 5, 2005 at 3:47 pm
You should never delete them directly from the system tables. You can however create a script that collects the info from INFORMATION_SCHEMA-views (or system tables) and then dynamically removes them...
July 5, 2005 at 7:57 am
Viewing 15 posts - 556 through 570 (of 1,413 total)