Viewing 15 posts - 39,121 through 39,135 (of 49,571 total)
Vicki Peters (5/14/2009)
Awesome, that worked. Thank you!
Yup, but note that it does what Lowell and I already suggested. Create a new table, copy all the data over, recreate the constraints,...
May 14, 2009 at 10:31 am
Vicki Peters (5/14/2009)
I'd like to insert it in a place that makes sense.
Why? Order of columns in a table is quite irrelivent. All it affects is what you see in...
May 14, 2009 at 8:05 am
Looks like you may have some irreparable corruption there. Can you please run the following so that I can see exactly what errors remain. Please post the full results.
DBCC CHECKDB(<Database...
May 14, 2009 at 7:08 am
Well, on versions before 2008 there really weren't many options. Triggers, properly implemented, do auditing quite well.
May 14, 2009 at 6:52 am
There's no way to have separate diff 'streams' Even if you could use COPY_ONLY, it just means that the backup that you've taken doesn't reset the diff base. Any diffs...
May 14, 2009 at 6:07 am
Take a look at the sys.dm_exec_sessions and the sys.dm_exec_connections DMVs. You can use @@Spid to get the spid of the session to filter those DMVs.
Doing auditing in triggers?
May 14, 2009 at 5:13 am
SeanF (5/14/2009)
select count(column name) from tablewill return the number of non null columns
More correctly it will return the number of rows in the table where the column specified is not...
May 14, 2009 at 4:56 am
New database?
Existing database?
30 million concurrent users? If not, what's the estimate for concurrent users?
Expected database size?
May 14, 2009 at 4:55 am
No practical difference. They both count the number of rows in the resultset.
May 14, 2009 at 3:47 am
What do you mean by "redo a new database"? Restore from backup?
May 14, 2009 at 3:27 am
Those aren't errors. They're part of the normal restart-recovery of databases that SQL will do if the databases were not cleanly shut down when the SQL service terminated.
May 14, 2009 at 3:21 am
Please post table definitions, sample data and desired output. Read this to see the best way to post this to get quick responses.
http://www.sqlservercentral.com/articles/Best+Practices/61537/
May 13, 2009 at 11:07 pm
A strong password is one that cannot be brute forced in a reasonable amount of time and is not vulnerable to a dictionary attack.
Bad password: P@$$w0rd
Reason: Those substitutions are common,...
May 13, 2009 at 11:06 pm
ComITSolutions (5/13/2009)
Yes, My application Stops Sql Server agent & SQl Server Takes Back-up(mdf and ldf files and starts SQL Server and Server Agent.
Don't. That's a very poor way to...
May 13, 2009 at 10:50 pm
Viewing 15 posts - 39,121 through 39,135 (of 49,571 total)