Viewing 15 posts - 5,596 through 5,610 (of 6,216 total)
Tables are all contained in the .mdf file. You'll need to either export it to a different db so you can zip THAT .mdf, or export the data to a...
October 24, 2001 at 6:16 am
Wow. I am SO against XML in blobs! Until the tools progress some, it's just a royal pain to work with (Leon - come on, lets argue!).
How are you accessing...
October 24, 2001 at 5:33 am
Truncate is excellent if you want to remove ALL the data. One thing to remember - if you're using an identity column it will reset the seed!
Andy
October 23, 2001 at 5:42 pm
Jody - not bad, staging tables are always handy, although depending on your data source I'd be concerned about the dropping the constraint part. I understand why you do it,...
October 23, 2001 at 4:35 pm
Ana - have you tried running the same query in Query Analyzer, taken a look at the query plan?
Andy
October 23, 2001 at 4:31 pm
You could do it with an insert trigger. You could either rollback any transaction that would cause the row limit to exceeded, or you could delete the oldest/inactive records to...
October 23, 2001 at 4:25 pm
Is backing them up taking a lot of time? I avoid filegroups (just a personal preference) but if you can afford to back them up, why not? Another option would...
October 23, 2001 at 11:35 am
Basically - according to Inside SQL Server 2000, each data row has some version info as well (if you have it, try page 252). The amount of space this info...
October 23, 2001 at 11:33 am
Here is a starting point for you. See what you can do with this:
On Error Resume Next
Set oServer = New SQLDMO.SQLServer
With oServer
.LoginSecure = True
...
October 23, 2001 at 5:55 am
Did they give you a Q article on it? The problem only happens when you shrink - why would you need to? They don't have any kind of hotfix available?
Andy
...
October 23, 2001 at 5:47 am
One thing handy to have is a list of your SQL logins and the associated passwords. There's a puzzle for you!
Andy
October 23, 2001 at 5:45 am
Ran the following:
create table testtablesize (col1 varchar(8000), col2 varchar(60))
Generated this:
Warning: The table 'testtablesize' has been created but its maximum row size (8085) exceeds the maximum number of bytes per row...
October 23, 2001 at 4:35 am
I have not seen this. What version of SQL? What service pack? Setting auto shrink to off is a good idea anyway.
Andy
October 22, 2001 at 7:09 pm
Yes, I'd expect performance to be the same or better. It is SO worth upgrading. Just be done with junk like devices is worth the move.
Andy
October 22, 2001 at 4:27 pm
Viewing 15 posts - 5,596 through 5,610 (of 6,216 total)