Viewing 15 posts - 7,081 through 7,095 (of 7,185 total)
Claudia
It's not necessarily a bad thing for the log to be bigger than the data - especially if you have a high volume of transactions. What you need to do...
May 31, 2006 at 1:34 am
Ahhh - snapshot replication. While the snapshot is being applied, every insert will be written in the transaction log. That's why it keeps growing.
I think you're confusing the transaction log...
May 30, 2006 at 7:47 am
Alex
In that case, you can write some VB in another Excel workbook that saves your file as an xls and creates the name, then schedule that from SQL Server or...
May 30, 2006 at 6:24 am
Michael
Check out the topic Identifying a Data Source Using a Linked Server Name in Books Online.
John
May 30, 2006 at 5:17 am
Alex
Will this work for you?
(1) Save your spreadsheet as an xls file.
(2) Create a named range in the spreadhseet to cover all the data.
(3) In Enterprise Manager, create a Linked...
May 30, 2006 at 5:12 am
Cláudia
This is normal behaviour. Your destination database is having inserts, deletes and/or updates done on it and these operations will be recorded in the transaction log, causing it eventually to...
May 30, 2006 at 4:53 am
Something that you touched upon is not having control over the membership of the Windows group. If you grant a Windows group access to your SQL server, bear in mind...
May 26, 2006 at 7:12 am
Luis
If your update query looks like this:
UPDATE MyTable
SET MyCol = 'NewValue'
WHERE SomeOtherColumn = 'SomeOtherValue'
Then you can see what rows you are affecting by running this:
SELECT * FROM MyTable
WHERE SomeOtherColumn =...
May 26, 2006 at 4:05 am
I'm liking it - even though it doesn't auto-complete information schema views. Unfortunately I'm stuck with a Windows NT box for administering my production servers and so I can't use...
May 26, 2006 at 1:38 am
Sharon
You need to normalise the MyUsers table. This means having one user ID in each row of the table. Then your query will look like this:
SELECT u.col1, u.col2, m.col1, m.col2
FROM...
May 25, 2006 at 7:05 am
David
The problem with instantiating user-defined structures is that you may end up with crap table design, poor indexing and missing referential integrity. You, as the DBA, will probably spend more...
May 25, 2006 at 6:07 am
Dionisis
What I would suggest is leaving the column as it is, and have your client application present the data in the way you describe. That way, the data stays numeric...
May 25, 2006 at 3:48 am
I'm not saying this will necessarily fix your problem, but if you're using replication then I recommend upgrading to SP4.
As for the problem itself, this is the error that you...
May 25, 2006 at 3:31 am
David
Never give a user db_owner access - not if it's your job on the line when it goes wrong.
First, I would question why an application user needs to create...
May 25, 2006 at 3:23 am
Anyone who doesn't need it. And I would think that includes everybody except DBAs and developers.
John
May 24, 2006 at 9:58 am
Viewing 15 posts - 7,081 through 7,095 (of 7,185 total)